chore(release): bump version to 10.0.0-rc.14 - #229
Merged
Conversation
Cuts the release documented under [Unreleased]: the release.yml failures that broke every tag-triggered publish since the npm Trusted Publishing migration, the npm dist-tag rule, and the flex-fields dark-theme and ng-zorro peer-range fixes. Moves the lockstep version in Directory.Build.props and all five Angular package.json files, including the two intra-repo sibling ranges in flex-fields-ckeditor and flex-fields-file-explorer that verify-version-lockstep.ps1 requires to track the release version.
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.
Cuts
10.0.0-rc.14, releasing everything that had accumulated under CHANGELOG's[Unreleased]:release.ymlfailures that broke every tag-triggered publish since the npm Trusted Publishing migration (theregistry-url/NODE_AUTH_TOKENcrash, the missing--tagon the GitHub Packages publish, and the.npmrccorruption that broke npmjs OIDC);build/resolve-npm-dist-tag.mjsletting a pre-release take npm'slatestwhile no stable release exists, plus the post-publish single-copy verification;ng-zorro-antdpeer range widened to the whole21.xline (Angular: @dignite/ng.flex-fields' ng-zorro-antd peer range caps consumers at 21.0.x #220), the intra-repo sibling ranges that let consumers install two copies of@dignite/ng.flex-fields(Angular: consumers install two copies of @dignite/ng.flex-fields, silently breaking field-type registration #211), and the CKEditor / Select / Tree dark-theme work.Version moves (lockstep)
<Version>inDirectory.Build.props—10.0.0-rc.13→10.0.0-rc.14.<AssemblyVersion>stays pinned at1.0.0.0.versionin all five Angularpackage.jsonfiles.@dignite/*intra-repo dependency ranges inflex-fields-ckeditorandflex-fields-file-explorer→^10.0.0-rc.14, whichverify-version-lockstep.ps1requires to track the release version.verify-version-lockstep.ps1 -Tag v10.0.0-rc.14passes locally.No source changes — CHANGELOG and version strings only. rc.13 published cleanly to both NuGet.org and npm, so this is a normal next release rather than a re-cut.
After merge:
git tag v10.0.0-rc.14 && git push origin v10.0.0-rc.14to triggerrelease.yml.