Skip to content

chore(main): release google-crc32c 1.9.0 - #18426

Open
release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--google-crc32c
Open

release-please[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--google-crc32c

Conversation

@release-please

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.9.0 (2026-09-18)

Features

Bug Fixes

  • bump pip from 26.1.1 to 26.2 in /packages/google-crc32c/scripts (#18259) (ef272c7)
  • crc32c: escape the version dot and anchor the pyenv check regex (#17555) (b6a0275)

Documentation

  • handwritten: centralize CONTRIBUTING.rst pointers (#17642) (23b9499)

This PR was generated with Release Please. See documentation.

@release-please
release-please Bot requested review from a team as code owners September 18, 2026 23:27
@trusted-contributions-gcf trusted-contributions-gcf Bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 18, 2026
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 18, 2026
@daniel-sanche daniel-sanche added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Sep 21, 2026
@daniel-sanche

Copy link
Copy Markdown
Contributor

Hmm I thought we removed this from releases. Either way, the release pipeline isn't set up for this, so adding the do not merge tag

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants