Skip to content

fix: prevent multiple mutations of the node_operator_ key when removing nodes with RemoveNodes proposal #7953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
NikolaMilosa wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

fix: prevent multiple mutations of the node_operator_ key when removing nodes with RemoveNodes proposal #7953

NikolaMilosa wants to merge 3 commits into from
+48 −39

Conversation

@NikolaMilosa
Copy link
Contributor

@NikolaMilosa NikolaMilosa commented Dec 4, 2025

This PR consolidates the do_remove_nodes with the rest of the update calls which follow a natural rule:

1 registry key should have at most 1 registry mutation per 1 version.

@NikolaMilosa NikolaMilosa added the CI_ALL_BAZEL_TARGETS Runs all bazel targets and uploads them to S3 label Dec 4, 2025
@github-actions github-actions bot added the fix label Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

CI_ALL_BAZEL_TARGETS Runs all bazel targets and uploads them to S3 fix

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@NikolaMilosa