History

Release next version as patch (1.5.x), not major

The unified-auth changeset cascaded to a 2.0.0 major release: four fixed-group plugins (openapi, mcp, graphql, onepassword) declare @executor-js/react as a peerDependency, and changesets' default rule major-bumps any package whose peerDependency changes. The fixed group then propagated that major to every member. - Set the changeset bumps to patch. - Enable onlyUpdatePeerDependentsWhenOutOfRange so peer-dependents only major-bump when the new version leaves the declared range (workspace:* always satisfies, so no forced major).

Rhys Sullivan committed 5 months ago

Commit 616e37d1 parent c92bbda2 files · +5 −2Browse files

Unified · Split

2 files
  1. .changeset/config.json +3 −0
  2. .changeset/unified-auth-methods.md +2 −2
.changeset/config.json+3−0
@@ -25,6 +25,9 @@ · 24 unmodified lines
2525 "access": "public",
2626 "baseBranch": "main",
2727 "updateInternalDependencies": "patch",
28+ "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
29+ "onlyUpdatePeerDependentsWhenOutOfRange": true
30+ },
2831 "ignore": [
2932 "@executor-js/local",
3033 "@executor-js/host-mcp",
.changeset/unified-auth-methods.md+2−2
@@ -1,6 +1,6 @@
11 ---
2−"executor": minor
3−"@executor-js/react": minor
2+"executor": patch
3+"@executor-js/react": patch
44 ---
55
66 **One auth model across OpenAPI, GraphQL, and MCP**