Repository navigation
Release v0.1.19 - #267
Release v0.1.19#267
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3624e6c1ed
ℹ️ 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".
| @@ -0,0 +1,16 @@ | |||
| Cordiale package version: `${PACKAGE_VERSION}` (tag version `${VERSION}`, GitHub Actions run ID `${RUN_ID}`, attempt `${RUN_ATTEMPT}`). | |||
There was a problem hiding this comment.
Use the placeholders rendered by the release workflow
When the v0.1.19 tag runs .github/workflows/packages.yml, the release-note renderer substitutes ${BUILD_ID} and ${BUILD_ATTEMPT}, not ${RUN_ID} and ${RUN_ATTEMPT}. These two values will therefore be published literally in the GitHub release body, leaving its build provenance metadata incorrect; rename them to the placeholders consumed by the workflow.
Useful? React with 👍 / 👎.
Version bump to v0.1.19.