You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bumpy seems to struggle with tagged verson updates #134
I deploy alpha/canary releases first, and bumpy seems to ignore these, waiting for a minor/patch update before triggering. Is there a way to ensure bumpy wraps up a changelog in an alpha update?
Yes. Otherwise everything builds up and then is only promoted at patch.
$ bunx bumpy status
67 bump file(s) pending
Minor
foo: 0.2.0-alpha.155 → 0.2.0 (packages/foo)
Patch
create-foo-app: 0.1.7 → 0.1.8 (packages/create-foo-app)
I'd rather get a changelog on all alpha releases - and then a coordinated changelog of all alpha releases at patch/minor update. Look at how nextjs handles their alpha releases. It can be hundreds of commits in alpha before its promoted to patch/minor.
would it be ok to keep the pre-release changelog in a different file, for example CHANGELOG-alpha.md - which gets deleted when it eventually gets fully released?
Activity
theoephraim commentedon Jun 24, 2026
Sorry I don't quite understand. You're just hoping for changelog generated for the prerelease?
switz commentedon Jun 24, 2026
Yes. Otherwise everything builds up and then is only promoted at patch.
I'd rather get a changelog on all alpha releases - and then a coordinated changelog of all alpha releases at patch/minor update. Look at how nextjs handles their alpha releases. It can be hundreds of commits in alpha before its promoted to patch/minor.
theoephraim commentedon Jul 3, 2026
would it be ok to keep the pre-release changelog in a different file, for example
CHANGELOG-alpha.md- which gets deleted when it eventually gets fully released?theoephraim commentedon Jul 3, 2026
Also - are you seeing the per-release changes in each github release for pre-releases? (You should)
switz commentedon Jul 4, 2026
Yeah I suppose that would be fine, as long as all the changes would then get wrapped up together into the main changelog?
re: second question, I haven't gotten that far yet.