Revert 2.0.0 release and re-release as 1.5.23 patch#1199
Conversation
This reverts commit a7d4603.
The update-available-notifications changeset marked @executor-js/api and @executor-js/react as minor. With the changesets fixed group, any minor in the release escalates the whole fixed group to a major bump, which is what produced the unintended 2.0.0. Setting every entry to patch keeps the re-release a 1.5.23 patch.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 7e45912 | Commit Preview URL Branch Preview URL |
Jun 29 2026, 01:23 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 7e45912 | Jun 29 2026, 01:23 AM |
Cloudflare previewTorn down — the PR is closed. |
Greptile SummaryThis PR reverts the unintended
Confidence Score: 5/5Safe to merge; the change is a mechanical revert of version metadata with no runtime code touched. All five restored changesets are correctly marked No files require special attention; the changeset bump types and all package versions are internally consistent. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["PR #1171 Version Packages\n(consumed changesets)"] -->|"update-available-notifications\nmarked api + react as **minor**"| B["Fixed-group escalation:\nminor → major bump"]
B --> C["Unintended 2.0.0 release\npublished to npm"]
subgraph "This PR — revert + requeue"
D["Restore 5 changesets\n(cimd-org-redirect-uri\ndesktop-background-service-consent-seam\ndesktop-sidecar-auth-token-dash\ngraphql-valid-selections\nupdate-available-notifications)"]
E["Downgrade ALL bump types\nto **patch**"]
F["Roll back package.json versions\ne.g. executor 2.0.0 → 1.5.22\n@executor-js/sdk 2.0.0 → 1.5.22\n@executor-js/api 1.5.0 → 1.4.42"]
G["Update bun.lock\nto match reverted versions"]
D --> E --> F --> G
end
C -->|revert| D
G --> H["Changesets bot queues\nfresh Version Packages PR\n→ clean 1.5.23 patch"]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A["PR #1171 Version Packages\n(consumed changesets)"] -->|"update-available-notifications\nmarked api + react as **minor**"| B["Fixed-group escalation:\nminor → major bump"]
B --> C["Unintended 2.0.0 release\npublished to npm"]
subgraph "This PR — revert + requeue"
D["Restore 5 changesets\n(cimd-org-redirect-uri\ndesktop-background-service-consent-seam\ndesktop-sidecar-auth-token-dash\ngraphql-valid-selections\nupdate-available-notifications)"]
E["Downgrade ALL bump types\nto **patch**"]
F["Roll back package.json versions\ne.g. executor 2.0.0 → 1.5.22\n@executor-js/sdk 2.0.0 → 1.5.22\n@executor-js/api 1.5.0 → 1.4.42"]
G["Update bun.lock\nto match reverted versions"]
D --> E --> F --> G
end
C -->|revert| D
G --> H["Changesets bot queues\nfresh Version Packages PR\n→ clean 1.5.23 patch"]
Reviews (1): Last reviewed commit: "Release changesets as patch to avoid fix..." | Re-trigger Greptile |
What
Reverts the
Version Packages (#1171)commit, which bumped the fixed package group to a2.0.0major and published it. The major was unintended: no changeset declared a major bump.Why 2.0.0 happened
The release changesets were all patch/minor. The
update-available-notificationschangeset marked@executor-js/apiand@executor-js/react(outside the changesetsfixedgroup) asminor. With thefixedgroup present, any minor in the release escalates the entire fixed group to a major bump, producing2.0.0instead of a normal patch/minor.This PR
patch, so the re-release is a clean1.5.23patch with no fixed-group escalation.changeset statusafter this change: all affected packages bump at patch, none at minor or major.Merging this resets the published version state on
mainand queues a fresh1.5.23Version Packages PR.