fix(tmp): replace expired ros2 apt repo key #14
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
GuillaumeLaine
force-pushed
the
fix-ros2-exipred-keyring
branch
from
2c91482 to
6946b1f
Compare
bkueng
approved these changes
Jun 3, 2025
Contributor
bkueng
left a comment
bkueng
left a comment
There was a problem hiding this comment.
Thanks for looking into this.
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.
Due to expired ros2 apt repo key, our CIs relying on this workflow are failing (cannot
apt update).This is a temporary fix that replaces the expired ros2 key with the new one. We can revert this commit once the the Docker ros images are updated: requires docker-library/official-images#19162
Testing
Tested locally with
docker build, builds successfully with this change. The new step adds ~5s to CI locally