release/* branches version bumping is weird

[mofojed]

• Can't just run the ./release.sh command, need to specify the patch
  • Manually ran cog bump --package "ui" --patch" which got most of the way there... except it seemed to bump the minor version. Crap.
  • Could do cog bump --package "ui" --version 0.15.3, or add the --dry-run flag to see it before bumping
  • That doesn't work though, because it thinks the current version is still what's on the main branch...
  • Then needed to do git push origin release/ui-v0.15
• What do we set for the dist-tag? Since the branch will be dependent on the package...
  • Or do we just have one branch for "vplus", and tag it as such?
• Tries to push to main instead of the same branch
• Python Plugins should be published when the Release is created, instead of triggered from a tag push
  • Right now it's being published as part of the modified-plugin.yml workflow on a tag push, rather than triggering when the release is created.

[mofojed]

Sounds like bump-profiles are what we need: https://docs.cocogitto.io/guide/#bump-profiles

[mofojed]

Breaking it down a bit, can use conventional-changelog-cli to create the changelog, e.g.

./node_modules/.bin/conventional-changelog -p conventionalcommits --tag-prefix ui-v --commit-path ./plugins/ui

[mofojed]

Release Please looks interesting: https://github.com/googleapis/release-please

[mofojed]

Cocogitto doesn't seem to support patching from a hotfix branch: https://github.com/cocogitto/cocogitto/issues/241 That seems like a major oversight, especially considering they mention hotfix in the Bump Profiles section: https://docs.cocogitto.io/guide/#bump-hooks I'm a little confused. Looks like it may already be addressed with an open PR when it merges?