[coisa]

Enables publish: true in the existing Changelog reusable caller, allowing an approved managed version PR merge to create its tag and GitHub Release. Keeps @v0, PR-origin discovery, preparation, credentials, runners, permissions and publication validation unchanged. Includes one independent patch fragment.

Validation: actionlint, git diff --check and the adopted v0.2.0 CLI check --since=origin/main passed. The selected v0 channel still resolves to 2d3f84fa9e5350f03636153fdb3ae2a822e5ae60; its publisher runs only for a merged same-repository PR from changelog/version into main and verifies the approved version transaction.

The generated version PR #40 was merged at 420018d9c94ab5e32df0a51eb3bbe2609d183fec, but v1.7.1 has no published tag/Release while publication was disabled. This configuration change enables future publication; it does not replay that earlier closed event or publish v1.7.1 retroactively. The subsequent preparation run 39110426591 reported “Version PR synchronization could not be verified”. The read-only v0.2.0 CLI status check identifies the underlying planning blocker: “Maintained release 1.7.1 is awaiting its reachable stable Git tag; complete its approved publication or reviewed recovery before planning another version. Latest reachable stable version: 1.7.0.” prepare-release: true already controls version-PR creation independently of this setting. An explicitly authorized recovery/publication of the approved v1.7.1 is still needed before the next version PR can be planned; enabling this setting alone cannot clear that existing blocker.

No tag, Release, historical publication or managed version branch is changed by this PR, and no publication was dispatched for testing.

[chatgpt-codex-connector]

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-18T17:19:58.144209Z	c2503ae	PR opened
🔒 Security Review	✅ Completed 2026-10-18T17:22:59.760512Z	c2503ae	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.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 36dcb65f-2358-4916-ac77-75374aff032f

📥 Commits

Reviewing files that changed from the base of the PR and between 8c21c0b and c2503ae.

📒 Files selected for processing: 2

• .changelog/enable-release-publication.md
• .github/workflows/changelog.yml

+-----------------------------------------+
| Tensor cores warmed; bug cores chilled. |
+-----------------------------------------+
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Changelog

✅ Contribution check passed.

Head: c2503ae12ef1433553a56cd9701cc6325af113d6

Base: 8c21c0bfdae72361b31a279b3881dfdbcefbf712

Contribution: 1 new valid fragment(s). Policy: ordinary.

• enable-release-publication.md — changed, patch

  Publish the release tag and GitHub Release after an approved managed version pull request is merged.