Skip to content

Backport PR #5902 to release-line-0.6.7#5909

Open
canton-network-da wants to merge 2 commits into
release-line-0.6.7from
automation/backport-1bf7a307940ccdd37b46f433f611161f622b8bd5-release-line-0.6.7
Open

Backport PR #5902 to release-line-0.6.7#5909
canton-network-da wants to merge 2 commits into
release-line-0.6.7from
automation/backport-1bf7a307940ccdd37b46f433f611161f622b8bd5-release-line-0.6.7

Conversation

@canton-network-da

Copy link
Copy Markdown
Contributor

This PR was automatically created to backport PR #5902 to release-line-0.6.7.

moritzkiefer-da and others added 2 commits June 11, 2026 11:24
Currently the dashboard mixes up different serials/migration ids which
produces a mess.

[static]

Signed-off-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Co-authored-by: moritz.kiefer@digitalasset.com <moritz.kiefer@purelyfunctional.org>
Signed-off-by: DA Automation <splice-maintainers@digitalasset.com>
@canton-network-da

Copy link
Copy Markdown
Contributor Author

[backport] Reminder

Please consider backporting to the following branches:

  • main
  • release-line-0.6.6
  • release-line-0.6.5
  • release-line-0.6.4

▶️ Please check the boxes for branches that you wish to backport to and backport PRs will
automatically be created when you merge this PR.

And your PR is currently against base branch: release-line-0.6.7.

Note: Any PR comment containing [backport] will be considered for auto-backporting upon merge,
you can always add those manually for PRs that did not get these reminders. You can also edit
this comment manually and add more branches that this should be backported to.

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