Update to actions-riff-raff@v4 #109
Open
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
|
Ah, I got confused: I thought we (Content Pipeline) owned this repository, but actually I don’t believe we do! |
|
I think the repository is owned by @guardian/ophan, but I can’t request a review from that team for some reason. Maybe this is the same reason the codeowners file in this repo is flagged by Github as invalid? |
Saw a recent email from DevX about upgrading, figured I’d do it quickly. Version 4 means we can get rid of the AWS credentials step and leaves us less vulnerable to credentials access by malicious dependencies See [the release notes for version 4](https://github.com/guardian/actions-riff-raff/releases/tag/v4) and [those for version 3](https://github.com/guardian/actions-riff-raff/releases/tag/v3.0.0) (the latter necessary because we’re coming from version 2.)
emdash-ie
force-pushed
the
update-actions-riff-raff-to-v4
branch
from
3924271 to
5439b15
Compare
|
I've added the Ophan team as an Admin of this repo at https://github.com/guardian/status-app/settings/access, I hope this helps! |
Ah yes, that seems to have fixed it :) Thanks! |
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.
Saw a recent email from DevX about upgrading, figured I’d do it quickly. Version 4 means we can get rid of the AWS credentials step and leaves us less vulnerable to credentials access by malicious dependencies
See the release notes for version 4 and those for version 3 (the latter necessary because we’re coming from version 2.)
(Have also committed auto-formatting done by my editor)