Skip to content

chore: release 0.6.0#12

Merged
Zakariya1057 merged 1 commit into
mainfrom
chore/release-0.6.0
May 29, 2026
Merged

chore: release 0.6.0#12
Zakariya1057 merged 1 commit into
mainfrom
chore/release-0.6.0

Conversation

@Zakariya1057

Copy link
Copy Markdown
Collaborator

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:

Per the pre-1.0 rule (breaking ⇒ minor), that bumps 0.5.1 → 0.6.0.

Changes

  • Sources/PolyMessaging/Public/Version.swift: 0.5.10.6.0 (and reworded the doc comment now that bumps are manual)
  • CHANGELOG.md: add the 0.6.0 entry documenting the breaking environment default
  • Remove now-orphaned ​.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):

git tag v0.6.0 && git push origin v0.6.0

SPM consumers resolve that tag.

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)
@Zakariya1057 Zakariya1057 merged commit 1c025eb into main May 29, 2026
2 checks passed
@Zakariya1057 Zakariya1057 deleted the chore/release-0.6.0 branch May 29, 2026 15:10
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