ci: Fix release-please workflow #205
Open
Conversation
This file contains 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
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.
This pull request includes updates to the release workflow configuration and the release-please configuration file. The most important changes are adjustments to the GitHub Actions workflow for handling releases and social media announcements.
fixes #203
Updates to release workflow configuration:
.github/workflows/release-please.yml: Updated the action used for releases fromGoogleCloudPlatform/release-please-actiontogoogleapis/release-please-actionand added the GitHub token input..github/workflows/release-please.yml: Changed the command used for social media announcements fromnpx @humanwhocodes/tweettonpx @humanwhocodes/crosspostto support multiple platforms, and updated the environment variables for Twitter and added new ones for Mastodon and Bluesky.Updates to release-please configuration:
release-please-config.json: Added abootstrap-shaentry to the configuration. This resets how release-please looks for new versions. This is how I fixed the problem in another project.