Skip to content

Conversation

@wolfy1339
Copy link
Member

Resolves #ISSUE_NUMBER


Before the change?

  • Used Node 16 for the update-prettier workflow

After the change?

  • Use Node LTS instead of pinning to a specific version

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@wolfy1339 wolfy1339 added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Mar 19, 2025
@github-actions
Copy link

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

@oscard0m oscard0m enabled auto-merge (squash) May 7, 2025 09:04
@oscard0m oscard0m force-pushed the ci-node-version branch from 29ec54b to 4fc50fc Compare May 7, 2025 09:04
@oscard0m oscard0m merged commit 39f8b45 into main May 7, 2025
7 checks passed
@oscard0m oscard0m deleted the ci-node-version branch May 7, 2025 09:05
@github-project-automation github-project-automation bot moved this from 🆕 Triage to ✅ Done in 🧰 Octokit Active May 7, 2025
@github-actions
Copy link

🎉 This PR is included in version 16.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

3 participants