Skip to content

chore(main): release 2.5.5#324

Closed
pyroscope-development-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--pyroscope-java
Closed

chore(main): release 2.5.5#324
pyroscope-development-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--pyroscope-java

Conversation

@pyroscope-development-app
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.5.5 (2026-06-01)

Bug Fixes

  • security/unknown: update go toolchain directive to v1.25.10 [security] (#314) (610e997)
  • security/unknown: update module golang.org/x/crypto to v0.52.0 [security] (#315) (715d6d9)
  • security/unknown: update module golang.org/x/net to v0.55.0 [security] (#316) (6990fd2)

Miscellaneous Chores

Continuous Integration

  • adopt release-please (735a31d)
  • migrate workflows to GATB (95a542a)
  • migrate workflows to GATB (67aa612)
  • remove Javadoc GitHub Pages deploy workflow (#318) (2c2335d)

This PR was generated with Release Please. See documentation.

@korniltsev-grafanista
Copy link
Copy Markdown
Contributor

Closing: stale release PR. There are 0 commits since v2.5.4 (git log v2.5.4..main is empty). This PR was generated during a race where v2.5.4 was still a draft release, so release-please anchored back to bootstrap-sha and regenerated the full changelog. Re-running release-please now correctly finds v2.5.4 with 0 new commits.

@korniltsev-grafanista korniltsev-grafanista deleted the release-please--branches--main--components--pyroscope-java branch June 1, 2026 14:10
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