Conversation
RikRootsGuardian
approved these changes
Oct 30, 2025
RikRootsGuardian
left a comment
RikRootsGuardian
left a comment
There was a problem hiding this comment.
I can think of no way this one-word update will fail. Approved!
JustinPinner
added
SECURITY
maintenance
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What does this change?
conf/riff-raff.yamlupdated to new AMI with more recent OSHow to test
Deploy and observe. There should be no difference in requests or outputs.
Tested on CODE, verified that the instance processing the requests was running the correct AMI and that the returned content matched with equivalent checks from dotcom.
NOTE: If anyone else intends to test this from dotcom's m.code URL, that will not exercise the same path to the RSS instances, so you'll have to poke the LB directly. It's also worth noting that itunes:image elements are absent from CODE's responses because it's not configured there. However the execution is otherwise identical.
How can we measure success?
Ensure before and after results are consistent and no new errors are evident ✅
Have we considered potential risks?
If it fails, we'll redeploy the previous build or fix forwards.
Images
N/A
Accessibility