Fixes for that default to @MainActor in Swift 6.2+

[mergesort]

We all love Swift Concurrency don't we?

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

[chatgpt-codex-connector]

[P0] Constrain types to nonexistent SendableMetatype

The change introduces a new SendableMetatype requirement on StorableItem (and AsyncValueSubject) but no such protocol or type alias exists anywhere in the repository or in Swift’s standard library. Adding this constraint causes every use of StorableItem or AsyncValueSubject to fail to compile because the compiler cannot resolve SendableMetatype. Unless a definition and conformances are provided, the package will not build.

Useful? React with 👍 / 👎.

[mergesort]

@codex fix the fact that this isn't backwards compatible. I just realized that this fix will only work when the Swift compiler is 6.2+, so please conditionally compile the type changes made only when the compiler is 6.2+, otherwise keep the StorableItem type as it previously was.

[chatgpt-codex-connector]

Summary

• Wrapped the StorableItem type alias in a compiler version check so Swift < 6.2 retains the older Codable & Sendable constraint while Swift ≥ 6.2 adds SendableMetatype. Sources/Boutique/StorableItem.swiftL1-L5
• Introduced a shared AsyncValueSubjectValueConstraint alias so AsyncValueSubject only requires SendableMetatype when building with Swift 6.2 or newer. Sources/Boutique/Internal/AsyncValueSubject.swiftL1-L9

Testing

• ⚠️ swift test (fails: HTTP 403 while cloning remote dependencies)

View task →