Skip to content

chore(main): release pyroscope-lambda-extension 1.8.0#73

Open
pyroscope-development-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--pyroscope-lambda-extension
Open

chore(main): release pyroscope-lambda-extension 1.8.0#73
pyroscope-development-app[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--pyroscope-lambda-extension

Conversation

@pyroscope-development-app
Copy link
Copy Markdown

🤖 I have created a release beep boop

1.8.0 (2026-05-29)

Features

Bug Fixes

  • change log level to debug when exiting (#26) (c3bf02f)
  • configure MaxIdleConnsPerHost (was 2 by default) (#19) (9214f26)
  • deprecate release-please manual workflow (#37) (e5c72d6)
  • Fixing the release-please action (#49) (78af369)
  • relaying error handling (#30) (815cae0)
  • remove ap-northeast{2,3} arm builds (#8) (88501e9)
  • rename org_id to tenant_id (#23) (f21acfc)
  • security/unknown: update module golang.org/x/sys to v0.44.0 [security] (#60) (26fe56f)
  • set architecture when publishing (#6) (ae3372f)
  • use format string in Fatalf to fix go vet error (#71) (b1c8ca5)

This PR was generated with Release Please. See documentation.

@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented May 29, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

0 participants