Scope changelog entry IDs to releases - #39
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: 04ea320c61
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 38c291bc8c
ℹ️ 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".
caf34f4 to
6ea7b29
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6ea7b29df4
ℹ️ 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".
Preserve each historical entry occurrence and resolve release manifests against their own entry directories. Reused IDs remain eligible for release creation and retain release context in show output and statistics. Assisted-by: GPT-5 (Codex)
Assisted-by: GPT-5 (Codex)
Ignore retained release-candidate manifests after their stable release exists. Historical RC IDs no longer suppress reused unreleased entries when another stable release is updated. Assisted-by: GPT-5 (Codex)
Cover the outstanding-to-closed candidate transition in the existing helper test instead of reproducing the full release workflow. Assisted-by: GPT-5 (Codex)
Remove product behavior from the bundled add-entry instructions. The skill explains how to use the command. Product documentation remains the source for system semantics. Assisted-by: GPT-5 (Codex)
Apply scope tokens before resolving row, exact, and partial entry identifiers. Constrain release identifiers to the same scope so reused IDs return only the requested namespace. Assisted-by: GPT-5 (Codex)
6ea7b29 to
9717308
Compare
Prevent scoped show queries from rendering or exporting a release manifest when a newer stable release defines the latest scope. Assisted-by: GPT-5 (pi)
1 participant
🔍 Problem
Entry slugs were treated as globally unique across the complete changelog
history. Reusing a slug from an older release could hide the new entry from
release creation, collapse distinct occurrences in
showand statistics, andlet validation resolve a manifest reference against the wrong release.
🛠️ Solution
unreleasedor one release.manifest.
stable release.
💬 Review
Focus on the release-scoped identity invariant and the release-candidate
📚 Docs PR: tenzir/content#138lineage exception. Exact
showlookups intentionally return every matchingoccurrence.