Repository navigation
chore: release 2.0.1 with available npm version - #27
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: 0d44537492
ℹ️ 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".
|
|
||
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), | ||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.1.html). |
There was a problem hiding this comment.
Restore the Semantic Versioning 2.0.0 link
The version in this URL refers to the Semantic Versioning specification itself, not this package's release. SemVer's published specification is 2.0.0, so changing the link to v2.0.1.html leaves changelog readers with an invalid specification link; keep this URL at https://semver.org/spec/v2.0.0.html.
Useful? React with 👍 / 👎.
npm permanently reserves version 2.0.0, which its registry history records as published on 2026-02-08 and which is no longer available. Use 2.0.1 for this release.
Updates only release version metadata and documentation; the implementation and dependency versions are unchanged from #26.