-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Prepare v5.0.0 release #1684
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
Prepare v5.0.0 release #1684
Conversation
- Bump package version to 5.0.0 - Add v5.0.0 release notes (Node.js 24 runtime + runner requirement)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR prepares the v5.0.0 release by bumping the package version and documenting the Node.js 24 runtime upgrade along with the minimum required Actions Runner version.
Key Changes:
- Version bump from 4.3.0 to 5.0.0 across package files
- Added release notes documenting Node.js 24 runtime and minimum runner requirement (v2.327.1)
- Introduced "Changelog" section header in RELEASES.md for improved organization
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updated version from 4.3.0 to 5.0.0 |
| package-lock.json | Updated version to 5.0.0 and standard lockfile maintenance (peer dependency bookkeeping changes) |
| RELEASES.md | Added v5.0.0 release notes with Node.js 24 runtime upgrade and minimum runner version requirement; introduced "Changelog" section header |
The PR is well-prepared with no issues identified. All version references are consistent, the release notes properly document the breaking changes (Node.js runtime upgrade and runner version requirement), and the changes follow the repository's established conventions for release documentation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Bumps [actions/cache](https://github.com/actions/cache) from 4.3.0 to 5.0.1. Release notes *Sourced from [actions/cache's releases](https://github.com/actions/cache/releases).* > v5.0.1 > ------ > > > [!IMPORTANT] > > **`actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`.** > > > > If you are using self-hosted runners, ensure they are updated before upgrading. > > --- > > v5.0.1 > ====== > > What's Changed > -------------- > > * fix: update `@actions/cache` for Node.js 24 punycode deprecation by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1685](https://redirect.github.com/actions/cache/pull/1685) > * prepare release v5.0.1 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1686](https://redirect.github.com/actions/cache/pull/1686) > > v5.0.0 > ====== > > What's Changed > -------------- > > * Upgrade to use node24 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1630](https://redirect.github.com/actions/cache/pull/1630) > * Prepare v5.0.0 release by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1684](https://redirect.github.com/actions/cache/pull/1684) > > **Full Changelog**: <actions/cache@v5...v5.0.1> > > v5.0.0 > ------ > > > [!IMPORTANT] > > **`actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`.** > > > > If you are using self-hosted runners, ensure they are updated before upgrading. > > --- > > What's Changed > -------------- > > * Upgrade to use node24 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1630](https://redirect.github.com/actions/cache/pull/1630) > * Prepare v5.0.0 release by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1684](https://redirect.github.com/actions/cache/pull/1684) > > **Full Changelog**: <actions/cache@v4.3.0...v5.0.0> Changelog *Sourced from [actions/cache's changelog](https://github.com/actions/cache/blob/main/RELEASES.md).* > Releases > ======== > > Changelog > --------- > > ### 5.0.1 > > * Update `@azure/storage-blob` to `^12.29.1` via `@actions/[email protected]` [#1685](https://redirect.github.com/actions/cache/pull/1685) > > ### 5.0.0 > > > [!IMPORTANT] > > `actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`. > > If you are using self-hosted runners, ensure they are updated before upgrading. > > ### 4.3.0 > > * Bump `@actions/cache` to [v4.1.0](https://redirect.github.com/actions/toolkit/pull/2132) > > ### 4.2.4 > > * Bump `@actions/cache` to v4.0.5 > > ### 4.2.3 > > * Bump `@actions/cache` to v4.0.3 (obfuscates SAS token in debug logs for cache entries) > > ### 4.2.2 > > * Bump `@actions/cache` to v4.0.2 > > ### 4.2.1 > > * Bump `@actions/cache` to v4.0.1 > > ### 4.2.0 > > TLDR; The cache backend service has been rewritten from the ground up for improved performance and reliability. [actions/cache](https://github.com/actions/cache) now integrates with the new cache service (v2) APIs. > > The new service will gradually roll out as of **February 1st, 2025**. The legacy service will also be sunset on the same date. Changes in these release are **fully backward compatible**. > > **We are deprecating some versions of this action**. We recommend upgrading to version `v4` or `v3` as soon as possible before **February 1st, 2025.** (Upgrade instructions below). > > If you are using pinned SHAs, please use the SHAs of versions `v4.2.0` or `v3.4.0` > > If you do not upgrade, all workflow runs using any of the deprecated [actions/cache](https://github.com/actions/cache) will fail. > > Upgrading to the recommended versions will not break your workflows. > > ### 4.1.2 ... (truncated) Commits * [`9255dc7`](actions/cache@9255dc7) Merge pull request [#1686](https://redirect.github.com/actions/cache/issues/1686) from actions/cache-v5.0.1-release * [`8ff5423`](actions/cache@8ff5423) chore: release v5.0.1 * [`9233019`](actions/cache@9233019) Merge pull request [#1685](https://redirect.github.com/actions/cache/issues/1685) from salmanmkc/node24-storage-blob-fix * [`b975f2b`](actions/cache@b975f2b) fix: add peer property to package-lock.json for dependencies * [`d0a0e18`](actions/cache@d0a0e18) fix: update license files for `@actions/cache`, fast-xml-parser, and strnum * [`74de208`](actions/cache@74de208) fix: update `@actions/cache` to ^5.0.1 for Node.js 24 punycode fix * [`ac7f115`](actions/cache@ac7f115) peer * [`b0f846b`](actions/cache@b0f846b) fix: update `@actions/cache` with storage-blob fix for Node.js 24 punycode depr... * [`a783357`](actions/cache@a783357) Merge pull request [#1684](https://redirect.github.com/actions/cache/issues/1684) from actions/prepare-cache-v5-release * [`3bb0d78`](actions/cache@3bb0d78) docs: highlight v5 runner requirement in releases * Additional commits viewable in [compare view](actions/cache@0057852...9255dc7) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps [actions/cache](https://github.com/actions/cache) from 4.3.0 to 5.0.1. Release notes *Sourced from [actions/cache's releases](https://github.com/actions/cache/releases).* > v5.0.1 > ------ > > > [!IMPORTANT] > > **`actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`.** > > > > If you are using self-hosted runners, ensure they are updated before upgrading. > > --- > > v5.0.1 > ====== > > What's Changed > -------------- > > * fix: update `@actions/cache` for Node.js 24 punycode deprecation by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1685](https://redirect.github.com/actions/cache/pull/1685) > * prepare release v5.0.1 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1686](https://redirect.github.com/actions/cache/pull/1686) > > v5.0.0 > ====== > > What's Changed > -------------- > > * Upgrade to use node24 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1630](https://redirect.github.com/actions/cache/pull/1630) > * Prepare v5.0.0 release by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1684](https://redirect.github.com/actions/cache/pull/1684) > > **Full Changelog**: <actions/cache@v5...v5.0.1> > > v5.0.0 > ------ > > > [!IMPORTANT] > > **`actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`.** > > > > If you are using self-hosted runners, ensure they are updated before upgrading. > > --- > > What's Changed > -------------- > > * Upgrade to use node24 by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1630](https://redirect.github.com/actions/cache/pull/1630) > * Prepare v5.0.0 release by [`@salmanmkc`](https://github.com/salmanmkc) in [actions/cache#1684](https://redirect.github.com/actions/cache/pull/1684) > > **Full Changelog**: <actions/cache@v4.3.0...v5.0.0> Changelog *Sourced from [actions/cache's changelog](https://github.com/actions/cache/blob/main/RELEASES.md).* > Releases > ======== > > Changelog > --------- > > ### 5.0.1 > > * Update `@azure/storage-blob` to `^12.29.1` via `@actions/[email protected]` [#1685](https://redirect.github.com/actions/cache/pull/1685) > > ### 5.0.0 > > > [!IMPORTANT] > > `actions/cache@v5` runs on the Node.js 24 runtime and requires a minimum Actions Runner version of `2.327.1`. > > If you are using self-hosted runners, ensure they are updated before upgrading. > > ### 4.3.0 > > * Bump `@actions/cache` to [v4.1.0](https://redirect.github.com/actions/toolkit/pull/2132) > > ### 4.2.4 > > * Bump `@actions/cache` to v4.0.5 > > ### 4.2.3 > > * Bump `@actions/cache` to v4.0.3 (obfuscates SAS token in debug logs for cache entries) > > ### 4.2.2 > > * Bump `@actions/cache` to v4.0.2 > > ### 4.2.1 > > * Bump `@actions/cache` to v4.0.1 > > ### 4.2.0 > > TLDR; The cache backend service has been rewritten from the ground up for improved performance and reliability. [actions/cache](https://github.com/actions/cache) now integrates with the new cache service (v2) APIs. > > The new service will gradually roll out as of **February 1st, 2025**. The legacy service will also be sunset on the same date. Changes in these release are **fully backward compatible**. > > **We are deprecating some versions of this action**. We recommend upgrading to version `v4` or `v3` as soon as possible before **February 1st, 2025.** (Upgrade instructions below). > > If you are using pinned SHAs, please use the SHAs of versions `v4.2.0` or `v3.4.0` > > If you do not upgrade, all workflow runs using any of the deprecated [actions/cache](https://github.com/actions/cache) will fail. > > Upgrading to the recommended versions will not break your workflows. > > ### 4.1.2 ... (truncated) Commits * [`9255dc7`](actions/cache@9255dc7) Merge pull request [#1686](https://redirect.github.com/actions/cache/issues/1686) from actions/cache-v5.0.1-release * [`8ff5423`](actions/cache@8ff5423) chore: release v5.0.1 * [`9233019`](actions/cache@9233019) Merge pull request [#1685](https://redirect.github.com/actions/cache/issues/1685) from salmanmkc/node24-storage-blob-fix * [`b975f2b`](actions/cache@b975f2b) fix: add peer property to package-lock.json for dependencies * [`d0a0e18`](actions/cache@d0a0e18) fix: update license files for `@actions/cache`, fast-xml-parser, and strnum * [`74de208`](actions/cache@74de208) fix: update `@actions/cache` to ^5.0.1 for Node.js 24 punycode fix * [`ac7f115`](actions/cache@ac7f115) peer * [`b0f846b`](actions/cache@b0f846b) fix: update `@actions/cache` with storage-blob fix for Node.js 24 punycode depr... * [`a783357`](actions/cache@a783357) Merge pull request [#1684](https://redirect.github.com/actions/cache/issues/1684) from actions/prepare-cache-v5-release * [`3bb0d78`](actions/cache@3bb0d78) docs: highlight v5 runner requirement in releases * Additional commits viewable in [compare view](actions/cache@0057852...9255dc7) [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Prepares the next release by documenting the Node.js 24 runtime upgrade and bumping the package version.
Changes: