Skip to content

Conversation

@moritzkiefer-da
Copy link
Contributor

@moritzkiefer-da moritzkiefer-da commented Jun 6, 2025

[ci]

This breaks cross-version compatibility in a few ways:

  1. Sponsor SV needs to be on same version as the candidate.
  2. For recover from key scan needs to be on the same version as the validator.
  3. A HSM export needs to happen on the same version as the import.

1 and 2 don't seem problematic to me. 3 doesn't matter now that mainnet is upgraded.

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

[ci]

This breaks cross-version compatibility in a few ways:

1. Sponsor SV needs to be on same version as the candidate.
2. For recover from key scan needs to be on the same version as the
validator.
3. A HSM export needs to happen on the same version as the import.

1 and 2 don't seem problematic to me. 3 is a bit more problematic. In
particular, we need to avoid merging this while we might still want to
cut a new 3.x release that we upgrade testnet or mainnet to directly
and even afterwards there may be stragglers. We can either tell people
they need to upgrade to 0.4.1 first to complete the HDM which sounds
fairly reasonable or we opt for the safer option of waiting for 30
days after the HDM is complete because then they would be pruned away
anyway.

Signed-off-by: Moritz Kiefer <[email protected]>
[ci]

Signed-off-by: Moritz Kiefer <[email protected]>
@moritzkiefer-da moritzkiefer-da force-pushed the cocreature/import-acs branch from df03b3a to f97b33c Compare June 30, 2025 09:41
@moritzkiefer-da moritzkiefer-da marked this pull request as ready for review June 30, 2025 11:10
@moritzkiefer-da moritzkiefer-da requested a review from nicu-da June 30, 2025 11:10
show"Download ACS snapshot for DSO at $authorizedAt",
participantAdminConnection
.downloadAcsSnapshot(
.downloadAcsSnapshotForPartyMigration(
Copy link
Contributor Author

Choose a reason for hiding this comment

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

the new endpoint handles that correctly without the crap here

Copy link
Contributor

@nicu-da nicu-da left a comment

Choose a reason for hiding this comment

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

Nice, thanks!

@moritzkiefer-da moritzkiefer-da merged commit a9aa5b8 into main Jun 30, 2025
114 of 116 checks passed
@moritzkiefer-da moritzkiefer-da deleted the cocreature/import-acs branch June 30, 2025 12:34
moritzkiefer-da pushed a commit that referenced this pull request Jul 1, 2025
[ci]

This reverts commit a9aa5b8.

blows up on cilr because it's too slow

Signed-off-by: Moritz Kiefer <[email protected]>
moritzkiefer-da added a commit that referenced this pull request Jul 1, 2025
* Revert "Switch to new ACS export/import endpoints (#1021)"

[ci]

This reverts commit a9aa5b8.

blows up on cilr because it's too slow

Signed-off-by: Moritz Kiefer <[email protected]>

* Revert "Bump base version for ciperiodic migration tests (#1268)"

[ci]

This reverts commit 63fc1ef.

Signed-off-by: Moritz Kiefer <[email protected]>

---------

Signed-off-by: Moritz Kiefer <[email protected]>
Co-authored-by: Moritz Kiefer <[email protected]>
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.

4 participants