Upgrade actions checkout version.

Change Summary

This update involves modifying the GitHub Actions workflows (deploy.yml and plan.yml) to use a specific commit hash (8e8c483db84b4bee98b60c0593521ed34d9990e8) of the actions/checkout action instead of a version tag (v4).

Technical Details

• Files Modified:
  • .github/workflows/deploy.yml
  • .github/workflows/plan.yml
• Changes Made:
  • Replaced uses: actions/checkout@v4 with uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 in both workflow files.
• Reason for Change:
  • The specific commit hash is used to ensure consistency and avoid potential issues that might arise from using a version tag that could point to different commits over time.

Key Learnings & Insights

• Consistency in CI/CD Pipelines:
  • Using a specific commit hash for actions ensures that the CI/CD pipeline remains consistent across different runs, reducing the risk of introducing breaking changes due to updates in the action.
• Version Pinning:
  • Pinning to a specific commit is a best practice in CI/CD to maintain stability and predictability in the build and deployment processes.
• Trade-offs:
  • While pinning to a specific commit provides stability, it also means that automatic updates and bug fixes in newer versions of the action will not be utilized unless manually updated.

Impact Assessment

• System Stability:
  • This change enhances the stability of the CI/CD pipeline by ensuring that the actions/checkout action does not change unexpectedly.
• Maintenance:
  • Future updates to the actions/checkout action will require manual intervention to update the commit hash, which could introduce additional maintenance overhead.
• No Breaking Changes:
  • There are no breaking changes introduced by this update. However, it is important to monitor the specified commit for any deprecated features or security vulnerabilities.

Developer Notes

• Gotchas:
  • Ensure that the specified commit (8e8c483db84b4bee98b60c0593521ed34d9990e8) is thoroughly tested and does not contain any known issues.
• Future Improvements:
  • Consider implementing a process to regularly review and update the pinned commit to benefit from improvements and security patches in the actions/checkout action.
• Context for Future Developers:
  • This change was made to enhance pipeline stability. Future changes to the actions/checkout action should be carefully evaluated for their impact on the CI/CD process.