Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Fix release-please workflow #205

Merged
merged 1 commit into from
Jan 15, 2025
Merged

ci: Fix release-please workflow #205

merged 1 commit into from
Jan 15, 2025

Conversation

nzakas
Copy link
Contributor

@nzakas nzakas commented Jan 7, 2025

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 from GoogleCloudPlatform/release-please-action to googleapis/release-please-action and added the GitHub token input.
  • .github/workflows/release-please.yml: Changed the command used for social media announcements from npx @humanwhocodes/tweet to npx @humanwhocodes/crosspost to 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 a bootstrap-sha entry to the configuration. This resets how release-please looks for new versions. This is how I fixed the problem in another project.

id: release
with:
release-type: 'node'
# The logic below handles the npm publication:
token: ${{secrets.GITHUB_TOKEN}}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is implied, but whatev

@boneskull boneskull merged commit 29ab908 into main Jan 15, 2025
16 checks passed
@boneskull boneskull deleted the rp-fix branch January 15, 2025 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

release-please not recognizing release
2 participants