Skip to content

chore(main): release pubsublite 2.0.0#19998

Merged
brownsuga918 merged 1 commit into
mainfrom
release-please--branches--main--components--pubsublite
Jun 17, 2026
Merged

chore(main): release pubsublite 2.0.0#19998
brownsuga918 merged 1 commit into
mainfrom
release-please--branches--main--components--pubsublite

Conversation

@release-please

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0 (2026-06-17)

⚠ BREAKING CHANGES

  • all: The HAS operator on timestamp fields now only accepts the wildcard "" for presence checks (e.g. "create_time:"). Using timestamp values with HAS (e.g. "create_time:"2022-..."") is no longer supported.

Features

Bug Fixes

Miscellaneous Chores


This PR was generated with Release Please. See documentation.

@release-please release-please Bot requested review from a team as code owners June 17, 2026 03:16
@trusted-contributions-gcf trusted-contributions-gcf Bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 17, 2026
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 17, 2026
@codyoss codyoss added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jun 17, 2026
@brownsuga918 brownsuga918 removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jun 17, 2026
@brownsuga918 brownsuga918 merged commit a7b2ac6 into main Jun 17, 2026
17 checks passed
@brownsuga918 brownsuga918 deleted the release-please--branches--main--components--pubsublite branch June 17, 2026 03:39
@codyoss

codyoss commented Jun 17, 2026

Copy link
Copy Markdown
Member

@brownsuga918 This PR should not have been merged which I why I put the label on it. I think I removed the release label in time before the automation actually did the release. I will send a followup PR tomorrow to revert these changes. This should not have been bumping the major.

codyoss added a commit that referenced this pull request Jun 17, 2026
This reverts commit a7b2ac6. This
should not have been a major version bump. I stopped release-please
before the release got out so all we have to do is reset these files.
hongalex pushed a commit that referenced this pull request Jul 6, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.9.0](pubsublite/v1.8.2...pubsublite/v1.9.0)
(2026-07-06)


### Features

* Enable open telemetry attrs
([#14426](#14426))
([74eab64](74eab64))
* **pubsublite:** Add GMK Implementation changes
([#14466](#14466))
([50a5550](50a5550))


### Bug Fixes

* **pubsublite:** Reduce pscompat BufferedByteLimit
([#14234](#14234))
([e768524](e768524)),
closes
[#14237](#14237)


### Reverts

* Release pubsublite 2.0.0
([#19998](#19998))
([#20006](#20006))
([d7b7078](d7b7078))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pubsublite: use of 10GB int consts breaks 32 bit systems

3 participants