chore(main): release @trey.turner/artifacts-api-client 1.1.1#22
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: 8515a37019
ℹ️ 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".
| "packages/api-client": "1.1.1", | ||
| "packages/mocks-counterfact": "0.0.1", | ||
| "packages/cli": "0.0.1" | ||
| "packages/cli": "0.0.2" |
There was a problem hiding this comment.
release-please-config.json:9-12 still manages packages/cli, so changing .release-please-manifest.json to 0.0.2 here tells Release Please that CLI 0.0.2 has already been cut. However, packages/cli/package.json:3 and packages/cli/CHANGELOG.md:3 both remain at 0.0.1, so the repo no longer contains any real 0.0.2 CLI release. The next time the CLI changes, the automation will start from the wrong baseline and can skip or misnumber that package's next release.
Useful? React with 👍 / 👎.
treyturner
force-pushed
the
release-please--branches--main--components--@trey.turner/artifacts-api-client
branch
from
8515a37 to
bd2c0f8
Compare
1 participant
🤖 I have created a release beep boop
1.1.1 (2026-03-19)
Continuous Integration
This PR was generated with Release Please. See documentation.