Skip to content

Bump version to v26.0.0-dev.0, adapt release scripting & tests #33983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Nov 10, 2025
Merged

Bump version to v26.0.0-dev.0, adapt release scripting & tests #33983

merged 1 commit into from
Nov 10, 2025

Conversation

@def-
Copy link
Contributor

@def- def- commented Oct 30, 2025 •
edited
Loading

This should be merged on Friday, November 7, after we cut the next v0.X.Y release. Then we have 6 days in testing where we already have a v26.0.0-dev.0 version to play around with before cutting it into v26.0.0-rc.1 on Thursday, November 13.

Status: Currently blocked on #34027

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@def- def- changed the title Bump version to v26.0.0-dev.0 & remove operator-weekly Bump version to v26.0.0-dev.0 Oct 30, 2025
@def- def- force-pushed the pr-self-managed-weekly branch 4 times, most recently from 23e921a to c113d4e Compare October 30, 2025 16:59
@def- def- marked this pull request as ready for review November 6, 2025 17:02
@def- def- requested review from a team as code owners November 6, 2025 17:02
@def- def- requested a review from ggevay November 6, 2025 17:02
@def- def- force-pushed the pr-self-managed-weekly branch from c113d4e to fec4922 Compare November 7, 2025 08:49
@def- def- requested a review from bosconi November 7, 2025 08:49
@def- def- force-pushed the pr-self-managed-weekly branch from 5ef9271 to cf631bd Compare November 7, 2025 08:55
@def-
Copy link
Contributor Author

def- commented Nov 7, 2025

@teskje We are still seeing a bunch of upgrade test failures: Checks 0dt upgrade across four versions

platform-checks-mz_5-1              | environmentd: fatal: incompatible persist version 0.164.0, current: 26.0.0-dev.0, make sure to upgrade the catalog one version forward at a time

Are there already changes in flight that will fix that?

@def- def- force-pushed the pr-self-managed-weekly branch 3 times, most recently from bdb5638 to b3ceb6f Compare November 7, 2025 11:11
@def- def- requested a review from a team as a code owner November 7, 2025 11:11
@def- def- force-pushed the pr-self-managed-weekly branch from b3ceb6f to 9a2f60b Compare November 7, 2025 11:36
@teskje
Copy link
Contributor

teskje commented Nov 7, 2025

Yep, #34027 is supposed to resolve the version jump errors. It changes how the persist shard version gets updated. Currently, the read-only env bumps the shard version, which makes the leader env shut down. With Ben's change, the read-only env only observes the shard version and it doesn't get bumped until the promotion happens. Which means we won't to rush to get any changes into 0.164, we only need to merge Ben's PR before 26.0.

@def- def- mentioned this pull request Nov 7, 2025
Merged
5 tasks
@def-
Copy link
Contributor Author

def- commented Nov 7, 2025

Awesome, then I hope we can merge that soon! CC @bkirwi

@def- def- force-pushed the pr-self-managed-weekly branch 3 times, most recently from 9c2101e to fa8ba62 Compare November 10, 2025 16:39
@def-
Copy link
Contributor Author

def- commented Nov 10, 2025

Ready for review!

@def- def- requested review from bkirwi, jubrad and teskje November 10, 2025 16:39
@def- def- changed the title Bump version to v26.0.0-dev.0 Bump version to v26.0.0-dev.0, adapt release scripting & tests Nov 10, 2025
@def- def- requested a review from SangJunBak November 10, 2025 16:46
teskje
teskje approved these changes Nov 10, 2025
View reviewed changes
Copy link
Contributor

@teskje teskje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, provided the tests pass!

@def- def- force-pushed the pr-self-managed-weekly branch from fa8ba62 to 960a983 Compare November 10, 2025 17:57
@def- def- force-pushed the pr-self-managed-weekly branch from 960a983 to c4e4497 Compare November 10, 2025 18:05
@def-
Copy link
Contributor Author

def- commented Nov 10, 2025

Nightly is looking mostly ok: https://buildkite.com/materialize/nightly/builds/14041
Had to fix one further test, new run for that: https://buildkite.com/materialize/nightly/builds/14043

@def- def- enabled auto-merge November 10, 2025 18:06
@def- def- merged commit a1a7357 into MaterializeInc:main Nov 10, 2025
129 checks passed
@def- def- deleted the pr-self-managed-weekly branch November 10, 2025 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@teskje teskje teskje approved these changes

@ggevay ggevay Awaiting requested review from ggevay ggevay is a code owner automatically assigned from MaterializeInc/adapter

@bosconi bosconi Awaiting requested review from bosconi

@bkirwi bkirwi Awaiting requested review from bkirwi

@jubrad jubrad Awaiting requested review from jubrad

@alex-hunt-materialize alex-hunt-materialize Awaiting requested review from alex-hunt-materialize

@doy-materialize doy-materialize Awaiting requested review from doy-materialize

@SangJunBak SangJunBak Awaiting requested review from SangJunBak

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@def- @teskje