Skip to content

ci: installer export on unity-builder@v5 + allowDirtyBuild#11

Open
IvanMurzak wants to merge 1 commit into
mainfrom
ci/unity-builder-v5
Open

ci: installer export on unity-builder@v5 + allowDirtyBuild#11
IvanMurzak wants to merge 1 commit into
mainfrom
ci/unity-builder-v5

Conversation

@IvanMurzak

Copy link
Copy Markdown
Owner

Summary

  • Bump the installer Export step from game-ci/unity-builder@v4@v5 and add allowDirtyBuild: true.

Why

unity-builder@v4 defaults to semantic versioning and refuses to build on a dirty working tree ("Branch is dirty. Refusing to base semantic version on uncommitted changes"). After the EditMode test step runs, the Unity project leaves untracked/generated files, so the Export step failed on repos freshly created/migrated from this template. The installer's version comes from package.json (via PackageExporter), not from git, so allowDirtyBuild: true is the correct decoupling — and @v5 matches the proven Unity-MCP extension workflows.

Discovered while migrating Unity-Gyroscope-Manager / Unity-Mouse-Parallax to this template structure; both hit this and are fixed by the same change.

v4 refused a dirty working tree for semantic versioning, breaking the installer export on freshly-migrated repos. We version the installer from package.json (via PackageExporter), not git, so allowDirtyBuild is correct.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant