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

follow semver for releases #2755

Open
croconut opened this issue Sep 3, 2024 · 0 comments
Open

follow semver for releases #2755

croconut opened this issue Sep 3, 2024 · 0 comments

Comments

@croconut
Copy link

croconut commented Sep 3, 2024

Is your feature request related to a problem? Please describe.
i recently was unable to perform a patch update due to a breaking change in #2719 following semver would prevent this.

Describe the solution you'd like
clear deprecation warnings and/or bumping breaking changes to major version releases.

Describe alternatives you've considered
freezing the version. im updating the code right now, but i would have had an outage if i only used colons on prod. fortunately my dev vs prod is nearly identical wrt this library. that said, now im tempted to add a test suite run with NODE_ENV = production lol

i dont know what else would randomly break on a patch, colons in the queue name was i think the only non-standard thing we do. i would recommend that experimental features not get bugfixes that break other things in a non-major update though.

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