chore: verify release-bot flow#23
Merged
Merged
Conversation
Test PR that drives a real v0.5.1 patch bump to confirm the GitHub App release flow works end-to-end. The resulting Version Packages PR should be authored by ccpluginizer-release-bot[bot] and trigger its own validate + changeset-check workflows.
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
End-to-end verifier for the GitHub App release-bot flow set up in #22. Adds a real
patchchangeset for@ccpluginizer/ccpluginizerso the nextrelease.ymlrun is forced to open a "Version Packages" PR.Expected behavior after merging this PR
release.ymlfires on push tomain.changesets/actionsees one non-empty changeset (verify-release-flow.md) plus the parked empty one (fresh-mugs-drop.md).ccpluginizer-release-bot[bot](notgithub-actions[bot]) — this is the property we're verifying.validate+changeset-checkfire on the release PR and pass without admin override — the second property we're verifying.What this PR itself changes
Just the changeset file. No code change. The "release" is essentially synthetic —
verify-release-flow.mdis the only substantive change going into v0.5.1, and its release notes are about verifying the bot flow.Test plan
changeset-check(this PR has a changeset, will pass)validate(no code change, should pass trivially)ccpluginizer-release-bot[bot]validate+changeset-checkboth pass without manual intervention