Repository navigation
Automate WattPlan releases with a PowerShell skill - #54
Merged
Merged
Conversation
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
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.
Replace the manual release runbook with a three-step
wattplan-releaseskill and a colocated PowerShell 7 script. Agents provide the target tag and intended Markdown notes; the script handles publication.The script rejects dirty checkouts, unpublished local main commits, and existing tags. It switches to and fast-forwards main, updates both versions, commits and pushes, waits for successful push CI on the exact main SHA, then creates and pushes an annotated tag and waits for its separate CI. After verifying the published release state and nonempty
wattplan.zip, it applies and verifies the supplied notes. Failures stop with the current stage and preserve completed steps; CI waits are bounded.Move release guidance into the skill and update repository links. No release was published during validation.
Validation:
git diff --checkpassed.