Skip to content
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 legacy registry action #86

Merged
merged 2 commits into from
Mar 4, 2024
Merged

Fix legacy registry action #86

merged 2 commits into from
Mar 4, 2024

Conversation

noandrea
Copy link
Collaborator

@noandrea noandrea commented Mar 4, 2024

No description provided.

@noandrea noandrea merged commit 5fec12d into master Mar 4, 2024
68 checks passed
@noandrea noandrea deleted the fix-legacy-registry-action branch March 4, 2024 22:16
@@ -42,4 +42,9 @@ cd ..
echo "Running ./scripts/update-tracing-runtime-lock.sh $SPEC_VERSION ..."
source ./scripts/update-tracing-runtime-lock.sh $SPEC_VERSION

echo "Format with cargo fmt"
Copy link

Choose a reason for hiding this comment

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

Not sure that you need this in theory as format should be applied on moonbeam repo if we had the check, and if we don't there's no need to format.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

the ci is always failing on for cargo fmt check, I prefer that we format before pushing

Copy link

Choose a reason for hiding this comment

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

Maybe remove the cargo fmt check is better in order to be consistent with the main repo?

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.

3 participants