Add RC conveniences to release-unity.yml#4661
Open
allister-beamable wants to merge 1 commit into
Open
Conversation
Fold the useful pieces of the retired combined workflow into the real Unity release, keeping CLI and Unity decoupled and the npm trusted publisher intact: - nugetVersion input: jq-writes versions-default.json at build time so the bundled CLI version no longer needs a hand-edit of the deep file. Blank keeps the SDK's current dependency, i.e. reuse the previous CLI artifact when the CLI has not changed. - rcNumber 0 (the default) auto-derives the next RC from existing tags for the rc release type; an explicit rcNumber wins. - Fail-fast changelog guard for rc/production: the changelog top entry must match the version line being cut, checked before any build. Non-rc modes (nightly/exp/production) are unchanged except the shared changelog guard, which runs only for rc and production. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folds the useful parts of the (now retired, #4660) combined RC workflow into the real Release Unity SDK workflow — keeping CLI and Unity decoupled, and keeping the npm trusted publisher intact (this is the trusted filename, so public-npm publishing keeps working).
Changes
1.
nugetVersioninput (the deep-file fix + reuse-prior-CLI)Optional. When set, jq-writes
nugetPackageVersioninversions-default.jsonat build time — no more hand-editing that deeply-nested file. Blank keeps the SDK's current dependency, i.e. reuse the previous CLI artifact when the CLI has not changed (per Chris). Provide a value only when bundling a freshly cut CLI.2. Auto RC number
For
releaseType: rc,rcNumber: 0(the default) derives the next RC from existingunity-sdk-<maj.min.patch>-PREVIEW.RC*tags (read viagit ls-remote, so a shallow clone is fine). An explicitrcNumber > 0always wins. Cut RC2..N without tracking the number.3. Fail-fast changelog guard
For
rc/production, the changelog's top## [x.y.z]entry must matchmajor.minor.patch, checked right after checkout before any build. nightly/exp are unaffected.Notes
com.beamable@5.1.0-PREVIEW.RC11on Nexus (from the retired workflow) means auto-RC would compute11and collide. Cut the next Unity RC withrcNumber: 12explicitly until that line moves on.🤖 Generated with Claude Code