Commit aaf93e5
authored
chore codfish/semantic-release-action from 3.5.0 to 4.0.0 in /.github/workflows (#10)
Bumps
[codfish/semantic-release-action](https://github.com/codfish/semantic-release-action)
from 3.5.0 to 4.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/codfish/semantic-release-action/releases">codfish/semantic-release-action's
releases</a>.</em></p>
<blockquote>
<h2>v4.0.0</h2>
<h1><a
href="https://github.com/codfish/semantic-release-action/compare/v3.5.0...v4.0.0">4.0.0</a>
(2025-08-18)</h1>
<h3>Features</h3>
<ul>
<li>upgrade semantic release & other dependencies to latest (<a
href="https://github.com/codfish/semantic-release-action/commit/df70072418dfb07d5a91c030528eb3605b01c6b2">df70072</a>),
closes <a
href="https://redirect.github.com/codfish/semantic-release-action/issues/211">#211</a></li>
</ul>
<h3>BREAKING CHANGES</h3>
<ul>
<li>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.</li>
<li><strong>From <a
href="https://github.com/semantic-release/semantic-release/releases/tag/v23.0.0">semantic
v23</a></strong>: 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 <a
href="https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0">https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0</a>
for more detail</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/22ce451ffd02a9ee2c4bfd126d028e4bd655770e"><code>22ce451</code></a>
Merge pull request <a
href="https://redirect.github.com/codfish/semantic-release-action/issues/214">#214</a>
from codfish/upgrades</li>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/df70072418dfb07d5a91c030528eb3605b01c6b2"><code>df70072</code></a>
feat: upgrade semantic release & other dependencies to latest</li>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/3dae0482fa9be59272a6727ff25adc8b014368c8"><code>3dae048</code></a>
chore: add ai context</li>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/12c84988adb09ed64f9ee253f679a2ffb203ac77"><code>12c8498</code></a>
docs: update README to update checkout version</li>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/14f7beb73f79f126539141e5aa436a1a1f161d34"><code>14f7beb</code></a>
ci: fix potential danger GitHub action (<a
href="https://redirect.github.com/codfish/semantic-release-action/issues/212">#212</a>)</li>
<li><a
href="https://github.com/codfish/semantic-release-action/commit/d7b2c852cb18ec0b46ae8a551dfb33c50bceec2c"><code>d7b2c85</code></a>
docs: update README.md to use latest docker digest</li>
<li>See full diff in <a
href="https://github.com/codfish/semantic-release-action/compare/v3.5.0...v4.0.0">compare
view</a></li>
</ul>
</details>
<br />
[](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)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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 <dependency name> 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)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 6ae82db commit aaf93e5
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
| 17 | + | |
18 | 18 | | |
19 | 19 | | |
0 commit comments