Skip to content

chore(main): release 25.2.0 #2079

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
Mar 7, 2025
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 25, 2025

🤖 I have created a release beep boop

25.2.0 (2025-03-07)

Features

Bug Fixes

Documentation

Chores


This PR was generated with Release Please. See documentation.

Copy link

cloudflare-workers-and-pages bot commented Feb 25, 2025

Deploying rivet with  Cloudflare Pages  Cloudflare Pages

Latest commit: e0e11f7
Status:🚫  Build failed.

View logs

Copy link
Contributor

graphite-app bot commented Feb 25, 2025

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR updates the version in Rivet from 5.1.2 to 5.1.3 as part of an automated release process managed by Release Please.

  • Updates .release-please-manifest.json with the new version number 5.1.3
  • Adds a new entry in CHANGELOG.md documenting the addition of a Better Stack monitoring example
  • The release is triggered automatically by the release-please GitHub Action workflow
  • The change is minimal and follows the project's versioning scheme and changelog format

Greptile AI: No major changes found since last review.

💡 (4/5) You can add custom instructions or style guidelines for the bot here!

2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 08cd0c4 to 749c2b8 Compare March 3, 2025 22:30
@github-actions github-actions bot changed the title chore(main): release 5.1.3 chore(main): release 5.2.0 Mar 4, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch 6 times, most recently from e0c1748 to 10ceda7 Compare March 5, 2025 02:46
@github-actions github-actions bot changed the title chore(main): release 5.2.0 chore(main): release 5.1.3 Mar 5, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 10ceda7 to a1247c2 Compare March 5, 2025 04:05
@github-actions github-actions bot changed the title chore(main): release 5.1.3 chore(main): release 25.1.3 Mar 5, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch 8 times, most recently from c2cfc6a to 545accc Compare March 7, 2025 01:46
@github-actions github-actions bot changed the title chore(main): release 25.1.3 chore(main): release 25.2.0 Mar 7, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 545accc to 80aa471 Compare March 7, 2025 10:37
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 80aa471 to e0e11f7 Compare March 7, 2025 10:47
@NathanFlurry NathanFlurry merged commit bd2236d into main Mar 7, 2025
1 check failed
@NathanFlurry NathanFlurry deleted the release-please--branches--main branch March 7, 2025 11:07
Copy link
Contributor Author

github-actions bot commented Mar 7, 2025

🤖 Release is at https://github.com/rivet-gg/rivet/releases/tag/v25.2.0 🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant