chore: use devcontainer image v1.1.0 and fix ebclfsa workflow #82
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
|
The created documentation from the pull request is available at: docu-html |
opajonk
reviewed
Jan 28, 2026
Some time passed already since creation of version 1.0 and we should eventually the use version used in the workflow.
Changing the workflow could otherwise in undetected build breaks. Co-authored-by: Oliver Pajonk <[email protected]> Signed-off-by: lurtz <[email protected]>
Fixes the ebclfsa build where bazel now wants to download version 9.0.0. The specified bazel version is present in the devcontainer and will not trigger a download.
lurtz
force-pushed
the
use-devcontainer-v1.1.0
branch
from
78ee688 to
f49dc46
Compare
lurtz
changed the title
opajonk
approved these changes
Jan 28, 2026
AlexanderLanin
approved these changes
Jan 29, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Some time passed already since creation of version 1.0 and we should eventually the use version used in the workflow.
Closes #81