Skip to content

chore(ci): stop forcing a release now canopy 1.0.0 is out - #544

Closed
passcod wants to merge 1 commit into
mainfrom
chore/unforce-release
Closed

chore(ci): stop forcing a release now canopy 1.0.0 is out#544
passcod wants to merge 1 commit into
mainfrom
chore/unforce-release

Conversation

@passcod

@passcod passcod commented Sep 4, 2026

Copy link
Copy Markdown
Member

🤖 Reverts the temporary setting from #543, which forced one release so canopy 1.0.0 could be tagged and deployed. That has happened: public-server-v1.0.0 and its eight siblings are tagged at c5620c83e, and the deploy ran.

With release_always back to false, a merged release PR is once again the only thing that releases, so an ordinary merge to main does not reach production.

Reverts the temporary setting from #543: the canopy crates are tagged at
1.0.0, so a release PR is again the only thing that releases and deploys.
@passcod

passcod commented Sep 4, 2026

Copy link
Copy Markdown
Member Author

🤖 Superseded by #545, which rewrites release-plz.toml wholesale — release_always no longer exists as a two-track setting.

@passcod passcod closed this Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant