Skip to content
New issue

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

Local packaged dependencies referenced by file mistakenly trigger bump and show up in Changelog #1035

Open
hectormmg opened this issue Mar 11, 2025 · 0 comments

Comments

@hectormmg
Copy link

When a package has internal private dependencies (i.e. packaged utils referenced by "file:" in the package.json), the existing version range will not match the package's actual version. This is causing beachball bump to add changelog entries on bump referencing the bumping of said internal dependencies.

if (existingVersionRange !== bumpedVersionRange) {

I couldn't find any configuration option in the docs to make beachball ignore these internal packages.

Example from a verbose execution of beachball bump:

@azure/msal-common needs to be bumped because eslint-config-msal file:../../shared-configs/eslint-config-msal -> 0.0.0
@azure/msal-common needs to be bumped because msal-test-utils file:../../shared-test-utils -> 0.0.1
@azure/msal-common needs to be bumped because rollup-msal file:../../shared-configs/rollup-msal -> 0.0.0

Example of the resulting changelog with false bump entries for these dependencies:

AzureAD/microsoft-authentication-library-for-js@20674a1#diff-8f1fef2ac7777148212f5d8a43e43e428ba981830435fcef371908663229d89eR14

Is there anything in the config that can currently prevent this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant