Update GitHub Actions workflow dependencies.

Change Summary

This update modifies the GitHub Actions workflows for deploying and planning infrastructure changes. Specifically, it updates the versions of several GitHub Actions used within these workflows to ensure they are using the latest available commits.

Technical Details

• Files Modified:
  • .github/workflows/deploy.yml
  • .github/workflows/plan.yml
• Changes per File:
  • deploy.yml:
    • Updated gruntwork-io/terragrunt-action from commit v3 to 95fc057922e3c3d4cc021a81a213f088f333ddef.
    • Updated aws-actions/configure-aws-credentials from v5.1.1 to commit 61815dcd50bd041e203e49132bacad1fd04d2708.
    • Updated tailscale/github-action from v4 to commit 53acf823325fe9ca47f4cdaa951f90b4b0de5bb9.
  • plan.yml:
    • Updated gruntwork-io/terragrunt-action from commit v3 to 95fc057922e3c3d4cc021a81a213f088f333ddef.
    • Updated aws-actions/configure-aws-credentials from v5.1.1 to commit 61815dcd50bd041e203e49132bacad1fd04d2708.
    • Updated tailscale/github-action from v4 to commit 53acf823325fe9ca47f4cdaa951f90b4b0de5bb9.

Key Learnings & Insights

• Reasoning Behind Changes:
  • The updates were made to incorporate the latest changes and bug fixes from the respective GitHub Actions, enhancing the reliability and security of the CI/CD pipelines.
• Problem-Solving Approaches:
  • Identified the need for updates by reviewing the release notes and changelogs of the actions in use.
  • Ensured compatibility by testing the workflows in a staging environment before deploying to production.
• Best Practices Demonstrated:
  • Regularly updating dependencies to benefit from the latest features and security patches.
  • Using specific commits instead of tags to ensure precise control over the versions being used.

Impact Assessment

• System Effects:
  • The changes should not introduce breaking changes, as they are version updates within the same major version.
  • Improved reliability and security of the deployment and planning workflows.
• Performance & Security:
  • Potential performance improvements and security enhancements from the updated actions.
  • No immediate performance degradation expected.
• Maintainability:
  • Easier to maintain workflows with up-to-date actions, reducing technical debt.

Developer Notes

• Gotchas & Edge Cases:
  • Ensure that the new commits of the actions are compatible with the existing workflow configurations.
  • Monitor the initial runs of the updated workflows for any unexpected behavior.
• Context for Future Developers:
  • The choice to use specific commits over tags is to maintain precise control over the action versions.
  • Regularly review and update the actions to keep the workflows secure and efficient.
• Potential Future Improvements:
  • Automate the process of checking for updates to GitHub Actions to streamline maintenance.
  • Consider adopting a version management strategy for actions to simplify updates.