ci: include dependency on tools package to bump package versions - #58
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: de4179957d
ℹ️ 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".
| @@ -1,5 +1,6 @@ | |||
| { | |||
| "bump-minor-pre-major": true, | |||
| "plugins": ["node-workspace"], | |||
There was a problem hiding this comment.
When a commit changes only packages/tools, the default node-workspace behavior will not bump CLI or MCP because both declare @testplane/tools as "*", which already satisfies every new tools version. The release therefore creates only a private tools release, while the workflow's cli_release_created and mcp_release_created outputs remain false and neither publish job runs, so users do not receive the tools change. Configure the plugin with its always-link-local option (or use dependency ranges that become outdated) so tools releases force consumer releases.
Useful? React with 👍 / 👎.
1 participant
No description provided.