Skip to content

Upgrade GitHub Actions to latest versions#1390

Closed
salmanmkc wants to merge 1 commit intoEffect-TS:mainfrom
salmanmkc:upgrade-github-actions-node24-general
Closed

Upgrade GitHub Actions to latest versions#1390
salmanmkc wants to merge 1 commit intoEffect-TS:mainfrom
salmanmkc:upgrade-github-actions-node24-general

Conversation

@salmanmkc
Copy link
Copy Markdown

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
changesets/action v1 v1.7.0 Release release.yml
peter-evans/create-or-update-comment v4 v5 Release bundle-comment.yml, jsdoc-analysis-comment.yml
peter-evans/create-pull-request v7 v8 Release ai-codegen.yml
peter-evans/find-comment v3 v4 Release bundle-comment.yml, jsdoc-analysis-comment.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

⚠️ Breaking Changes

  • peter-evans/create-pull-request (v7 → v8): Major version upgrade — review the release notes for breaking changes
  • peter-evans/find-comment (v3 → v4): Major version upgrade — review the release notes for breaking changes
  • peter-evans/create-or-update-comment (v4 → v5): Major version upgrade — review the release notes for breaking changes

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.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 21, 2026

⚠️ No Changeset found

Latest commit: 7fef465

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

sed -i 's/"stripInternal": false/"stripInternal": true/' tsconfig.base.json
- name: Create Release Pull Request or Publish
uses: changesets/action@v1
uses: changesets/action@v1.7.0
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a superfluous change. v1 will still use v1.7.0 given semver.

@IMax153
Copy link
Copy Markdown
Member

IMax153 commented Mar 12, 2026

Superceded by #1724

@IMax153 IMax153 closed this Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants