Fix: Bump mbta/actions version for Tasks Tag propagation#772
Merged
Conversation
huangh
approved these changes
Jul 1, 2026
huangh
left a comment
huangh
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for all the work digging into this!
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.
Asana Task: review lamp kill task permissions
What changes does this PR propose?
This PR bumps the
mbta/actionscommit hash so that it will be able to consume the new deploy-ecs actions that will include the ability to add Tags to tasks in ECS. Once the tags are propagated and IAM policies are amended to have access to the new Tags being given, the issue in the Asana task will be resolved.See ECS tag PR in the actions repo here: mbta/actions#79
How were these changes validated?
1. New tests?2. Used a runner?3. Doesn't need validation? Maybe it's just documentation.PR is a Bump in the actions repo. Other teams have used it except for this notable bump with the tagging functionality which shouldn't break any deployment.
What questions should reviewers consider?
Feel free to ping me on slack for any questions not answered through the Asana task