deps: Bump github.com/google/flatbuffers to v1.12.1 #1746
Merged
Conversation
This file contains 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
The v1.12.0 version of the flatbuffers package has an issue where the hash of the package will differ depending on if you fetch the source using the default, public Go Modules proxy or if you fetch the source directly, which can cause build issues [1][2]. The flatbuffers maintainers released v1.12.1 to fix this issue [3]. [1] https://github.com/open-policy-agent/conftest/runs/3576130950?check_suite_focus=true [2] open-policy-agent/conftest#613 [3] google/flatbuffers#6466 Signed-off-by: James Alseth <[email protected]>
|
|
|
The CI issue appears to be unrelated to this change, so it shouldn't be blocking for this PR. |
|
@NamanJain8 Is it possible to create a patch release that includes this? We'd like to bump our |
|
Hi @jalseth, I will try to do the patch release in a few days. |
NamanJain8
pushed a commit
that referenced
this pull request
Oct 5, 2021
The v1.12.0 version of the flatbuffers package has an issue where the hash of the package will differ depending on if you fetch the source using the default, public Go Modules proxy or if you fetch the source directly, which can cause build issues [1][2]. The flatbuffers maintainers released v1.12.1 to fix this issue [3]. [1] https://github.com/open-policy-agent/conftest/runs/3576130950?check_suite_focus=true [2] open-policy-agent/conftest#613 [3] google/flatbuffers#6466 Signed-off-by: James Alseth <[email protected]> (cherry picked from commit a6bf4fd)
|
Hey @jalseth, we have released badger v3.2103.2 that contains this change. |
mangalaman93
pushed a commit
that referenced
this pull request
Feb 14, 2023
The v1.12.0 version of the flatbuffers package has an issue where the hash of the package will differ depending on if you fetch the source using the default, public Go Modules proxy or if you fetch the source directly, which can cause build issues [1][2]. The flatbuffers maintainers released v1.12.1 to fix this issue [3]. [1] https://github.com/open-policy-agent/conftest/runs/3576130950?check_suite_focus=true [2] open-policy-agent/conftest#613 [3] google/flatbuffers#6466 Signed-off-by: James Alseth <[email protected]> (cherry picked from commit a6bf4fd)
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.
The v1.12.0 version of the flatbuffers package has an issue where the
hash of the package will differ depending on if you fetch the source
using the default, public Go Modules proxy or if you fetch the source
directly, which can cause build issues [1][2]. The flatbuffers maintainers
released v1.12.1 to fix this issue [3].
[1] https://github.com/open-policy-agent/conftest/runs/3576130950?check_suite_focus=true
[2] open-policy-agent/conftest#613
[3] google/flatbuffers#6466
Signed-off-by: James Alseth [email protected]
This change is