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

chore(main): release 5.1.2 #2023

Merged
merged 1 commit into from
Feb 24, 2025
Merged

Conversation

github-actions[bot]
Copy link
Contributor

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

🤖 I have created a release beep boop

5.1.2 (2025-02-24)

Features

Bug Fixes

  • hub: invalid token when parsing recent team id (#2011) (9120786)
  • hub: logs are not streamed when opening newly created actor (#2015) (2352677)
  • hub: prevent long lines to break the layout (#2014) (a16e496)
  • hub: remove outline on avatars (#2010) (64e322a)
  • js-utils: correctly handle esbuild with import-statement not matching node stdlib (#2067) (9b39c35)

Code Refactoring

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor

graphite-app bot commented Feb 13, 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 is an automated release update that bumps the version from 25.1.1 to 25.1.2, managed by Release Please.

  • Updates .release-please-manifest.json version to 25.1.2
  • Adds getting started prerequisites documentation in PR chore: added getting started prereq #2021
  • Updates CHANGELOG.md to document the new version and changes
  • Follows standard release automation workflow using Release Please GitHub Action

💡 (3/5) Reply to the bot's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!

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 from 5c61b1b to 631a4f2 Compare February 13, 2025 02:16
Copy link

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

Deploying rivet with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9a0a70f
Status: ✅  Deploy successful!
Preview URL: https://41f5b65c.rivet.pages.dev
Branch Preview URL: https://release-please--branches--ma.rivet.pages.dev

View logs

@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 2738ee4 to 9fd2507 Compare February 15, 2025 10:41
@github-actions github-actions bot changed the title chore(main): release 25.1.2 chore(main): release 25.2.0 Feb 17, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch 6 times, most recently from f874ea2 to 29fe430 Compare February 22, 2025 12:36
@github-actions github-actions bot changed the title chore(main): release 25.2.0 chore(main): release 5.1.2 Feb 22, 2025
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from 55d14f6 to 31359f0 Compare February 23, 2025 23:59
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 31359f0 to 9a0a70f Compare February 24, 2025 00:14
@NathanFlurry NathanFlurry merged commit f279f6b into main Feb 24, 2025
1 check passed
@NathanFlurry NathanFlurry deleted the release-please--branches--main branch February 24, 2025 06:18
Copy link
Contributor Author

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

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