Release Maintainer
Ship or inspect Rudder releases without losing source identity, authorization,
or public-surface completeness.
Route Before Reading
Read references/shared.md, then exactly one primary branch:
references/stable.md: stable readiness, publish, public notes, Desktop
update drill, post-stable cleanup, next-version handoff, and the gate before
public announcement.
references/canary.md: automatic canary publication, first npm bootstrap,
Desktop prerelease assets, and temporary pre-stable latest behavior.
references/rollback.md: move npm dist-tags to an already published version
without unpublishing packages or rewriting tags.
references/partial-recovery.md: npm/tag/Release/Desktop/docs surfaces
disagree, a workflow failed after partial publication, or install lookup
returns misleading errors.
references/setup.md: one-time GitHub environment, npm trusted-publishing,
and workflow setup.
references/announcement.md: manual Rudder Discord announcement after a
stable release has converged. This is a stable closeout add-on, not a primary
release branch.
Use a second branch only when the observed state genuinely crosses branches,
such as a stable publish that needs partial recovery. Do not preload every
reference for a readiness question.
For a requested Rudder stable release, read references/announcement.md after
the release surfaces are verified. Zeeland explicitly authorized this default
on 2026-09-08: send one release announcement to Rudder / #announcements unless
the user opts out. Reuse that standing authority without a second confirmation.
Read-only checks, canaries, and publishing only a named non-release surface do
not trigger it. Do not add announcements to Release CI or create a webhook.
Authorization Boundary
An explicit request to release a Rudder version, such as release vX.Y.Z,
ship this version, or 发版 in a version-release context, authorizes the
complete standard release lifecycle below. A request to publish only named docs,
a package, or another surface authorizes that surface and its prerequisites.
Resolve a bare publish from context; do not expand it into a full version release.
- resolve and lock the single consistent version and source SHA;
- land reviewed release source on
main through a PR and required checks when needed;
- run required exact-source CI, preflight, and package validation once;
- publish npm, tag, GitHub Release, Desktop, and production-docs surfaces;
- verify public installation, clean obsolete canary Releases/tags, and advance
the next-version base through its protected-branch PR;
- publish and read back the stable Discord announcement under Zeeland's standing
authorization, unless the user explicitly opts out.
Release and next-version PRs are part of this authorization. Never push directly
to main or bypass its protection. Do not ask for routine second approval after validation.
Ask only when channel, version, source, or destination is materially ambiguous.
Questions such as “how does release work?” or “is this ready?” are read-only.
Implementation requests without a release/publish imperative stop at Review
Ready.
Separate authority is still required for npm unpublish, force-pushing or
retargeting published tags, deleting the active canary line, bypassing CI,
exposing secrets, or expanding to another product/environment.
Cross-Branch Invariants
- Lock stable source to a full immutable commit SHA. Later
main movement does
not silently retarget it, and manual stable dispatch must not use a branch or
tag as source_ref.
- Freeze that source as soon as a stable release imperative arrives. New
unrelated
main work belongs to the next release instead of extending the
active release window.
- Never republish an npm version that already exists.
- npm packages use
@rudderhq; Desktop binaries belong to GitHub Releases.
- Stable uses npm
latest; canary uses canary. A first-public pre-stable
bootstrap may also use latest only after matching Desktop assets exist.
- Canary tags are
canary/vX.Y.Z-canary.N; their GitHub Release title is the
clean vX.Y.Z-canary.N and the Release is prerelease.
- A stable tag points at the reviewed source commit, not a generated handoff
commit.
- Partial publication is repaired from its first missing surface; immutable
npm versions are not republished.
- Public completion requires applicable npm, tag, GitHub Release, Desktop,
changelog/docs, install smoke, and next-version handoff evidence. A Discord
announcement URL is required only when announcement delivery is in scope.
- Canary releases do not receive Discord announcements. Do not add announcement
delivery to Release CI as part of ordinary release execution.
- Cleanup removes obsolete GitHub Releases and
canary/* tags, not published
npm canary versions.
- A stable release takes priority over an in-flight canary for the same or an
older version base once the locked stable source passes its gates. Do not wait
for obsolete canary Desktop assets; record npm/tag state, stop the remaining
canary work when safe, and let stable cleanup remove its Release/tag.
- Keep public install smoke, including slow Windows runtime installation. A slow
real install is product evidence to optimize, not a release gate to delete.
- Once a stable campaign is active, candidate-repair commits use
[skip release]
unless a canary is explicitly needed. CI still validates the repair, while the
automatic canary path does not duplicate the manual stable candidate.
- Do not dispatch a third run after the same stage fails twice on unchanged
inputs. Diagnose and repair that stage, then rerun the new immutable SHA once.
- Preserve unrelated dirty work. Prefer a clean temporary worktree/clone for
hands-on publication.
Operating Loop
- Classify the request as setup, canary, stable, rollback, partial recovery,
or read-only inspection.
- Read
references/shared.md and the selected primary reference.
- Resolve live local and remote state, then freeze the stable SHA immediately;
release truth is temporally unstable.
- When release narratives are missing and subagents are available, start one
bounded release-notes subagent in parallel with read-only preflight. Give it
the locked diff and require drafts for the GitHub notes plus both public
changelogs; the primary agent reviews and integrates the drafts.
- State the selected version, locked source SHA, channel, active workflow run,
last completed stage, and unresolved blockers in a progress update.
- Execute one stable publish path whose machine gates run before mutation; do
not introduce a separate preview dispatch or second human hand-off.
- Verify every applicable public surface from the same locked source.
- For an authorized stable announcement, follow
references/announcement.md: check for an existing
version post, publish the bounded announcement with no default ping, read it
back, and record its direct message URL.
Stable releases include this step by default. Record an explicit opt-out as
skipped by user; missing or unknown delivery means partial closeout. Do not
ask for routine second authorization.
- Report version/ref, workflow runs, npm tags, Release assets, install proof,
changelog/docs state, announcement URL, cleanup, and remaining manual work.
Output
For read-only requests:
Current state:
Blockers:
Next actions:
Authorization:
Verification required:
For hands-on execution:
RESULT: RELEASED | PARTIAL | BLOCKED
Version/channel:
Locked source:
Checks:
Published surfaces:
Install proof:
Announcement:
Cleanup/handoff:
Remaining blocker:
1---2name: release-maintainer-23description: "Use when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord announcements, install smoke, stable/canary promotion, rollback, and release workflow failures. Use for both hands-on publish requests and read-only release readiness questions; route to the smallest relevant release reference instead of loading every release branch."4metadata:5 source: https://skillmd.com/skills/undertone0809/release-maintainer-26---78# Release Maintainer910Ship or inspect Rudder releases without losing source identity, authorization,11or public-surface completeness.1213## Route Before Reading1415Read `references/shared.md`, then exactly one primary branch:1617- `references/stable.md`: stable readiness, publish, public notes, Desktop18 update drill, post-stable cleanup, next-version handoff, and the gate before19 public announcement.20- `references/canary.md`: automatic canary publication, first npm bootstrap,21 Desktop prerelease assets, and temporary pre-stable `latest` behavior.22- `references/rollback.md`: move npm dist-tags to an already published version23 without unpublishing packages or rewriting tags.24- `references/partial-recovery.md`: npm/tag/Release/Desktop/docs surfaces25 disagree, a workflow failed after partial publication, or install lookup26 returns misleading errors.27- `references/setup.md`: one-time GitHub environment, npm trusted-publishing,28 and workflow setup.29- `references/announcement.md`: manual Rudder Discord announcement after a30 stable release has converged. This is a stable closeout add-on, not a primary31 release branch.3233Use a second branch only when the observed state genuinely crosses branches,34such as a stable publish that needs partial recovery. Do not preload every35reference for a readiness question.3637For a requested Rudder stable release, read `references/announcement.md` after38the release surfaces are verified. Zeeland explicitly authorized this default39on 2026-09-08: send one release announcement to Rudder / #announcements unless40the user opts out. Reuse that standing authority without a second confirmation.41Read-only checks, canaries, and publishing only a named non-release surface do42not trigger it. Do not add announcements to Release CI or create a webhook.4344## Authorization Boundary4546An explicit request to release a Rudder version, such as `release vX.Y.Z`,47`ship this version`, or `发版` in a version-release context, authorizes the48complete standard release lifecycle below. A request to publish only named docs,49a package, or another surface authorizes that surface and its prerequisites.50Resolve a bare `publish` from context; do not expand it into a full version release.51521. resolve and lock the single consistent version and source SHA;532. land reviewed release source on `main` through a PR and required checks when needed;543. run required exact-source CI, preflight, and package validation once;554. publish npm, tag, GitHub Release, Desktop, and production-docs surfaces;565. verify public installation, clean obsolete canary Releases/tags, and advance57 the next-version base through its protected-branch PR;586. publish and read back the stable Discord announcement under Zeeland's standing59 authorization, unless the user explicitly opts out.6061Release and next-version PRs are part of this authorization. Never push directly62to `main` or bypass its protection. Do not ask for routine second approval after validation.63Ask only when channel, version, source, or destination is materially ambiguous.6465Questions such as “how does release work?” or “is this ready?” are read-only.66Implementation requests without a release/publish imperative stop at Review67Ready.6869Separate authority is still required for npm unpublish, force-pushing or70retargeting published tags, deleting the active canary line, bypassing CI,71exposing secrets, or expanding to another product/environment.7273## Cross-Branch Invariants7475- Lock stable source to a full immutable commit SHA. Later `main` movement does76 not silently retarget it, and manual stable dispatch must not use a branch or77 tag as `source_ref`.78- Freeze that source as soon as a stable release imperative arrives. New79 unrelated `main` work belongs to the next release instead of extending the80 active release window.81- Never republish an npm version that already exists.82- npm packages use `@rudderhq`; Desktop binaries belong to GitHub Releases.83- Stable uses npm `latest`; canary uses `canary`. A first-public pre-stable84 bootstrap may also use `latest` only after matching Desktop assets exist.85- Canary tags are `canary/vX.Y.Z-canary.N`; their GitHub Release title is the86 clean `vX.Y.Z-canary.N` and the Release is prerelease.87- A stable tag points at the reviewed source commit, not a generated handoff88 commit.89- Partial publication is repaired from its first missing surface; immutable90 npm versions are not republished.91- Public completion requires applicable npm, tag, GitHub Release, Desktop,92 changelog/docs, install smoke, and next-version handoff evidence. A Discord93 announcement URL is required only when announcement delivery is in scope.94- Canary releases do not receive Discord announcements. Do not add announcement95 delivery to Release CI as part of ordinary release execution.96- Cleanup removes obsolete GitHub Releases and `canary/*` tags, not published97 npm canary versions.98- A stable release takes priority over an in-flight canary for the same or an99 older version base once the locked stable source passes its gates. Do not wait100 for obsolete canary Desktop assets; record npm/tag state, stop the remaining101 canary work when safe, and let stable cleanup remove its Release/tag.102- Keep public install smoke, including slow Windows runtime installation. A slow103 real install is product evidence to optimize, not a release gate to delete.104- Once a stable campaign is active, candidate-repair commits use `[skip release]`105 unless a canary is explicitly needed. CI still validates the repair, while the106 automatic canary path does not duplicate the manual stable candidate.107- Do not dispatch a third run after the same stage fails twice on unchanged108 inputs. Diagnose and repair that stage, then rerun the new immutable SHA once.109- Preserve unrelated dirty work. Prefer a clean temporary worktree/clone for110 hands-on publication.111112## Operating Loop1131141. Classify the request as setup, canary, stable, rollback, partial recovery,115 or read-only inspection.1162. Read `references/shared.md` and the selected primary reference.1173. Resolve live local and remote state, then freeze the stable SHA immediately;118 release truth is temporally unstable.1194. When release narratives are missing and subagents are available, start one120 bounded release-notes subagent in parallel with read-only preflight. Give it121 the locked diff and require drafts for the GitHub notes plus both public122 changelogs; the primary agent reviews and integrates the drafts.1235. State the selected version, locked source SHA, channel, active workflow run,124 last completed stage, and unresolved blockers in a progress update.1256. Execute one stable publish path whose machine gates run before mutation; do126 not introduce a separate preview dispatch or second human hand-off.1277. Verify every applicable public surface from the same locked source.1288. For an authorized stable announcement, follow `references/announcement.md`: check for an existing129 version post, publish the bounded announcement with no default ping, read it130 back, and record its direct message URL.131 Stable releases include this step by default. Record an explicit opt-out as132 skipped by user; missing or unknown delivery means partial closeout. Do not133 ask for routine second authorization.1349. Report version/ref, workflow runs, npm tags, Release assets, install proof,135 changelog/docs state, announcement URL, cleanup, and remaining manual work.136137## Output138139For read-only requests:140141```text142Current state:143Blockers:144Next actions:145Authorization:146Verification required:147```148149For hands-on execution:150151```text152RESULT: RELEASED | PARTIAL | BLOCKED153Version/channel:154Locked source:155Checks:156Published surfaces:157Install proof:158Announcement:159Cleanup/handoff:160Remaining blocker:161```