Skip to content

fix: XLTS versions on MacOS are not supported #751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 11, 2025
+51 −92
Merged

fix: XLTS versions on MacOS are not supported #751

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
131 changes: 45 additions & 86 deletions dist/index.js
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion dist/index.js.map
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@
"reflect-metadata": "^0.1.13",
"semver": "^7.5.2",
"ts-md5": "^1.3.1",
"unity-changeset": "^3.0.1",
"unity-changeset": "^3.1.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Update the lockfile to pull 3.1.0.

Bumping the semver range in package.json isn’t enough on its own—Yarn will keep resolving to the existing 3.0.1 pinned in yarn.lock. Please regenerate and commit the lockfile (or otherwise ensure the bundled unity-changeset version actually moves to 3.1.0); without that, the XLTS fix never ships.

🤖 Prompt for AI Agents 
In package.json around line 53, the semver was bumped to "unity-changeset":
"^3.1.0" but the lockfile still pins 3.0.1; regenerate and commit the updated
lockfile so Yarn actually resolves to 3.1.0. Run yarn install (or yarn upgrade
unity-changeset@^3.1.0), verify yarn.lock now contains 3.1.0, run tests/build,
and commit the updated yarn.lock (or the appropriate lockfile) alongside this
package.json change.

"uuid": "^9.0.0",
"yaml": "^2.2.2"
},
Expand Down
8 changes: 4 additions & 4 deletions yarn.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7681,10 +7681,10 @@ undici@^5.25.4:
dependencies:
"@fastify/busboy" "^2.0.0"

unity-changeset@^3.0.1:
version "3.0.1"
resolved "https://registry.yarnpkg.com/unity-changeset/-/unity-changeset-3.0.1.tgz#47c964878c53d27da571c7c350dac8edf8cdc8a4"
integrity sha512-3GVbZuOusSLPADIE5yvMcNrlkt0MGFNARWe4hU0Y+MNMlvuSRBPTvtz0h+UUzQzRD07d/lj4LkIj3YwxBdEuQg==
unity-changeset@^3.1.0:
version "3.1.0"
resolved "https://registry.yarnpkg.com/unity-changeset/-/unity-changeset-3.1.0.tgz#7217915b995f1c441d8bdb1045c45c09f64ca94a"
integrity sha512-bFqaq3yuxeMROwqw81fi6S2f8l+4lracvnW8SkdJLGDx+QvWxQhjK4LsGYM19/plDDh7q3MwEbzQgmcqj5uxBg==
dependencies:
"@deno/shim-deno" "~0.18.0"
graphql "^16.8.1"
Expand Down
Loading