docs: update README release process for release-please - #450
Merged
Conversation
The manual scripts/release.sh + github-changelog-generator flow was replaced by release-please (#448); point the Development "release" step and the Changelog note at it.
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.
Follow-up to #448: the
## Developmentrelease step and the## Changelognote still described the removedscripts/release.sh+ github-changelog-generator flow. This points them at release-please.Also done out of band: the now-unused
pypi_passwordandtest_pypi_passwordActions secrets were deleted, so OIDC trusted publishing is the only publish path (no token fallback).