Introduced additional package version strategies #2
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
kstanikviacbs
force-pushed
the
feature/additional_package_version_strategies
branch
from
1a1cfd3 to
a33adb6
Compare
kstanikviacbs
changed the title
kstanikviacbs
force-pushed
the
feature/additional_package_version_strategies
branch
from
a33adb6 to
2017102
Compare
Introduced upToNextMajor, upToNextMinor, branch and revision versioning strategies.
kstanikviacbs
force-pushed
the
feature/additional_package_version_strategies
branch
from
2017102 to
a03f442
Compare
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.
🚀 Description
Current implementation hardcodes and thus supports only one package versioning strategy -
from.Use cases of plugin might require support whole bunch of different versioning strategies described here:
https://docs.swift.org/package-manager/PackageDescription/PackageDescription.html
📄 Motivation and Context
This change attempts to introduce supporting them while still keeping plugin UX friendly.
🧪 How Has This Been Tested?
I haven't introduced any additional unit tests to cover new logic, instead - performed smoke tests across all new strategies locally. Please do let me know if additional coverage is required.
📦 Types of changes
✅ Checklist