ci: include postgres template in version bumps#89
Merged
Conversation
The PostgreSQL template (added in #86) was never registered in the release version-bump automation, so every release bumped the other templates' @udibo/juniper version while leaving postgres frozen at ^0.5.0. - Add templates/postgres/deno.json to scripts/update-juniper-version.sh so the prepare step rewrites its @udibo/juniper version on release. - Add it to the @semantic-release/git assets in .releaserc.json so the rewrite is actually committed with the release. - Catch the template up to the current deps (@udibo/juniper ^0.7.1, pg ^8.21.0, zod ^4.4.3) to match the other templates, and regenerate the lockfile. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 0.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The PostgreSQL template (added in #86) was never registered in the release version-bump automation. As a result, every release rewrote and committed the
@udibo/juniperversion for the other templates while leaving the postgres template frozen at^0.5.0. This fixes the automation so the postgres template tracks releases like the others, and catches the template up to the current versions.Changes
scripts/update-juniper-version.sh— addtemplates/postgres/deno.jsonto theFILESarray so the prepare step rewrites its@udibo/juniperversion on each release..releaserc.json— addtemplates/postgres/deno.jsonto the@semantic-release/gitassets so the rewrite is actually committed with the release (this is the part that was silently dropping the change before).templates/postgres/deno.json— catch up to the current deps to match the other templates:@udibo/juniper^0.5.0→^0.7.1,pg^8.20.0→^8.21.0,zod^4.3.6→^4.4.3.deno.lock— regenerate for the postgres template workspace update.Typed as
ci(notchore(deps)/fix) on purpose: the dependency bumps are in a template, not the publishedsrc/library, so this should not cut a no-op release of@udibo/juniper.Testing
JSON.parsevalidates.releaserc.json.bash -nvalidates the update script syntax.@udibo/juniperversion now matches all other templates (^0.7.1).🤖 Generated with Claude Code