Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/release-passlet/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Pass all authenticated `gh` and Git operations through `passlet exec --grant <gr
- [ ] Open a draft release PR in this repository against main, or reuse the existing implementation PR. Confirm it includes the intended Approver, Agent, and package definitions.
- [ ] Write concise, user-facing release notes from changes since the previous published release. Explain what changed for users, including relevant migrations, instead of listing PR titles or internal workflow steps. Include a full changelog link. Commit the notes to `docs/releases/vX.Y.Z.md` in the release PR before pushing the preparation tag. Both workflow phases require this nonempty file, and source verification prevents changing it after preparation.
- [ ] Update user-facing documentation for changes since the previous release, including installation, setup, examples, and migration instructions where applicable. Mark unreleased features with `AddedIn` as described in `docs/authoring.mdx`. Finish these edits before preparing signed artifacts.
- [ ] Confirm the documentation preview build and link checks pass for the candidate. Website design, SEO and PageSpeed audits are outside the release gate. Production PageSpeed checks run weekly through [the ops updater](https://github.com/teamniteo/ops/tree/main/.agents/skills-local/updater).
- [ ] Confirm the documentation preview build and link checks pass for the candidate. Website design, SEO and PageSpeed audits are outside the release gate. Production PageSpeed checks run monthly through [the ops domain-health audit](https://github.com/teamniteo/ops/tree/main/.agents/skills-local/domain-health).
- [ ] Use the successful CI run for the exact candidate as product-test evidence. Run local checks when developing fixes, not again merely to release the same SHA. Source changes require fresh CI.
- [ ] Verify production signing prerequisites in `docs/RELEASING.md`.
- [ ] Wait for the latest PR CI run for the final candidate SHA to finish successfully. Verify that SHA is still the release PR head before preparing signed artifacts.
Expand Down
2 changes: 1 addition & 1 deletion docs/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ the existing prototype identity. The icon source is `assets/passlet.png`;

## Prepare and validate a release

Before pushing the preparation tag, update documentation and confirm the candidate's documentation preview build and link checks pass. Finalize documentation before signing, since publication only permits generated release-label replacements afterward. Website design and SEO audits are outside the release gate. Production PageSpeed audits run weekly through [the ops updater](https://github.com/teamniteo/ops/tree/main/.agents/skills-local/updater).
Before pushing the preparation tag, update documentation and confirm the candidate's documentation preview build and link checks pass. Finalize documentation before signing, since publication only permits generated release-label replacements afterward. Website design and SEO audits are outside the release gate. Production PageSpeed audits run monthly through [the ops domain-health audit](https://github.com/teamniteo/ops/tree/main/.agents/skills-local/domain-health).

Open the release PR in this repository against main. Include concise, user-facing notes in `docs/releases/vX.Y.Z.md`, describing changes since the previous published release and linking to the full changelog. Both workflow phases require this nonempty file. Finalize the notes before preparation, because source verification rejects later changes to them. After its CI passes, push an unused preparation tag such as `v0.4.2-prepare` at its exact reviewed head commit. Preparation verifies the PR is still open, the tag points to its current head, and its latest PR CI run passed. Fork PRs are rejected. Review that commit, including workflow and build-script changes, before approving signing. Both preparation and final publication require approval under the existing `release` environment, restricted to `v*` tags. No signing credentials are available to PR workflows.

Expand Down
Loading