Small docs/release.rst update, mainly to remove git push --tags.
#5748
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
Improve release documentation safety and clarity
Problem
The current release documentation has potential safety issues and unclear instructions:
git push --tagswhich pushes ALL local tags (potentially including experimental/unwanted tags)origin,upstream)Changes
git push --tagswith specificgit push upstream vX.Y.Zcommandgit push --tags!" to prevent accidental tag pushesupstreamrefers tohttps://github.com/pybind/pybind11.gitupstreamremote consistentlyWhy this matters
Using
git push --tagsin release documentation is dangerous because:Suggested changelog entry:
📚 Documentation preview 📚: https://pybind11--5748.org.readthedocs.build/