Commit bd5dde2
authored
fix(release): stop node-workspace from clobbering manual dependency ranges (#5740)
release-please's node-workspace plugin defaults to always-link-local: true,
which force-rewrites every workspace-internal dependency's semver range on
every regeneration of a release branch -- even when the current range
already satisfies the sibling's version. This has repeatedly clobbered
deliberate, manually-set constraints on @loopover/miner's and
@loopover/mcp's @loopover/engine dependency back to a bare "*" (most
recently caught by the repo's security scanner on #5730, PR #5729 before
that), and separately generated a string of "empty" release PRs
(mcp-v0.8.1, mcp-v1.0.1, miner-v2.0.1) that exist purely to speculatively
cross-bump a dependency range ahead of the sibling's actual publish, with
no real content of their own.
Setting always-link-local: false (a documented top-level manifest option,
confirmed against release-please's own JSON schema) makes the plugin only
touch a workspace dependency when the CURRENT range no longer covers the
sibling's version -- i.e. only for a genuine breaking change, which is
exactly when a deliberate, manually-verified bump is warranted anyway
(the judgment call this session has been making by hand every time this
came up).
Also fixes apps/gittensory-ui/src/lib/mcp-package.ts's
MCP_PACKAGE_KNOWN_LATEST_VERSION, stale against mcp's real just-published
0.9.0 (unrelated to the config change, but blocking this branch's own
gate via ui:version-audit).1 parent 90e2f75 commit bd5dde2
2 files changed
Lines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
| 28 | + | |
28 | 29 | | |
29 | 30 | | |
30 | 31 | | |
| |||
0 commit comments