Github actions: peg Rust version to 1.82 #75
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
This is the stable version at the time this branch was cut.
findepi
force-pushed
the
bo/v43/peg-rust-version-1.82
branch
from
9a75a46 to
b7eb34f
Compare
findepi
approved these changes
Nov 19, 2024
|
This PR was not green (https://github.com/sdf-labs/arrow-datafusion/actions/runs/11922227861/job/33228310973) |
findepi
added a commit
that referenced
this pull request
Nov 26, 2024
This reverts the `Github actions: peg Rust version to 1.82 (#75)` commit because it broke the CI build.
findepi
added a commit
that referenced
this pull request
Nov 26, 2024
This reverts the `Github actions: peg Rust version to 1.82 (#75)` commit because it broke the CI build.
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.
Which issue does this PR close?
Closes N/A
Rationale for this change
This is the stable version at the time this branch was cut.
We should do this for all maintainence branches going forward.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?