Skip to content

Conversation

lenaschoenburg
Copy link
Member

@lenaschoenburg lenaschoenburg commented Aug 15, 2025

We shouldn't rely on the number of migrations, even if we only just updated the version number, we must take a new snapshot.

(cherry picked from commit 81b7d07)

I also had to several other commits that adjusted tests.
The only new commit is 0aa3d73, somehow that wasn't necessary on main.

We shouldn't rely on the number of migrations, even if we only just
updated the version number, we must take a new snapshot.

(cherry picked from commit 81b7d07)
@lenaschoenburg lenaschoenburg added the backport stable/8.6 Backport a pull request to stable/8.6 label Aug 15, 2025
@github-actions github-actions bot added the component/zeebe Related to the Zeebe component/team label Aug 15, 2025
@lenaschoenburg lenaschoenburg changed the title fix: always take a snapshot after update, even without any migrations [Backport stable/8.7] fix: always take a snapshot after update, even without any migrations Aug 15, 2025
Required so we can take an initial snapshot on startup when there's
nothing to process.

(cherry picked from commit 51a9883)
Now that we always take a snapshot after update, we can no longer
assert that we don't have one. We can still test that we can update
when we didn't have a snapshot before the update though.

(cherry picked from commit e935c20)
@lenaschoenburg
Copy link
Member Author

@npepinpe Requesting another review because I had to cherry-pick various other commits and add a new fix with 0aa3d73

@lenaschoenburg lenaschoenburg force-pushed the ls/backport-version-update-fix branch from d69b242 to 075180b Compare August 15, 2025 13:43
(cherry picked from commit fc54f3e)
We can't assert that a specific snapshot is present, the broker with
dataloss can take it's own snapshot after receiving one.

(cherry picked from commit 105e83a)
@lenaschoenburg lenaschoenburg force-pushed the ls/backport-version-update-fix branch from 075180b to 85bfbc0 Compare August 15, 2025 14:04
@lenaschoenburg lenaschoenburg added this pull request to the merge queue Aug 15, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 15, 2025
@npepinpe npepinpe added this pull request to the merge queue Aug 15, 2025
Merged via the queue into stable/8.7 with commit e671fad Aug 15, 2025
54 checks passed
@npepinpe npepinpe deleted the ls/backport-version-update-fix branch August 15, 2025 19:02
@backport-action
Copy link
Collaborator

github-merge-queue bot pushed a commit that referenced this pull request Aug 15, 2025
…ot after update, even without any migrations (#36880)

# Description
Backport of #36847 to `stable/8.6`.

relates to
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport stable/8.6 Backport a pull request to stable/8.6 component/zeebe Related to the Zeebe component/team version:8.6.25
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants