ci(live): schedule safe contract validation - #162
Merged
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
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.
Summary
Claim issue #151 and schedule the existing safe live integration and compliance suites against the dedicated non-production Redis Cloud resources.
Closes #151.
Changes
Validation
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warningscargo test --workspaceincluding 99 doctests.tag_lifecycle_preserves_unrelated_tagspasses with exact request-body matching.Actions environment
The six approved credentials/resource IDs are configured as encrypted secrets in the
live-contract-testsenvironment. Its custom deployment policy permits only themainbranch. Secret names were verified without reading values; end-to-end dispatch follows merge because the new workflow is not yet present on the default branch.