chore: release 0.6.0#12
Merged
Merged
Conversation
Manual version bump, replacing the release-please automation removed in #11 (org policy blocks GitHub Actions from opening PRs, so it failed on every push to main). - Version.swift: 0.5.1 -> 0.6.0 (one feat! since v0.5.1 -> minor bump pre-1.0) - CHANGELOG.md: document the breaking Configuration.environment default change - remove now-orphaned release-please config (manifest + config json)
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.
Manual 0.6.0 release PR — the hand-rolled equivalent of the release-please "Release PR" we just removed in #11 (org policy blocks GitHub Actions from creating PRs, so release-please failed on every push to
main).What's in this release
One release-worthy commit since
v0.5.1:feat!: default Configuration.environment to .us, add named production regions(feat!: default Configuration.environment to .us, add named production regions #10)Per the pre-1.0 rule (breaking ⇒ minor), that bumps 0.5.1 → 0.6.0.
Changes
Sources/PolyMessaging/Public/Version.swift:0.5.1→0.6.0(and reworded the doc comment now that bumps are manual)CHANGELOG.md: add the0.6.0entry documenting the breakingenvironmentdefault.release-please-manifest.json+release-please-config.json(their workflow is gone)On merge
Tag the release manually (this is what release-please used to do):
SPM consumers resolve that tag.