Skip to content

Allow prerelease builds from any branch to publish to the nightly feed - #1099

Merged
KevinJump merged 1 commit into
v17/mainfrom
chore/prerelease-from-branches
Sep 30, 2026
Merged

KevinJump merged 1 commit into
v17/mainfrom
chore/prerelease-from-branches

Conversation

@KevinJump

Copy link
Copy Markdown
Owner

publish-nightly in prerelease.yml only ran from v17/main, so a /pre-release run from a feature branch built and packed but never reached the nightly feed. It was skipped in this run.

Change

  • publish-nightly runs from any branch. The workflow is workflow_dispatch only, so nothing publishes unless someone runs it.

  • Branch builds get their own version label, so they can't be mistaken for main nightlies:

    • v17/main: 17.4.3-prerelease.{date}.{run} (unchanged)
    • other branches: 17.4.3-branch.{branch}.{date}.{run}, e.g. 17.4.3-branch.fix-block-draft-matches-publish.20260930.14

    The branch name is reduced to [0-9A-Za-z-] so it's a valid SemVer identifier. branch sorts below prerelease, so a floating prerelease range will still resolve to a main nightly and not a branch build.

Notes

  • v18/main has its own copy of this workflow and will need the same change when this is forward-ported.
  • This commit is also cherry-picked onto fix/block-draft-matches-publish (Imported block values match what Umbraco publishes (#1097) #1098) so that branch can be pre-released now. Git will treat the two as the same change when both merge.

🤖 Generated with Claude Code

publish-nightly was limited to v17/main, so a prerelease run from a feature
branch built and packed but never reached the feed. The workflow is manual
only, so let any branch publish.

To keep branch builds distinguishable from main nightlies, non-main branches
are versioned "{version}-branch.{branch}.{date}.{run}" instead of
"{version}-prerelease.{date}.{run}". They sort below main nightlies, so a
floating prerelease range won't pick one up by accident.

Co-Authored-By: Claude Opus 5.5 <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