Upgrade GitHub Actions to latest versions

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action	Old Version(s)	New Version	Release	Files
aws-actions/configure-aws-credentials	v4	v5	Release	ci.yml, images.yml
peter-evans/create-pull-request	v5	v8	Release	i18n.yml
softprops/action-gh-release	v1	v2	Release	publish-python-sdk.yml, publish-ts-sdk.yml

Why upgrade?

Keeping GitHub Actions up to date ensures:

• Security: Latest security patches and fixes
• Features: Access to new functionality and improvements
• Compatibility: Better support for current GitHub features
• Performance: Optimizations and efficiency improvements

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

[vercel]

@salmanmkc is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

Updated three GitHub Actions to their latest versions across five workflow files for security patches, bug fixes, and new features.

• aws-actions/configure-aws-credentials v4→v5 in ci.yml and images.yml
• peter-evans/create-pull-request v5→v8 in i18n.yml
• softprops/action-gh-release v1→v2 in publish-python-sdk.yml and publish-ts-sdk.yml

The changes are minimal version bumps with no configuration changes, maintaining backward compatibility with existing workflow parameters.

Confidence Score: 5/5

• Safe to merge - straightforward dependency updates with no breaking changes
• All changes are simple version bumps to well-maintained GitHub Actions. No workflow configuration changes were needed, indicating backward compatibility. The actions maintain the same API surface and parameters.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/ci.yml	Updated aws-actions/configure-aws-credentials from v4 to v5 for AWS authentication
.github/workflows/i18n.yml	Updated peter-evans/create-pull-request from v5 to v8 for automated translation PRs
.github/workflows/images.yml	Updated aws-actions/configure-aws-credentials from v4 to v5 for AWS authentication
.github/workflows/publish-python-sdk.yml	Updated softprops/action-gh-release from v1 to v2 for creating GitHub releases
.github/workflows/publish-ts-sdk.yml	Updated softprops/action-gh-release from v1 to v2 for creating GitHub releases

Sequence Diagram

sequenceDiagram
    participant GH as GitHub
    participant CI as CI Workflow
    participant AWS as AWS Configure v5
    participant I18N as I18N Workflow
    participant PR as Create PR v8
    participant SDK as SDK Workflows
    participant Release as GH Release v2

    Note over GH,Release: Main CI/CD Pipeline

    GH->>CI: Push to main/staging
    CI->>AWS: Configure AWS credentials
    AWS->>CI: Return ECR registry access
    CI->>CI: Build and push Docker images

    GH->>I18N: Weekly schedule or manual trigger
    I18N->>I18N: Run translations
    I18N->>PR: Create pull request with changes
    PR->>GH: Submit automated translation PR

    GH->>SDK: Push to main (SDK changes)
    SDK->>SDK: Run tests and build
    SDK->>Release: Create GitHub release
    Release->>GH: Publish new SDK version

Loading

[greptile-apps]

Greptile's behavior is changing!

From now on, if a review finishes with no comments, we will not post an additional "statistics" comment to confirm that our review found nothing to comment on. However, you can confirm that we reviewed your changes in the status check section.

_{This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR".}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 25, 2026 5:16am

[waleedlatif1]

@salmanmkc please rebase now that I've changed the head to staging instead of main

[salmanmkc]

@salmanmkc please rebase now that I've changed the head to staging instead of main

done