fix: mastodon secret used workflow, not action

[cmeesters]

Summary by CodeRabbit

• Chores
  • Updated the release announcement workflow to use an updated Mastodon integration and improved token handling.

[coderabbitai]

Walkthrough

The GitHub Actions workflow for announcing releases on Mastodon was updated. The workflow now uses version 1.0.4 of the snakemake/mastodon-release-post-action and includes an access-token input sourced from the MASTODONBOT repository secret. No other workflow logic or exported entities were changed.

Changes

File(s)	Change Summary
.github/workflows/announce-release.yml	Updated action version to 1.0.4 and added access-token input using the MASTODONBOT secret.

Possibly related PRs

• ci: mastodon action #231: Updates and builds upon the Mastodon release announcement workflow, similar to this PR.
• fix: trying syntax fix #235: Modifies the same workflow file, focusing on job trigger logic.
• fix: using latest fix for the announcement action #263: Updates the Mastodon release post action version in the same workflow.

Suggested reviewers

• dlaehnemann

Poem

A bunny hops through YAML fields,
Updating tokens, secure and sealed.
Mastodon hears the joyous cheer,
With version bumps, releases near!
🐇✨
Announcements sent with secret grace—
Another workflow in its place!

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/announce-release.yml (1)

19-19: Bump action to v1.0.4
This update pins the snakemake/mastodon-release-post-action to release 1.0.4, which is required to support the new access-token input.

Consider whether you’d prefer pinning to the major version (@v1) to automatically receive non-breaking patches, or fixed patch versions for full reproducibility.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 760f8a5 and 1a3088a.

📒 Files selected for processing (1)

• .github/workflows/announce-release.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: testing

🔇 Additional comments (1)

.github/workflows/announce-release.yml (1)

22-22: Verify MASTODONBOT secret configuration
Ensure that the repository secret MASTODONBOT is defined in Settings → Secrets and has the correct token value. If it’s missing or mis-named, this workflow step will fail at runtime.