Repository navigation
chore: remove /release skill, superseded by release workflows - #126
Open
muzahidul-opti wants to merge 2 commits into
Open
muzahidul-opti wants to merge 2 commits into
muzahidul-opti wants to merge 2 commits into
Conversation
publish.yml now publishes to pub.dev and creates the GitHub release after the release PR merges (#122); running the skill would race the pipeline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
.claude/skills/ prepare-release/ # opens the release PR; title no longer says "Step 1", notes what runs after merge - release/ # flutter pub publish + gh release createAfter the release PR merges,
publish.yml(#122) now publishes to pub.dev and creates the GitHub release. If someone ran the skill after a merge, it would race the pipeline, and the second publish would fail because the version already exists.Evidence
/release.After: v4.0.0 went out through the pipeline alone:
git grepfinds no other references to the skill.Merge Danger
Door: two-way. Revert to restore the skill.
Blast Radius: Claude Code users lose
/release. The manual fallback steps are still in CLAUDE.md and on the Confluence release page.🤖 Generated with Claude Code