We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If I have a plain-old repo (e.g. single package.json, no workspaces), then the tool should ideally still work as-is.
package.json
However it doesn't seem to be the case currently, if I run it in an example repo with DEBUG=one-version I get the following logs:
DEBUG=one-version
❯ DEBUG=one-version bun run one-version:check $ one-version check [one-version] Initial config { "$schema": "https://one-version.vercel.app/schema.json", "packageManager": "bun", "versionStrategy": "pin" } [one-version] Workspaces [] [one-version] Workspaces Dependencies [] [one-version] Duplicate dependencies [] [one-version] Unpinned dependencies {} My preciousss ✨ One Version Rule Success - found no version conflicts!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
If I have a plain-old repo (e.g. single
package.json
, no workspaces), then the tool should ideally still work as-is.However it doesn't seem to be the case currently, if I run it in an example repo with
DEBUG=one-version
I get the following logs:The text was updated successfully, but these errors were encountered: