Set version range in manifest, up to local swift version to resolve#22
Conversation
|
Sorry I've not looked at his yet, I've been swamped 😄 I will look at this properly when I get the chance. The main thing I want to check is that the macro actually compiles and tests pass when using all of these different versions (or at least the latest of major version). |
No problem at all! I haven't had much chance to look into this myself. Appreciate you looking 👍 |
JosephDuffy
left a comment
There was a problem hiding this comment.
Just need to check CI works so may push more commits.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22 +/- ##
==========================================
- Coverage 98.80% 98.58% -0.22%
==========================================
Files 12 12
Lines 3752 2976 -776
==========================================
- Hits 3707 2934 -773
+ Misses 45 42 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Maybe it will need `use_oidc`?
1.0.1 is very old. Support for parsing `swift test` output (or specifically Swift Testing?) was in 2.12.0.
It actually support Swift 5.9, but we just need down to 6.0 right now
ba13beb to
c3573a9
Compare
|
Sorry for the delay @SixFiveSoftware. Thanks for the suggestion! There were some changes necessary so I'm glad I checked, this approach will hopefully work well for future changes too. I'll push a new tag. |
Here's the PR to set the version to a range. It looks like depending on your local Swift version, it will pick the version compatible with your current toolchain, according to their GitHub repo.