Skip to content

fix: release notes to action script #310

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

Merged
merged 1 commit into from
May 18, 2025
Merged

fix: release notes to action script #310

merged 1 commit into from
May 18, 2025

Conversation

cmeesters
Copy link
Member

@cmeesters cmeesters commented May 18, 2025

letting the own action handle posting release notes.

Summary by CodeRabbit

  • Chores
    • Updated release workflow configuration.

Copy link
Contributor

coderabbitai bot commented May 18, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The GitHub Actions workflow was modified by removing the step that extracted release notes from the changelog. However, the Mastodon posting step still references the now-missing release notes output, potentially causing issues during execution. No other workflow logic or error handling was changed.

Changes

File(s) Change Summary
.github/workflows/announce-release.yml Removed the step that extracted release notes from CHANGELOG.md; Mastodon post step still references the removed output.

Possibly related PRs

Suggested reviewers

  • dlaehnemann

Poem

A bunny hopped through YAML fields,
Snipping steps the changelog yields.
Mastodon waits for notes to show,
But now the notes have nowhere to go!
With paws and whiskers, bugs may bloom—
Let's fix this soon, before the boom!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 62b9ed0 and 06a50bd.

📒 Files selected for processing (1)
  • .github/workflows/announce-release.yml (1 hunks)

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

@cmeesters cmeesters merged commit c5a3d6e into main May 18, 2025
4 of 5 checks passed
@cmeesters cmeesters deleted the fix/release_notes branch May 18, 2025 14:53
cmeesters pushed a commit that referenced this pull request May 18, 2025
🤖 I have created a release *beep* *boop*
---


##
[1.3.6](v1.3.5...v1.3.6)
(2025-05-18)


### Bug Fixes

* release notes to action script
([#310](#310))
([c5a3d6e](c5a3d6e))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated the changelog with a new entry for version 1.3.6, including a
referenced bug fix.
  - Increased the package version to 1.3.6.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.

1 participant