chore(deps): update all to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
codfish/semantic-release-action	action	major	v1.9.0 → v5.0.0

---

Release Notes

codfish/semantic-release-action (codfish/semantic-release-action)

v5.0.0

Compare Source

Features

• upgrade deps, node, bump semantic-release to v25 (#​231) (6abd188)

BREAKING CHANGES

• @​semantic-release/github no longer consumes the GitHub Search API in the plugin.

Upgraded to semantic-release v25 with breaking changes in the GitHub plugin.
Any breaking changes from v25 apply to this github action version except for
Node version requirements. Because this is a docker-based github action, the
version of node in use is defined inside of the docker image, not by the
consuming runner or your code.

• @​semantic-release/github v12: The GitHub plugin no longer uses the GitHub
  Search API (/search/issues endpoint). It now uses GraphQL queries exclusively
  for issue retrieval. This architectural change may affect issue management in
  edge cases. See github plugin v12 release notes.

• semantic-release v25: Upgraded from v24.2.7 to v25.0.3

  • @​semantic-release/npm upgraded to v13
  • @​semantic-release/commit-analyzer and @​semantic-release/release-notes-generator moved from beta to stable
  • Dependency updates (yargs v18, hosted-git-info v9)
  • See semantic-release v25 release notes

• npm OIDC Trusted Publishing Support: The upgrade to @​semantic-release/npm v13 enables
  support for npm's new OIDC-based trusted publishing. This allows publishing to npm without
  long-lived access tokens by using GitHub's OIDC token provider. This is more secure and
  eliminates the need to store NPM_TOKEN as a repository secret when publishing from GitHub
  Actions. See npm documentation
  for configuration details.

• Node.js: Upgraded to v24.13.0 (bundled in Docker, not a breaking change for users)

• @​actions/core: Upgraded to v3.0.0 (internal implementation only)

1. Test in a separate branch first - the GitHub plugin's architectural change
   could affect issue management behavior
2. Review semantic-release v25 changes
3. Review @​semantic-release/github v12 changes
4. Update your workflows to use @v5
5. (Optional) Migrate to npm OIDC Trusted Publishing:
   • Configure your package on npmjs.com to enable trusted publishing from GitHub Actions
   • Add id-token: write permission to your workflow job
   • Remove the NPM_TOKEN secret (you won't need it anymore!)
   • See npm's trusted publishing guide

• v5 uses semantic-release v25 & node v24.13.0
• v4 uses semantic-release v24 & node v22.18.0
• v3 uses semantic-release v22 & node v20.9
• v2 uses semantic-release v20 & node v18.7

Compare: codfish/semantic-release-action@v4.0.1...v5.0.0

• upgrade to semantic-release v25, @​actions/core v3, Node v24.13.0, and update dev tooling

• semantic-release: v24.2.7 → v25.0.3
• @​semantic-release/github: v11 → v12
• @​semantic-release/npm: v12 → v13
• @​actions/core: v1.11.1 → v3.0.0
• Node.js: v22.18.0 → v24.13.0
• Dev tooling: Migrated from cod-scripts to eslint + vitest

v5

Compare Source

v4.0.1

Compare Source

Bug Fixes

• install additional packages to /action to avoid package manager issues (91fdaf1)

v4.0.0

Compare Source

Features

• upgrade semantic release & other dependencies to latest (df70072), closes #​211

BREAKING CHANGES

• Migrated to semantic-release v24. Any breaking changes from v23 and v24 apply to this github action version except for Node version requirements. Because this is a docker-based github action, the version of node in use is defined inside of the docker image, not by the consuming runner or your code.
• From semantic v23: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory or renamed to .releaserc.js to keep it in the root of the repository. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail

v4

Compare Source

v3.5.0

Compare Source

Features

• add working-directory input (#​210) (b621d34), closes #​209

v3.4.1

Compare Source

Bug Fixes

• update release workflow to ensure every docker tag is pushed (#​208) (9a999e0)

v3.4.0

Compare Source

Features

• add arm platform support (ac1b7f3), closes #​207

v3.3.0

Compare Source

Features

• use node v20.12.1 and use node-slim instead of alpine (#​205) (b0e57c9), closes #​204

v3.2.0

Compare Source

Features

• reduce container size (f93cffb), closes #​202

v3.1.1

Compare Source

Bug Fixes

• respect semantic config if it exists (37e061a), closes #​199

v3.1.0

Compare Source

Bug Fixes

• set default values in the entrypoint (1370f92)

Features

• bump node to v20.11.0 (a7d7235)

v3.0.0

Compare Source

Bug Fixes

• run safe-directory on /github/workspace (3e26d45)

Features

• bump semantic to v22, use node v20 (7f2510c)
• include main branch by default, update input casing (ad7eb9d)

BREAKING CHANGES

• Using semantic-release v22. Please see release notes:

  • https://github.com/semantic-release/semantic-release/releases/tag/v21.0.0
  • https://github.com/semantic-release/semantic-release/releases/tag/v22.0.0

• All inputs are using kebab case rather than snake. Simply update the following inputs if you are using them:

  • additional_packages -> additional-packages
  • dry_run -> dry-run
  • repository_url -> repository-url
  • tag_format -> tag-format

v3

Compare Source

v2.2.1

Compare Source

Bug Fixes

• force install additional plugins (78f3935)
• revert back to 18.7.0 (b81ef1d)

v2.2.0

Compare Source

Features

• add type, channel, gitHead, gitTag, name outputs (04df07b)

v2.1.0

Compare Source

Features

• bump to semantic-release v20, @​actions/core v1.10 (3f78bff)

v2.0.0

Compare Source

Features

• bump senamtic to v19, migrate to node v18 (f6e72fb), closes #​173

BREAKING CHANGES

• Runs using nodejs v18.x and npm v8 now,
  so any dependencies specified in extends or additional_packages
  that have dependency conflicts with semantic-release v19.x will
  cause the action to fail.

v2

Compare Source

v1.10.0

Compare Source

Features

• add additional_packages input variable (892c8c9), closes #​168

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.