Usage blocked by minimum macOS version

[tristanlabelle]

Recent versions of the SemanticVersion dependency now require macos 13.0. Because this project declares requiring macos 11.0, we get a build error that a project requiring 11.0 cannot depend on one requiring 13.0. Could we bump or remove the version requirement from this project?

error: the library 'ReleaseNotesCore' requires macos 11.0, but depends on the product 'SemanticVersion' which requires macos 13.0; consider changing the library 'ReleaseNotesCore' to require macos 13.0 or later, or the product 'SemanticVersion' to require macos 11.0 or earlier.

[finestructure]

We specifically had to require macOS 13+ when we dropped Foundation (NSRegex) recently, to simplify things (the package had two different regex code paths).

There were no functional changes at all (and there are unlikely to be any in the future). If you pin your version requirement to <=0.4.0 everything should keep working as it was!

[tristanlabelle]

@finestructure We have a large project and it's hard to keep track of the rationale behind why pinning a certain dependency was ok, and be confident that we're not missing on bug or security fixes in the future (we auto-bump unpinned deps). It would be much better to have a solution that doesn't require us to pin, such as updating this repo to depend on macos 13 like its dependency. Is that solution problematic?

[finestructure]

What we typically do is add a comment to the .package(...) clause where we pin a version as a reminder as to why it was pinned.

I'm afraid that's the best I can offer, because we cannot revert the change where we dropped Foundation (and NSRegex) in favour of the new Regex support (which requires macOS 13+). I went back and checked and the reason was so we are compatible with Wasm.

Hope that helps!

[tristanlabelle]

Bummer, but thanks for the support!