Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(.github): update action version in workflow files #3086

Merged

Conversation

sukvvon
Copy link
Contributor

@sukvvon sukvvon commented Jan 8, 2025

Closes #

📝 Description

Add a brief description

Updated the versions of actions in the workflow files, including actions/setup-node to v4, actions/checkout to v4, and slackapi/slack-github-action to v2, to ensure compatibility and leverage the latest features and fixes provided by these releases.

⛳️ Current behavior (updates)

Please describe the current behavior that you are modifying

  • The workflow currently uses an older version of actions/setup-node (e.g., v2 or v3), which may lack the latest updates or features available in the v4 release.
  • The workflow uses an older version of actions/checkout that may not include the improvements and optimizations available in the v4 release.
  • The workflow uses an older version of slackapi/slack-github-action, which may not include the updates and fixes provided in the v2 release.

🚀 New behavior

Please describe the behavior or changes this PR adds

  • The workflow now uses actions/setup-node@v4, providing improved performance, new features, and the latest fixes introduced in the updated version.
  • The workflow now uses actions/checkout@v4, incorporating the latest enhancements for managing repository checkouts during workflows.
  • The workflow now uses slackapi/slack-github-action@v2, enabling better integration with Slack and leveraging the latest improvements and fixes.

💣 Is this a breaking change (Yes/No):

No.

📝 Additional Information

Copy link

changeset-bot bot commented Jan 8, 2025

⚠️ No Changeset found

Latest commit: a609158

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

Copy link

vercel bot commented Jan 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
panda-docs ✅ Ready (Inspect) Visit Preview Jan 8, 2025 0:04am
panda-playground ✅ Ready (Inspect) Visit Preview Jan 8, 2025 0:04am
panda-studio ✅ Ready (Inspect) Visit Preview Jan 8, 2025 0:04am

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