Skip to content

Backport PR #6752 to release-line-0.7.1 - #6755

Merged
martinflorian-da merged 2 commits into
release-line-0.7.1from
automation/backport-bf5edc767e3c94b76ef9455e0aa7b80b99dfa7c7-release-line-0.7.1
Aug 12, 2026
Merged

Backport PR #6752 to release-line-0.7.1#6755
martinflorian-da merged 2 commits into
release-line-0.7.1from
automation/backport-bf5edc767e3c94b76ef9455e0aa7b80b99dfa7c7-release-line-0.7.1

Conversation

@canton-network-da

Copy link
Copy Markdown
Contributor

This PR was automatically created to backport PR #6752 to release-line-0.7.1.

martinflorian-da and others added 2 commits August 12, 2026 10:04
Apparently they changed something and the old query doesn't give signal anymore.

I picked the new query based on looking at logs... and looking at historic data it looks right and not too spammy.

Signed-off-by: Martin Florian <martin.florian@digitalasset.com>
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.7.0
  • release-line-0.6.14
  • release-line-0.6.13

▶️ 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.7.1.

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.

@martinflorian-da
martinflorian-da enabled auto-merge (squash) August 12, 2026 10:07
@martinflorian-da
martinflorian-da merged commit 4417fe8 into release-line-0.7.1 Aug 12, 2026
44 checks passed
@martinflorian-da
martinflorian-da deleted the automation/backport-bf5edc767e3c94b76ef9455e0aa7b80b99dfa7c7-release-line-0.7.1 branch August 12, 2026 10:24
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