-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Delete Examples/package-info
directory as outdated
#7434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
This example package was created many years ago during an initial attempt of versioning SwiftPM with semver. That approach has been abandoned since then, and SwiftPM doesn't provide any stable API outside of `PackageDescription` and `PackagePlugin` modules. This example code can mislead users of SwiftPM to believe that it can be consumed as a library and provide a stable API in other modules, which is currently not the case.
@swift-ci test |
@swift-ci test |
Examples/package-info
directoryExamples/package-info
directory as outdated
@swift-ci test windows |
bnbarham
approved these changes
Apr 2, 2024
furby-tm
pushed a commit
to wabiverse/swift-package-manager
that referenced
this pull request
May 15, 2024
This example package was created many years ago during an initial attempt of versioning SwiftPM with semver. That approach has been abandoned since then, and SwiftPM doesn't provide any stable API outside of `PackageDescription` and `PackagePlugin` modules. This example code can mislead users of SwiftPM to believe that it can be consumed as a library with a stable API in other modules, which is currently not the case.
furby-tm
pushed a commit
to wabiverse/swift-package-manager
that referenced
this pull request
May 15, 2024
This example package was created many years ago during an initial attempt of versioning SwiftPM with semver. That approach has been abandoned since then, and SwiftPM doesn't provide any stable API outside of `PackageDescription` and `PackagePlugin` modules. This example code can mislead users of SwiftPM to believe that it can be consumed as a library with a stable API in other modules, which is currently not the case.
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.
This example package was created many years ago during an initial attempt of versioning SwiftPM with semver. That approach has been abandoned since then, and SwiftPM doesn't provide any stable API outside of
PackageDescription
andPackagePlugin
modules.This example code can mislead users of SwiftPM to believe that it can be consumed as a library with a stable API in other modules, which is currently not the case.