fix: guard published release documentation#63
Conversation
![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: dd93543727
ℹ️ 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".
| /STABLE v[0-9]+\.[0-9]+\.[0-9]+(?: (?:release candidate|published release))?/g, | ||
| expected.published | ||
| ? `STABLE v${expected.version} published release` | ||
| : `STABLE v${expected.version}` |
There was a problem hiding this comment.
When the current source version is not yet the latest published release, for example USERS.md says the latest published release is the previous version, expected.published is false but any safe architecture fix still matches and consumes release candidate here, then rewrites it to bare STABLE v.... That means a routine surface-count or version sync during release-candidate prep silently removes the candidate status that this guard is meant to distinguish; the previous regex only updated the version portion and preserved the suffix.
Useful? React with 👍 / 👎.
1 participant
Summary
Verification