-
Notifications
You must be signed in to change notification settings - Fork 13
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
release/* branches version bumping is weird #557
Comments
- Note there's still some weirdness around how we should handle dist-tags, will address with deephaven#557 fixes. This just makes sure I don't publish a version "latest" from this branch - Update the changelogPreset to use conventionalcommits (was done in web-client-ui with deephaven/web-client-ui#2054)
- Note there's still some weirdness around how we should handle dist-tags, will address with #557 fixes. This just makes sure I don't publish a version "latest" from this branch - Update the changelogPreset to use conventionalcommits (was done in web-client-ui with deephaven/web-client-ui#2054)
Sounds like bump-profiles are what we need: https://docs.cocogitto.io/guide/#bump-profiles |
Breaking it down a bit, can use
|
Release Please looks interesting: https://github.com/googleapis/release-please |
Cocogitto doesn't seem to support patching from a hotfix branch: cocogitto/cocogitto#241 |
Release bumping in general needs better confirmation before the release is actually created. |
./release.sh
command, need to specify the patchcog bump --package "ui" --patch"
which got most of the way there... except it seemed to bump the minor version. Crap.cog bump --package "ui" --version 0.15.3
, or add the--dry-run
flag to see it before bumpinggit push origin release/ui-v0.15
main
instead of the same branchThe text was updated successfully, but these errors were encountered: