fix: `No changesets found` error occurs when installing Unity on MacOS #747

mob-sakai · 2025-10-08T01:10:50Z

The error is caused by old unity-changeset that doesn't support GraphQL.

Changes

upgrade unity-changeset@^2.0.0 to unity-changeset@^3.0.0

Related Issues

For several Unity versions getting "No changesets found at 'https://unity.com/releases/editor/archive' and 'https://unity.com/releases/editor/lts-releases.xml'" mob-sakai/unity-changeset#21

Related PRs

None

Successful Workflow Run Link

PRs don't have access to secrets so you will need to provide a link to a successful run of the workflows from your own
repo.

None

Checklist

Read the contribution guide and accept the
code of conduct
Docs (If new inputs or outputs have been added or changes to behavior that should be documented. Please make a PR
in the documentation repo)
Readme (updated or not needed)
Tests (added, updated or not needed)
Build with npm run build

Summary by CodeRabbit

Chores
- Updated a core dependency to the latest major version to maintain compatibility and incorporate upstream improvements. No user-facing behavior changes expected.

This error is caused by old `unity-changeset` that doesn't support GraphQL.

github-actions · 2025-10-08T01:11:01Z

coderabbitai · 2025-10-08T01:11:18Z

📝 Walkthrough

Walkthrough

Updates dependency version of unity-changeset in package.json from ^2.0.0 to ^3.0.0 and adjusts end-of-file newline.

Changes

Cohort / File(s)	Summary
Dependency bump `package.json`	Upgrade `unity-changeset` from `^2.0.0` to `^3.0.0`; normalized end-of-file newline

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

GabLeRoux

Poem

I twitch my nose at version three,
A tidy hop from two to be—
Dependencies aligned just so,
Carrot commits that softly grow.
One newline tucked, we’re bounded neat,
Thump-thump: the release feels fleet! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The description covers the required sections for Changes, Related Issues, Related PRs, and Checklist with clear details on the upgrade, but the “Successful Workflow Run Link” section is left empty without a provided link to an actual workflow run.	Please update the “Successful Workflow Run Link” section with a link to a successful CI workflow execution from your own repository so that reviewers can verify the build and tests pass.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly describes the specific error being fixed (“No changesets found” on MacOS) and follows the repository’s conventional “fix:” prefix, clearly summarizing the main change in a single sentence.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 88a89c9 and 3ca788a.

⛔ Files ignored due to path filters (4)

dist/index.js is excluded by !**/dist/**
dist/index.js.map is excluded by !**/dist/**, !**/*.map
dist/licenses.txt is excluded by !**/dist/**
yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

package.json (2 hunks)

🔇 Additional comments (1)

package.json (1)

53-53: Lockfile updated
Yarn.lock now includes [email protected]; bump is applied.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

codecov · 2025-10-08T01:12:26Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.34%. Comparing base (88a89c9) to head (3ca788a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #747   +/-   ##
=======================================
  Coverage   38.34%   38.34%           
=======================================
  Files          78       78           
  Lines        3169     3169           
  Branches      663      663           
=======================================
  Hits         1215     1215           
  Misses       1809     1809           
  Partials      145      145

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

GabLeRoux · 2025-10-08T12:40:53Z

Thanks for the fix 🎉
LGTM! 🫶

While reviewing, I asked myself why this change was necessary for unity-builder but not for unity-test-runner. Short answer: The test runner doesn't support executing tests on a macos runner.

If we plan to support executing tests directly on macos, we might want to consider extracting src/model/platform-setup/setup-mac.ts (where unity-changeset is currently used) as a shared dependency, but that is out of scope for this fix.

Here's a more detailed analysis (claude-4.5-sonnet)

Analysis: Why `unity-builder` uses `unity-changeset` but `unity-test-runner` doesn't

Based on my exploration of both projects, here's the key difference:

Unity Builder - Installs Unity Editor on macOS

unity-builder has platform-specific setup that installs Unity Editor when running on macOS (and potentially other platforms). Looking at the code:

const unityChangeset = await getUnityChangeset(buildParameters.editorVersion);
const moduleArguments = SetupMac.getModuleParametersForTargetPlatform(buildParameters.targetPlatform);
const architectureArguments = SetupMac.getArchitectureParameters();

const execArguments: string[] = [
  '--',
  '--headless',
  'install',
  ...['--version', buildParameters.editorVersion],
  ...['--changeset', unityChangeset.changeset],

Key point: When installing Unity via Unity Hub CLI, you need both the version number (e.g., 2021.3.1f1) and the changeset hash (e.g., a8c0cf11e2ae) to uniquely identify and install the correct Unity Editor build.

Unity Test Runner - Uses Docker Containers

unity-test-runner has a fundamentally different architecture:

get supportedPlatforms() {
  return ['linux', 'win32'];

It only supports Linux and Windows and runs tests inside Docker containers (see Docker.run() in main.ts). It doesn't install Unity locally - it uses pre-built Docker images that already have Unity installed.

The PR Fix

The PR #747 you referenced upgrades unity-changeset from ^2.0.0 to ^3.0.0 because:

Version 2.x was failing with "No changesets found" errors on macOS
Version 3.x uses GraphQL instead of scraping HTML pages from Unity's website, making it more reliable
This issue was specific to the changeset lookup mechanism that broke when Unity changed their website structure

Summary Table

Aspect	unity-builder	unity-test-runner
Platforms	Linux, Windows, macOS	Linux, Windows only
Unity Setup	Installs Unity locally on macOS via Unity Hub CLI	Uses pre-built Docker images
Needs Changeset?	✅ Yes - required for Unity Hub installation	❌ No - Docker images already have Unity
Dependency	`unity-changeset@^3.0.0`	None

Why the Changeset is Needed

Unity Hub CLI requires the changeset hash because Unity versions aren't truly unique by version string alone. The same version number can have different builds (e.g., for hotfixes), and the changeset uniquely identifies the exact binary.

The unity-changeset package queries Unity's version database to map version strings → changeset hashes, which is exactly what breaks when Unity changes their API (hence the v2→v3 upgrade).

Since unity-test-runner never installs Unity (it just runs containers), it never needs to look up changesets, so it doesn't need this dependency.

webbertakken · 2025-10-08T14:33:35Z

We're probably going to need a similar fix in Versioning backend to fix game-ci/documentation#510

webbertakken · 2025-10-08T14:46:28Z

@mob-sakai Looks like the unity-changesets doesn't have graphql listed as a prod dependency?

Workflows are showing Error: Cannot find module 'graphql'

GabLeRoux · 2025-10-08T14:49:46Z

@mob-sakai Looks like the unity-changesets doesn't have graphql listed as a prod dependency?

Workflows are showing Error: Cannot find module 'graphql'

As a workaround, we can install the GraphQL dependency ourselves, but fixing this upstream sounds ideal.

webbertakken · 2025-10-08T14:53:13Z

I'm pressed for time atm. Can do quick replies but not PRs

ozankasikci · 2025-10-08T15:32:30Z

Workflows are showing Error: Cannot find module 'graphql'

having the same issue here, can we expect a quick fix or should we install graphql on our servers as a workaround?

webbertakken · 2025-10-08T15:45:52Z

Workaround is downgrade to v4.6.1.

But the fix should also be simple. We just need the dependency installed. or for the unity-changeset tool to include it.

ozankasikci · 2025-10-08T16:03:25Z

@webbertakken I've just opened a PR to fix the issue: #749

mob-sakai · 2025-10-08T18:52:01Z

@mob-sakai Looks like the unity-changesets doesn't have graphql listed as a prod dependency?

Workflows are showing Error: Cannot find module 'graphql'

Wow, sorry for the trouble everyone.

webbertakken · 2025-10-08T18:57:46Z

@mob-sakai no worries of course! Actually thank you so much for helping out.

Do you think it's possible to make the executable include graphql? or have it install it as a prod dev internally?

mob-sakai · 2025-10-08T19:05:44Z

Yeah, no problem! 👍
I checked and there were warnings about peer dependencies.
I missed them.

unity-builder $ yarn install

...

warning "unity-changeset > [email protected]" has unmet peer dependency "graphql@14 - 16".
warning "unity-changeset > graphql-request > @graphql-typed-document-node/[email protected]" has unmet peer dependency "graphql@^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0".

...

mob-sakai · 2025-10-08T19:26:36Z

Released as [email protected].
Should I PR this project?

$ npm view [email protected] dependencies
{
  'graphql-request': '6.1.0',
  '@deno/shim-deno': '~0.18.0',
  graphql: '^16.8.1'
}

webbertakken · 2025-10-08T19:38:33Z

It's no longer a peer dependency if it's absolutely required to run the tool.

Shall we move them to prod dependencies instead?

Looking at your second comment, that is exactly what you did. Sounds good!

webbertakken · 2025-10-08T23:17:27Z

Can confirm that 3.0.1 works as expected.

See game-ci/versioning-backend#67 and game-ci/versioning-backend#68

fix: No changesets found error occurs when installing Unity on MacOS

3ca788a

This error is caused by old `unity-changeset` that doesn't support GraphQL.

webbertakken approved these changes Oct 8, 2025

View reviewed changes

GabLeRoux approved these changes Oct 8, 2025

View reviewed changes

webbertakken merged commit 8ec161b into game-ci:main Oct 8, 2025
6 checks passed

webbertakken mentioned this pull request Oct 8, 2025

Since today Android and iOS builds fail to find graphql #748

Closed

mob-sakai deleted the fix/unity-changeset branch October 8, 2025 23:55

mob-sakai mentioned this pull request Oct 9, 2025

fix: upgrade unity-changeset to v3.0.1 for graphql dependency #750

Merged

4 tasks

coderabbitai bot mentioned this pull request Oct 11, 2025

fix: XLTS versions on MacOS are not supported #751

Merged

4 tasks

Uh oh!

fix: No changesets found error occurs when installing Unity on MacOS #747

fix: No changesets found error occurs when installing Unity on MacOS #747

Uh oh!

Conversation

mob-sakai commented Oct 8, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Related Issues

Related PRs

Successful Workflow Run Link

Checklist

Summary by CodeRabbit

Uh oh!

github-actions bot commented Oct 8, 2025

Uh oh!

coderabbitai bot commented Oct 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Suggested reviewers

Poem

Pre-merge checks and finishing touches

Uh oh!

codecov bot commented Oct 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

GabLeRoux commented Oct 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Analysis: Why unity-builder uses unity-changeset but unity-test-runner doesn't

Unity Builder - Installs Unity Editor on macOS

Unity Test Runner - Uses Docker Containers

The PR Fix

Summary Table

Why the Changeset is Needed

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

GabLeRoux commented Oct 8, 2025

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

ozankasikci commented Oct 8, 2025

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

ozankasikci commented Oct 8, 2025

Uh oh!

mob-sakai commented Oct 8, 2025

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

mob-sakai commented Oct 8, 2025

Uh oh!

mob-sakai commented Oct 8, 2025

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

webbertakken commented Oct 8, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

fix: `No changesets found` error occurs when installing Unity on MacOS #747

fix: `No changesets found` error occurs when installing Unity on MacOS #747

mob-sakai commented Oct 8, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Oct 8, 2025 •

edited

Loading

codecov bot commented Oct 8, 2025 •

edited

Loading

GabLeRoux commented Oct 8, 2025 •

edited

Loading

Analysis: Why `unity-builder` uses `unity-changeset` but `unity-test-runner` doesn't