NPM: Auto doesn't set latest GH release when publishing
Closed this issue · 0 comments
jackw commented
Describe the bug
I'm not 💯 but I think this PR introduced a new flag to git.publish for make_latest however I'm noticing that in Auto 11.0.4 when we publish to NPM the github releases aren't updated to reflect latest. This has the unfortunate side effect that when Auto next tries to calculate version bumps it queries GH based on the latest GH release date. This results in Auto including already released PRs to calculate next version bump and generates changelogs containing duplicated entries.
To Reproduce
- Set up monorepo with Auto 11.0.4 to publish packages to NPM.
- Merge a PR that triggers a release
- GH release will not have latest set
- Merge another PR that triggers a release
- GH releases will not have latest set
Expected behavior
When publishing to NPM the GH release should be set to latest unless it's an old version branch.
Screenshots
Environment information:
"auto" version: v11.0.4
"git" version: v2.43.0
"node" version: v20.9.0
Additional context