-
Notifications
You must be signed in to change notification settings - Fork 235
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
Major version bump where minor is set #358
Comments
I think we are experiencing a similar issue at #381, our patch changes are released as major changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, we faced the issue with versioning for the second time and decided to create this issue. I've tried to find some solutions or answers why it happens but didn't found anything helpful.
In our project we have a bunch of fixed packages to have consistency when something has changed.
Here is how our config looks:
And here is the latest generated changeset md file:
From the first sight, everything looks nice.
The previous versions of our packages was next:
@organization/anchor
- 1.0.0@organization/react-core
- 1.0.3@organization/theme
- 1.0.3@organization/vite-config-package
- 1.1.0@organization/eslint-config
- 1.2.0@organization/eslint-config-legacy
- 1.1.0@organization/stylelint-config
- 1.2.0@organization/ts-config
- 1.1.0When the "github action" had been completed we've seen that most of our packages' versions was bumped to next major version instead of minor.
The major version was applied to the all components' packages but not for system configs. Looks like the issue is related to fixed version functionality.
The text was updated successfully, but these errors were encountered: