docs: document what happened to build tags in v3#2358
Open
dearchap wants to merge 1 commit into
Open
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
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.
What type of PR is this?
What this PR does / why we need it:
Adds a "Build Tags" section to the v2→v3 migration guide explaining that the
urfave_cli_no_docsandurfave_cli_no_suggestbuild tags from v2 are not available in v3 because they are no longer necessary:github.com/urfave/cli-docs/v3)embed.FS(zero deps)Binary size in v3 is managed through architectural simplification rather than build tags.
Which issue(s) this PR fixes:
Fixes #2304
Special notes for your reviewer:
Only
docs/migrate-v2-to-v3.mdwas modified.Testing
Rendered the markdown locally to verify formatting.
Release Notes