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
tj-actions/changed-files	v46	v47	Release	ci.yaml

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.

[github-actions]

No linked issues found. Please link an issue in your pull request description or title.

Per our Contributing Guidelines, all PRs must:

• Reference an issue with one of:
  • Closing keywords: Fixes #123, Closes #123, Resolves #123 (auto-closes on merge in the same repository)
  • Reference keywords: Related to #123, Refs #123, Part of #123, See #123 (links without closing)
• The linked issue should have 5+ 👍 reactions from unique users (excluding bots and the PR author)
• Include discussion demonstrating the importance of the change

You can also use cross-repo references like owner/repo#123 or full URLs.

[github-actions]

❌ Infrastructure File Protection

This PR modifies protected infrastructure files:

• .github/workflows/ci.yaml (4 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

1. Revert changes to .github/ files
2. Use ./autoformat.sh to format only source code directories
3. Avoid running formatters on infrastructure files

If structural changes are necessary:

1. Open an issue describing the needed infrastructure changes
2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.

[salmanmkc]

hm really

[github-actions]

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

[github-actions]

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

[github-actions]

❌ Infrastructure File Protection

This PR modifies protected infrastructure files:

• .github/workflows/ci.yaml (4 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

1. Revert changes to .github/ files
2. Use ./autoformat.sh to format only source code directories
3. Avoid running formatters on infrastructure files

If structural changes are necessary:

1. Open an issue describing the needed infrastructure changes
2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.