-
Notifications
You must be signed in to change notification settings - Fork 340
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.
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
fix(manifest): resolve node persistence after removal #4819
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very neat find. please simplify by just nil-ing the ref field
@asabya can you pls fix the commit msg, see https://github.com/ethersphere/bee/actions/runs/11669094347/job/33647232645?pr=4819#step:5:41 |
8787863
to
b31b0db
Compare
fixed |
Checklist
Description
This PR fixes #4808. Where loading a manifest then removing forks from it would not persist in the next load.