After further investigation, it turns out these issues are not release blockers.
So we’ll continue with the current RC4 voting and validation process rather than moving to RC5. On 2026/08/27 08:03:38 Vitalii Terentev wrote: > Found a few issues, moving to RC #5. > > On 2026/08/21 16:54:24 Vitaly Terentyev via dev wrote: > > Hi everyone, > > Please review and vote on the release candidate #4 for the version 2.76.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > > > Reviewers are encouraged to test their own use cases with the release > > candidate, and vote +1 if > > no issues are found. Only PMC member votes will count towards the final > > vote, but votes from all > > community members are encouraged and helpful for finding regressions; you > > can either test your own > > use cases [13] or use cases from the validation sheet [10]. > > > > The complete staging area is available for your review, which includes: > > * GitHub Release notes [1], > > * the official Apache source release to be deployed to dist.apache.org [2], > > which is signed with the key with fingerprint D20316F712213422 as automated > > [3], > > * all artifacts to be deployed to the Maven Central Repository [4], > > * source code tag "v2.76.0-RC4" [5], > > * website pull request listing the release [6], the blog post [6], and > > publishing the API reference manual [7]. > > * Python artifacts are deployed along with the source release to > > dist.apache.org [2] and PyPI[8]. > > * Go artifacts and documentation are available at pkg.go.dev [9] > > * Validation sheet with a tab for 2.76.0 release to help with validation > > [10]. > > * Docker images published to Docker Hub [11]. > > * PR to run tests against release branch [12]. > > * Github Release pre-release page for v2.76.0-RC4 [13]. > > * pull request to apache/beam updating the managed-io docs[15] > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > For guidelines on how to try the release in your projects, check out our RC > > testing guide [14]. > > > > Thanks, > > Release Manager > > > > [1] https://github.com/apache/beam/milestone/44 > > [2] https://dist.apache.org/repos/dist/dev/beam/2.76.0/ > > [3] https://dist.apache.org/repos/dist/release/beam/KEYS > > [4] https://repository.apache.org/content/repositories/orgapachebeam-1436/ > > [5] https://github.com/apache/beam/tree/v2.76.0-RC4 > > [6] https://github.com/apache/beam/pull/39718 > > [7] https://github.com/apache/beam-site/pull/708 > > [8] https://pypi.org/project/apache-beam/2.76.0rc4/ > > [9] > > https://pkg.go.dev/github.com/apache/beam/sdks/[email protected]/go/pkg/beam > > [10] > > https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit?gid=1287201083#gid=1287201083 > > [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image > > [12] https://github.com/apache/beam/pull/39653 > > [13] https://github.com/apache/beam/releases/tag/v2.76.0-RC4 > > [14] > > https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md > > [15] <https://github.com/apache/beam/pull/39717> > > https://github.com/apache/beam/pull/39839 > > > > >
