Skip to content

Conversation

@SangJunBak
Copy link
Contributor

  • Added a banner to signal we're only allowed 1 major version at a time
  • Specify upgrade pattern
  • Got rid of compatibility table

Motivation

Tips for reviewer

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.

- Added a banner to signal we're only allowed 1 major version at a time
- Specify upgrade pattern
- Got rid of compatibility table
@SangJunBak SangJunBak requested a review from a team as a code owner November 13, 2025 18:18
@SangJunBak SangJunBak changed the title docs: Unify versions in installl/upgrade guides for 26.0.0 docs: Unify versions in install/upgrade guides for 26.0.0 Nov 13, 2025
Copy link
Contributor

@kay-kim kay-kim left a comment

Choose a reason for hiding this comment

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

just couple of blurbs. Once addressed, feel free to merge in. Thank you!

mz_version={{ $operator_helm_chart_version }}

curl -o sample-values.yaml https://raw.githubusercontent.com/MaterializeInc/materialize/refs/tags/$mz_operator_version/misc/helm-charts/operator/values.yaml
curl -o sample-values.yaml https://raw.githubusercontent.com/MaterializeInc/materialize/refs/tags/self-managed-$mz_version/misc/helm-charts/operator/values.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

Double checking ... this won't change to just $mz_version?
Just wonderin g... since the others, we're using $mz_version without the self-managed prefix.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah this detail I'm not 100% sure on. Kinda hard given the actually releases / git tags haven't been cut for 26.0.0. I'll ask.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Asked here but I don't think we need to block for this https://materializeinc.slack.com/archives/C07PN7KSB0T/p1763065921015899

@@ -0,0 +1,5 @@
{{< important >}}

Upgrades are supported for only one major version at a time. Skipping major versions or downgrading is not supported.
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we give an example?

@SangJunBak SangJunBak merged commit 0873e20 into MaterializeInc:docs-upcoming-v26.0.0 Nov 13, 2025
1 of 3 checks passed
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.

2 participants