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

Restore freshness check for Cargo.raze.lock. #78

Merged
merged 2 commits into from
Feb 9, 2021

Conversation

PiotrSikora
Copy link
Member

It was removed in #75, and while Cargo.raze.lock being outdated
was still caught as part of the cargo-raze format check, mixing
formatting and freshness checks resulted in confusing reporting.

Signed-off-by: Piotr Sikora piotrsikora@google.com

It was removed in proxy-wasm#75, and while Cargo.raze.lock being outdated
was still caught as part of the cargo-raze format check, mixing
formatting and freshness checks resulted in confusing reporting.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>
@PiotrSikora PiotrSikora merged commit 28a94df into proxy-wasm:master Feb 9, 2021
nullpo-head pushed a commit to nullpo-head/proxy-wasm-rust-sdk that referenced this pull request Apr 20, 2021
It was removed in proxy-wasm#75, and while Cargo.raze.lock being outdated
was still caught as part of the cargo-raze format check, mixing
formatting and freshness checks resulted in confusing reporting.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>
nullpo-head pushed a commit to nullpo-head/proxy-wasm-rust-sdk that referenced this pull request Apr 20, 2021
It was removed in proxy-wasm#75, and while Cargo.raze.lock being outdated
was still caught as part of the cargo-raze format check, mixing
formatting and freshness checks resulted in confusing reporting.

Signed-off-by: Piotr Sikora <piotrsikora@google.com>
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.

2 participants