Skip to content

Release v0.1.19 - #267

Merged
Sythos merged 1 commit into
mainfrom
enya/release-v0.1.19
Oct 8, 2026
Merged

Sythos merged 1 commit into
mainfrom
enya/release-v0.1.19

Conversation

@Sythos

@Sythos Sythos commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Version bump to v0.1.19.

@Sythos Sythos self-assigned this Oct 8, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T10:06:15.823373Z 3624e6c PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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}`).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

@Sythos
Sythos merged commit 7b08f41 into main Oct 8, 2026
9 checks passed
@Sythos
Sythos deleted the enya/release-v0.1.19 branch October 8, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant