[haskou]

Summary

• Sync package.json to the already published npm version 2.7.0.
• Update the publish workflow to compute releases from package.json, publish with Trusted Publishing, then commit the release version and create the matching vX.Y.Z tag.
• Add a PR-number release marker so rerunning the same merged PR does not publish another version.
• Document that successful publishes commit the release version and tag.

Validation

• git diff --check
• yarn lint && yarn test:coverage && yarn build
• Parsed .github/workflows/ci.yml with js-yaml

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4d63be2b33

ℹ️ 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".

[chatgpt-codex-connector]

Recheck the tag before declaring the release done

If a release run partially succeeds by pushing the release commit to the base branch but then fails while pushing v${NEXT_VERSION}, any rerun for that merged PR will hit this subject grep, set already_released=true, and exit before the later tag creation/push logic runs. That leaves the npm release without the matching Git tag and makes the workflow unable to repair it on rerun; the early-exit check should also verify the tag exists remotely or allow the tag step to run.

Useful? React with 👍 / 👎.