Repository navigation
Conversation
…ps#487) RELEASING.md sets the naming for branches (dev, main, release/X.Y.Z, type/issue-slug), tags (vX.Y.Z and vX.Y.Z-alphaN/betaN/rcN) and release titles, and the steps to cut a prerelease and a final release. CONTRIBUTING.md links to it and describes work branch names. build.ps1 stops a Prerelease, Release or PSGalleryRetry build unless it runs from release/<ModuleVersion>, -GitHubPreTag matches the manifest Prerelease (prerelease builds), and Prerelease is cleared (release builds). -GitHubPreTag accepts alpha, beta and rc followed by a number. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main now has its own ruleset (no deletion, fast-forward only), so the release step fast-forwards it with a push. Merging the release branch back into dev is removed: the dev ruleset requires pull requests and linear history. Cutting a release branch now merges the previous release tag with -s ours, which changes no files but keeps each release a descendant of the last so main can fast-forward. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Branch, tag and release names had drifted, and nothing documented how a release is cut.
RELEASING.mddefines thedev,main,release/X.Y.Zandtype/issue-slugbranches, thevX.Y.ZandvX.Y.Z-alphaN/-betaN/-rcNtags, the release title, and the steps for a prerelease and a final release.CONTRIBUTING.mdlinks to it and states the work branch format.build.ps1now stops a Prerelease, Release or PSGalleryRetry build that breaks those rules, before anything is published.build.ps1 checks
release/<ModuleVersion>.-GitHubPreTagis required and must equal the manifestPrerelease, case-sensitive. This was checked only when-GalleryKeywas given.Prereleasemust be empty.-GitHubPreTagacceptsalpha,betaorrcfollowed by a number from 1. It accepted only analphaprefix.The check block ran against stubbed branch and manifest data for 8 cases, each passing or stopping as intended.
The tag pattern rejects
rc.1,RC1,rc0andpreview1.Follow-ups
prerelease/0.63.0-rc1. The final 0.63.0 build needsrelease/0.63.0cut fromv0.63.0-rc1with this change cherry-picked, orbuild.ps1will stop it.mainwas realigned tov0.62.1(0f6cc718). Its 19 older commits each have an identical patch indev, so no code was lost.mainnow has its ownProtect mainruleset: no deletion, fast-forward only.Protect devis unchanged except that it no longer coversmain.-s ours, so each release descends from the last andmaincan fast-forward.0.63.0 -- unreleasedheading that feat: add 825 REST cmdlets #482 also adds, so expect a small conflict there.Closes #487.