Retire the combined RC publish workflow#4660
Open
allister-beamable wants to merge 1 commit into
Open
Conversation
CLI and Unity SDK release on independent cadences -- a Unity RC should not force a CLI cut (the RC7-vs-RC10 divergence reflected exactly this). The convenience it provided is being folded into release-unity.yml instead, which is already the npm trusted publisher, so this combined workflow is retired. 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.
Removes
.github/workflows/release-unity-rc.yml.The "one convenient job" coupled CLI and Unity SDK releases 1:1, which fights their real cadence — a Unity RC often needs no new CLI artifact, and the two version lines diverge (CLI was RC7 while Unity was RC10). It also forced a new workflow filename, which broke npm trusted publishing (keyed to
release-unity.yml).The useful pieces (auto RC number,
versions-default.jsonoverride / reuse-prior-CLI, changelog guard) are being folded intorelease-unity.ymlin a follow-up, where the npm trusted publisher already works.Already shipped via the retired workflow and kept as-is: CLI
7.2.0-PREVIEW.RC8(fully published). The orphaned Unitycom.beamable@5.1.0-PREVIEW.RC11on Nexus means the next Unity RC should be RC12.🤖 Generated with Claude Code