-
Notifications
You must be signed in to change notification settings - Fork 17
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
Build byte code files in CI, remove from git tree #279
Conversation
@leordev @ALRubinger I've added you as CODEOWNERS, lmk if you'd prefer to not be |
.github/workflows/ci.yml
Outdated
@@ -10,49 +22,193 @@ env: | |||
CARGO_TERM_COLOR: always | |||
# Make sure CI fails on all warnings, including Clippy lints | |||
RUSTFLAGS: "-Dwarnings" | |||
TBDEX_SDK_LOG_LEVEL: debug |
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.
TBDEX_SDK_LOG_LEVEL
should be called WEB5_SDK_LOG_LEVEL
here
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.
nice catch, fixed!
Previously we have been checking-in the byte code files, but this is undesirable for many reasons. Most of the work here is a rip from TBD54566975/tbdex-rs#96
I've also removed the
jitpack.yml
because that will no longer function with the removal of the byte code files from source control.@ALRubinger @leordev I went as far as to run Maven tests, but could we go ahead and add snapshot deployments? I don't want to go the full 9-yards and add releases, but if we could go ahead and deploy snapshots then that would be a big win for cross-project integrations (since I'm removing the JitPack integration here).