Bump to v2.0.0, require Swift 6.3, remove CocoaPods support#201
Draft
Bump to v2.0.0, require Swift 6.3, remove CocoaPods support#201
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #201 +/- ##
==========================================
- Coverage 99.91% 99.91% -0.01%
==========================================
Files 36 36
Lines 3470 3455 -15
==========================================
- Hits 3467 3452 -15
Misses 3 3
🚀 New features to boost your workflow:
|
dfed
force-pushed
the
dfed/major-version-bump
branch
from
04848cc to
0c42a56
Compare
dfed
commented
Mar 30, 2026
dfed
force-pushed
the
dfed/major-version-bump
branch
2 times, most recently
from
e965a84 to
95c3b8b
Compare
- Version 1.5.4 → 2.0.0 - swift-tools-version 6.0 → 6.3 - swift-syntax range 600..<604 → 603..<605 - Remove deprecated CSV configuration file support (replaced by @SafeDIConfiguration macro) - Update CI to macOS-26 runner with Xcode 26.4, swift:6.3 container - Update SwiftFormat to 0.60.1, add trailing-commas and test-case-name-format options - Update README with v2.0 dependency examples and Swift 6.3 requirement note Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Provides `swift package plugin safedi-v1-to-v2 --target <TargetName>` to help users migrate from SafeDI 1.x to 2.x. The plugin validates the swift-tools-version, migrates CSV configuration files to a @SafeDIConfiguration enum, and creates the configuration file if one doesn't already exist. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
dfed
force-pushed
the
dfed/major-version-bump
branch
from
fff5373 to
e162219
Compare
dfed
changed the title
When an existing @SafeDIConfiguration file was found, the plugin warned that CSV values must be manually migrated, but then unconditionally deleted the CSV files — destroying the data the user needs to migrate. Move CSV deletion inside the else branch so it only runs when the plugin successfully creates the new configuration file. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@SafeDIConfigurationmacro in Add @SafeDIConfiguration macro to replace CSV config #199)MigrateSafeDIFromVersionOnecommand plugin (swift package plugin safedi-v1-to-v2 --target <Target>) to automate migration from 1.x to 2.xtrailing-commasandtest-case-name-formatoptionsUnexpectedNodesSyntaxdetection explaining its SwiftSyntax 602 originsTest plan
swift buildpasses locallyswift test -c release— all 363 tests pass./lint.shpasses (with manual fix for SwiftFormat hoistTry bug in multiline string interpolation)🤖 Generated with Claude Code