[agoldis]

Owner: @agoldis
Linear: ENG-1981

@currents/cmd depends on @currents/rules through ^0.1.0. Any new 0.1.x release of @currents/rules on npm reaches every install of @currents/cmd without a lockfile and every lockfile refresh, with no release of @currents/cmd.

This pins @currents/rules to 0.1.0, the version in packages/rules and on npm, the same way @currents/commit-info is pinned. In this repo @currents/rules still links to the workspace package. When packages/rules gets a new version, packages/cmd must be bumped to it in the same change.

No other published package in this repo uses a range for a @currents/* dependency.

The fix reaches users with the next patch release of @currents/cmd.

🤖 Generated with Claude Code

https://claude.ai/code/session_011baD3gbpQpnPQBzH1BRtK8

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[baz-reviewer]

Baz Summary

Pin @currents/cmd’s @currents/rules dependency to 0.1.0 so unreviewed patch releases cannot reach users without a new command-package release. Update the workspace lockfile consistently with the package manifest.

Latest Contributors(2)

User	Commit	Date
agoldis@gmail.com	fix: pin @currents/rul...	October 31, 2026
maxi@currents.dev	Merge pull request #46...	October 27, 2026

---

Merger   ✅ Ready to Merge

The focused dependency change pins @currents/rules from ^0.1.0 to 0.1.0 as described. CI ran and there are no open discussions or concrete blockers.

---

  _{Activate Skill Maintainer to keep your skills up to date}

  _{This PR would have been improved with Baz Planner - Try it now}