Skip to content

release: 0.10.0 (supersedes 0.9.x)#72

Merged
Mx-Iris merged 1 commit intomainfrom
release/0.10.0
Apr 19, 2026
Merged

release: 0.10.0 (supersedes 0.9.x)#72
Mx-Iris merged 1 commit intomainfrom
release/0.10.0

Conversation

@Mx-Iris
Copy link
Copy Markdown
Member

@Mx-Iris Mx-Iris commented Apr 19, 2026

Summary

  • Bump swift-demangling dependency to 0.2.0 to pick up a critical demangling fix (the 0.1.1 pin used by 0.9.0 / 0.9.1 is known-broken).
  • Rename Changelogs/0.9.0.mdChangelogs/0.10.0.md and add a supersede notice pointing users off 0.9.x.
  • Drop Changelogs/0.9.1.md (the semantic-string release-pin patch is folded into the broader 0.10.0 notes).
  • Update README.md install snippet + CLI note to 0.10.0.
  • Bump Sources/swift-section/Version.swift placeholder to 0.10.0-dev.

Test plan

  • swift package update — resolves swift-demangling to 0.2.0
  • swift build — succeeds (0 errors, 0 linker errors)
  • After merge: tag 0.10.0, release CI builds the universal binary and publishes the GitHub release using Changelogs/0.10.0.md
  • After tag: deprecate 0.9.0 / 0.9.1 releases (edit release notes with supersede banner, mark as prerelease)

Bump swift-demangling to 0.2.0 to pick up a critical demangling fix.
0.9.0/0.9.1 shipped with swift-demangling pinned below 0.2.0 and should
not be used — 0.10.0 replaces them.

- Package.swift: swift-demangling from "0.2.0"
- Changelogs: rename 0.9.0.md -> 0.10.0.md with supersede notice,
  drop 0.9.1.md
- README: bump install snippet and CLI note to 0.10.0
- Version.swift: bump dev placeholder to 0.10.0-dev
Copilot AI review requested due to automatic review settings April 19, 2026 15:55
@Mx-Iris Mx-Iris merged commit af343fc into main Apr 19, 2026
2 checks passed
@Mx-Iris Mx-Iris deleted the release/0.10.0 branch April 19, 2026 15:55
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request bumps the project version to 0.10.0, updates the swift-demangling dependency to 0.2.0 to fix a critical bug, and consolidates release notes. The review identifies a version mismatch for MachOKit between the changelog and the package manifest, and suggests including the swift-semantic-string fix details in the new changelog since the previous version's file was removed.

Comment thread Changelogs/0.10.0.md
@@ -1,9 +1,16 @@
# 0.9.0
# 0.10.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There is a version discrepancy between the changelog and the package manifest. Line 54 of this file states that MachOKit was bumped to 0.47.100, but the Package.swift manifest still references 0.46.1 (line 100) and 0.46.100 (line 189). Please ensure the manifest is updated to match the release notes or correct the changelog if the bump was not intended for this release.

Comment thread Changelogs/0.10.0.md

## Bug Fixes

- **Demangling**: bumped `swift-demangling` to `0.2.0` to pick up a critical fix. `0.9.0` / `0.9.1` pinned `0.1.1`, which shipped the bug and must be avoided.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The PR description indicates that the 0.9.1 fixes are folded into these notes, but the specific details regarding the swift-semantic-string pin (which is critical for x86_64 universal builds) are missing. Since Changelogs/0.9.1.md is being removed, this information should be preserved here to maintain a complete history of fixes.

Suggested change
- **Demangling**: bumped `swift-demangling` to `0.2.0` to pick up a critical fix. `0.9.0` / `0.9.1` pinned `0.1.1`, which shipped the bug and must be avoided.
- **Demangling**: bumped `swift-demangling` to `0.2.0` to pick up a critical fix. `0.9.0` / `0.9.1` pinned `0.1.1`, which shipped the bug and must be avoided.
- **Release workflow**: pinned `swift-semantic-string` to `0.1.1` to fix universal binary builds on x86_64 (restores macOS 10.15 deployment target for concurrency support).

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Prepares the 0.10.0 release, superseding 0.9.x, by bumping a critical demangling dependency and updating versioning/docs accordingly.

Changes:

  • Bump swift-demangling dependency requirement to 0.2.0.
  • Update README install snippet and CLI note to reference 0.10.0.
  • Update bundled development version placeholder and refresh release notes in Changelogs/0.10.0.md (including supersede notice and updated Known Issues link).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
Package.swift Updates swift-demangling dependency requirement to from: "0.2.0".
README.md Updates SwiftPM install snippet and CLI behavior note to 0.10.0.
Sources/swift-section/Version.swift Bumps local development placeholder version to 0.10.0-dev.
Changelogs/0.9.1.md Removes the 0.9.1 changelog entry.
Changelogs/0.10.0.md Renames/updates release notes for 0.10.0, adds supersede warning + dependency fix note, and updates Known Issues link tag.
Comments suppressed due to low confidence (1)

Changelogs/0.10.0.md:4

  • The warning banner says the 0.9.x tags were pinned below 0.2.0, "which contains a critical demangling bug". This reads as if 0.2.0 contains the bug, but later in the same changelog you correctly state that 0.2.0 contains the fix and 0.1.1 shipped the bug. Please reword this sentence to avoid implying 0.2.0 is the broken release (e.g., say the bug is fixed in 0.2.0 / present in 0.1.1).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants