Repository navigation
Finalize the 1.0.0-next.0 release candidate - #15
Conversation
|
@codex review |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This PR finalizes the 1.0.0-next.0 release candidate by locking in release-date copy, tightening wrong-tag recovery to preserve immutable tags, and hardening CI so tag-deletion events cannot trigger publication or GitHub Release creation.
Changes:
- Guard
publishandgithub-releasejobs to skip deleted-tag push events. - Finalize and validate release runbook ordering (date copy before binding/tagging) and strengthen “wrong tag” recovery to fail closed.
- Stamp the prerelease date across release notes and all package changelogs; update release-runbook verification tests accordingly.
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| scripts/check-release.test.mjs | Expands release/runbook and workflow contract tests (deleted-tag gating, recovery invariants, E404 checker behavior). |
| .github/workflows/ci.yml | Adds deleted-tag event guard to prevent publish/release jobs from running on tag deletion pushes. |
| docs/releasing.md | Updates release runbook to finalize dated release copy pre-binding, enforce immutable-tag recovery, and derive versions from verified artifacts. |
| docs/plans/2026-08-10-configured-dtcg-adoption.md | Updates release plan step wording for review checks. |
| docs/launch/v1.0.0-next.0.md | Marks the prerelease as “Released 2026-08-17.” |
| packages/core/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
| packages/dtcg/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
| packages/cli/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
| packages/hooks/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
| packages/mcp/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
| packages/primitree/CHANGELOG.md | Dates the 1.0.0-next.0 entry. |
Suppressed comments (3)
docs/releasing.md:997
- This step defines
ARTIFACT_DIR=artifacts/npm, but the manifest path in thenode -pcommand is still hard-coded. Using$ARTIFACT_DIRavoids duplication and keeps the snippet consistent with the variable.
VERSION=$(node -p "require('./artifacts/npm/manifest.json').version")
docs/releasing.md:1121
ARTIFACT_DIRis set in this block, but the manifest path is hard-coded. Consider using$ARTIFACT_DIRso the snippet stays correct if the artifact directory changes.
VERSION=$(node -p "require('./artifacts/npm/manifest.json').version")
docs/releasing.md:1171
- This block sets
ARTIFACT_DIRbut still hard-codes./artifacts/npm/manifest.jsonwhen extractingVERSION. Using$ARTIFACT_DIRremoves duplication and keeps the commands consistent.
VERSION=$(node -p "require('./artifacts/npm/manifest.json').version")
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 413fd2d45a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59330526e8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…zero Finalize the 1.0.0-next.0 release candidate
Summary
1.0.0-next.0release dates before binding and tagging the exactmaincommitVerification
1.0.0-next.0