-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: movement-full-node-v0.0.1-beta #1039
feat: movement-full-node-v0.0.1-beta #1039
Conversation
We need to get this into main asap, there are several other PRs that rely on this. We are going with a release tag strategy, rather than release branch (avoid long living branches) as recommended by @radupopa369 and @nicolaslpf. We need description in this PR and testing steps, also there are a tonne of conflicts. |
Wrong nick i guess you might want to ping @mcmillennick |
Myself and @musitdev will take on the load of resolving conflicts, but if you could write some description and testing steps in the description would be great. We have already tagged main with this release, but actually the release is on this feature branch. This was done to meet the release deadline, let's fix now. @l-monninger drop anything useful in comments myself of Philippe should know about. |
Yeah, not sure what happened here...
|
Just going to try pulling locally. |
Does not resolve. |
I wonder if it has something to do with squashing. |
Never seen it occur with squashing before. Are the changes from 993 even in main? The .debug/ is certainly there (which shouldn't be committed) cc @elliottdehn this commit is where the |
e737faa
into
l-monninger/secure-signing-e2e-integration
Summary
protocol-units
The secondary tag used for onboarding to and test the Movement Full Node w/ secure signing, governed gas pool, and additional admin utilities.
Changelog
Testing
Outstanding issues