Release v7.16.0#1686
Merged
Merged
Conversation
kdeldycke
force-pushed
the
prepare-release
branch
3 times, most recently
from
ca9cb24 to
2e34fd7
Compare
kdeldycke
force-pushed
the
prepare-release
branch
12 times, most recently
from
6c7814f to
5fcf665
Compare
kdeldycke
force-pushed
the
prepare-release
branch
from
5fcf665 to
9ec6f09
Compare
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.
Description
This PR is ready to be merged. See the
prepare-releasejob documentation for details. The merge event will trigger the:Creation of a
v7.16.0tag onmainbranchBuild and release of the Python package to PyPI
Compilation of the project's binaries
Publication of a GitHub
v7.16.0release with all artifacts above attachedHow-to release
v7.16.0Click
Ready for reviewbutton below, to get this PR out ofDraftmodeClick
Rebase and mergebutton belowCaution
Do not
Squash and merge: we need the 2 distinct commits in this PR.Important
If you suspect the PR content is outdated, click
Run workflowto refresh it manually before merging.Workflow metadatapushmain09b3f8ddprepare-releasechangelog.yaml🏭 Generated with repomatic
6.16.0