Repository navigation
chore: add /currents-release-package, the steps to release to npm - #15
Merged
Merged
Conversation
The steps are the ones used for 3.0.0-beta.0 and 3.0.0: release commit, PR merged with a merge commit, publish workflow from master or from a release branch for prereleases, check from npm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011baD3hSBFPLp26um5JriwA
|
| Topic | Details | ||||||
|---|---|---|---|---|---|---|---|
| Npm Release Flow | Document the complete latest, alpha, and beta npm release flow, including versioning, validation, PR or branch handling, publishing, package verification, rollback, and reporting.Modified files (1)
Latest Contributors(1)
| ||||||
| Release Communication | Define operator-controlled Slack announcements and threaded post-release confirmation messages with links and verification evidence.Modified files (1)
Latest Contributors(1)
|
Merger ✅ Ready to Merge
MERGE: low-risk documentation/skill addition with no open discussions or blockers; CI ran successfully.
![baz-app[bot]](https://avatars.githubusercontent.com/in/1124379?s=60&v=4){kind=small}
As in the platform release: announce in #releases before the publish, and reply in the thread when the version is on npm. commit-info has no Linear release pipeline. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011baD3hSBFPLp26um5JriwA
baz-app
Bot
dismissed
their stale review
November 5, 2026 05:12
Baz withdrew its approval because this pull request is no longer ready to merge.
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.
Owner: @agoldis
Adds
/currents-release-package(.claude/skills/currents-release-package/SKILL.md): the steps to release@currents/commit-infoto npm. Claude Code loads it in this repo as a skill and as a slash command, for example/currents-release-package 3.1.0.The steps are the ones used for 3.0.0-beta.0 and 3.0.0:
npm versionand a hand-written CHANGELOG sectionmaster, merged with a merge commit, then the publish workflow frommasterrelease/<version>branch, without a PR#releasesbefore the publish, and a reply in its thread when the version is on npm, as in the platform release. The agent shows each message to the operator before posting it.commit-info has no Linear release pipeline, so the skill only lists the tickets in the announcement.
filesinpackage.jsononly includessrc, so.claudeis not published.🤖 Generated with Claude Code
https://claude.ai/code/session_011baD3hSBFPLp26um5JriwA