Breaking: Disable legacy packages by default #852
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
Legacy packages may still be used with "-tags legacy" added to the build. They may be permanently removed in a future release. Signed-off-by: Brandon Mitchell <git@bmitch.net>
87b5b2e to
37fcba1
Compare
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.
Fixes issue
This is a prerequisite for #749.
Describe the change
This switches the default build tag from
!nolegacytolegacyso the packages are disabled by default. Legacy packages may still be used with-tags legacyadded to the build. However, they may be permanently removed in a future release, and migrating to the newer packages is recommended.How to verify it
No changes should be visible for users that have moved off of deprecated packages.
Changelog text
Please verify and check that the pull request fulfills the following requirements