Naga add hardcoded keysets #878
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ansonhkg
had a problem deploying
to
Health Check
GitHub Actions
Failure
…in auth-services and networks
- add missing `maxPrice` in the custom auth payload - e2e: fix custom auths
Ansonhkg
had a problem deploying
to
Health Check
GitHub Actions
Failure
Ansonhkg
had a problem deploying
to
Health Check
GitHub Actions
Failure
Ansonhkg
had a problem deploying
to
Health Check
GitHub Actions
Failure
Ansonhkg
had a problem deploying
to
Health Check
GitHub Actions
Failure
This was referenced Sep 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original PR: #866
Description
Updates to the latest
developbuild ofnetworkContext.jsonto catch keysets. Adds a hardcodednaga-keyset1value, since this is the coding inlit-noderight now.Adds a LICENCE file for the
wasmpackage ( suppresses a warning! )Removes
wasm-optfor the release build of thewasmpackage. Might be a local descrepency.Type of change
How Has This Been Tested?
e2e tests are passing