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

Bump h2 #570

Merged
merged 1 commit into from
Apr 3, 2024
Merged

Bump h2 #570

merged 1 commit into from
Apr 3, 2024

Conversation

CriesofCarrots
Copy link

Problem

Cargo audit failure

Summary of Changes

Bump h2 to v0.3.26

@CriesofCarrots CriesofCarrots requested a review from bw-solana April 3, 2024 20:24
bw-solana
bw-solana previously approved these changes Apr 3, 2024
@CriesofCarrots
Copy link
Author

CriesofCarrots commented Apr 3, 2024

Sorry, rebased with changes to programs/sbf/Cargo.lock. I forgot that we have to run cargo update on programs/sbf/Cargo.toml directly instead of ./scripts/cargo-for-all-lock-files.sh tree

@CriesofCarrots CriesofCarrots added the automerge automerge Merge this Pull Request automatically once CI passes label Apr 3, 2024
@CriesofCarrots CriesofCarrots merged commit f6e02e6 into anza-xyz:master Apr 3, 2024
46 of 48 checks passed
Copy link

mergify bot commented Apr 5, 2024

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

Copy link

mergify bot commented Apr 5, 2024

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

mergify bot pushed a commit that referenced this pull request Apr 5, 2024
(cherry picked from commit f6e02e6)
mergify bot pushed a commit that referenced this pull request Apr 5, 2024
(cherry picked from commit f6e02e6)
yihau pushed a commit that referenced this pull request Apr 5, 2024
Bump h2 (#570)

(cherry picked from commit f6e02e6)

Co-authored-by: Tyera <tyera@anza.xyz>
yihau pushed a commit that referenced this pull request Apr 5, 2024
Bump h2 (#570)

(cherry picked from commit f6e02e6)

Co-authored-by: Tyera <tyera@anza.xyz>
@HaoranYi HaoranYi mentioned this pull request Apr 8, 2024
anwayde pushed a commit to firedancer-io/agave that referenced this pull request Jul 23, 2024
Bump h2 (anza-xyz#570)

(cherry picked from commit f6e02e6)

Co-authored-by: Tyera <tyera@anza.xyz>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge automerge Merge this Pull Request automatically once CI passes v1.18
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants