Bump swift-configuration dependency to 0.2.0
#43
Merged
Conversation
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
philippzagar
force-pushed
the
p-zagar/lift-swift-configuration-dependency
branch
from
5f4eb84 to
1049f18
Compare
FranzBusch
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
To be compatible with other libraries / users that depend on the most up-to-date
swift-configuration0.2, we should lift ourswift-configurationdependency as well.Modifications
Bumps
swift-configurationdependency to 0.2.0Result
All of our library users must upgrade to
swift-configuration0.2Test Plan
Verified via our CI and local tests