chore(main): release @trey.turner/artifacts-cli 0.0.2#21
chore(main): release @trey.turner/artifacts-cli 0.0.2#21treyturner wants to merge 1 commit intomainfrom
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e353d80ef4
ℹ️ 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".
| { | ||
| "name": "@trey.turner/artifacts-cli", | ||
| "version": "0.0.1", | ||
| "version": "0.0.2", |
There was a problem hiding this comment.
In the release workflow I checked (.github/workflows/release-publish.yaml:23-26), googleapis/release-please-action is driven by the repo manifest, but this commit only bumps packages/cli/package.json to 0.0.2 and leaves .release-please-manifest.json:4 at 0.0.1. On the next cli change, release-please will still treat 0.0.1 as the last released version, which can regenerate a duplicate 0.0.2 release/changelog instead of advancing from 0.0.2.
Useful? React with 👍 / 👎.
treyturner
force-pushed
the
release-please--branches--main--components--@trey.turner/artifacts-cli
branch
from
e353d80 to
476a55d
Compare
1 participant
🤖 I have created a release beep boop
0.0.2 (2026-03-19)
Dependencies
This PR was generated with Release Please. See documentation.