[PR #80] chore(deps-dev): bump @semantic-release/commit-analyzer from 12.0.0 to 13.0.0 #81

New issue

Open

opened 2026-03-02 02:26:32 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:26:32 +03:00

Owner

Original Pull Request: https://github.com/AppacYazilim/zamanejs/pull/80

State: open
Merged: No

Bumps @semantic-release/commit-analyzer from 12.0.0 to 13.0.0.

Release notes

Sourced from @semantic-release/commit-analyzer's releases.

v13.0.0

13.0.0 (2024-05-31)

Bug Fixes

log the raw message again (e2f5d6c)

Features

support latest conventional-changelog packages (0254d7a)

BREAKING CHANGES

by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

v13.0.0-beta.2

13.0.0-beta.2 (2024-05-25)

Bug Fixes

log the raw message again (e2f5d6c)

v13.0.0-beta.1

13.0.0-beta.1 (2024-05-25)

Features

support latest conventional-changelog packages (0254d7a)

BREAKING CHANGES

by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

Commits

9d5b993 Merge pull request #653 from semantic-release/beta
e2f5d6c fix: log the raw message again
6a89bd9 refactor(prettier): fixed style problems
3953810 docs(maintainers): added myself to the contributors list
0254d7a feat: support latest conventional-changelog packages
7a2902e chore(deps): lock file maintenance (#651)
5d86f0b chore(deps): update dependency publint to v0.2.8 (#650)
6c5506b chore(deps): update dependency npm-run-all2 to v6.2.0 (#649)
9e7ce45 ci(action): update actions/checkout action to v4.1.6 (#648)
8fb7af8 chore(deps): update npm to v10.8.0 (#647)
Additional commits viewable in compare view

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 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 <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)

**Original Pull Request:** https://github.com/AppacYazilim/zamanejs/pull/80 **State:** open **Merged:** No --- Bumps [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer) from 12.0.0 to 13.0.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/semantic-release/commit-analyzer/releases"><code>@semantic-release/commit-analyzer</code>'s releases</a>.</em></p> <blockquote> <h2>v13.0.0</h2> <h1><a href="https://github.com/semantic-release/commit-analyzer/compare/v12.0.0...v13.0.0">13.0.0</a> (2024-05-31)</h1> <h3>Bug Fixes</h3> <ul> <li>log the raw message again (<a href="https://github.com/semantic-release/commit-analyzer/commit/e2f5d6c4594be06b2e3b822217920099fd264fec">e2f5d6c</a>)</li> </ul> <h3>Features</h3> <ul> <li>support latest conventional-changelog packages (<a href="https://github.com/semantic-release/commit-analyzer/commit/0254d7a5c59ccc4692b86218554f8850ebf46682">0254d7a</a>)</li> </ul> <h3>BREAKING CHANGES</h3> <ul> <li>by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config</li> </ul> <h2>v13.0.0-beta.2</h2> <h1><a href="https://github.com/semantic-release/commit-analyzer/compare/v13.0.0-beta.1...v13.0.0-beta.2">13.0.0-beta.2</a> (2024-05-25)</h1> <h3>Bug Fixes</h3> <ul> <li>log the raw message again (<a href="https://github.com/semantic-release/commit-analyzer/commit/e2f5d6c4594be06b2e3b822217920099fd264fec">e2f5d6c</a>)</li> </ul> <h2>v13.0.0-beta.1</h2> <h1><a href="https://github.com/semantic-release/commit-analyzer/compare/v12.0.0...v13.0.0-beta.1">13.0.0-beta.1</a> (2024-05-25)</h1> <h3>Features</h3> <ul> <li>support latest conventional-changelog packages (<a href="https://github.com/semantic-release/commit-analyzer/commit/0254d7a5c59ccc4692b86218554f8850ebf46682">0254d7a</a>)</li> </ul> <h3>BREAKING CHANGES</h3> <ul> <li>by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/9d5b993083585a396b8380f2bb2af6241c1dd3a8"><code>9d5b993</code></a> Merge pull request <a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/653">#653</a> from semantic-release/beta</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/e2f5d6c4594be06b2e3b822217920099fd264fec"><code>e2f5d6c</code></a> fix: log the raw message again</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/6a89bd9ca41fe0fc1af286154debd2d2ef2b7bea"><code>6a89bd9</code></a> refactor(prettier): fixed style problems</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/395381044d1cd12145406f1581cc72e320c9be71"><code>3953810</code></a> docs(maintainers): added myself to the contributors list</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/0254d7a5c59ccc4692b86218554f8850ebf46682"><code>0254d7a</code></a> feat: support latest conventional-changelog packages</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/7a2902e73b5aada0ab7a2781843a653b8033e0da"><code>7a2902e</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/651">#651</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/5d86f0b0bc039c16cc41c9bcb3cd17ebe691edcc"><code>5d86f0b</code></a> chore(deps): update dependency publint to v0.2.8 (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/650">#650</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/6c5506b8961d9ed38c7d020f3cb0765d7e8b6663"><code>6c5506b</code></a> chore(deps): update dependency npm-run-all2 to v6.2.0 (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/649">#649</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/9e7ce450412810b31245ca83a10fae4469e7cba3"><code>9e7ce45</code></a> ci(action): update actions/checkout action to v4.1.6 (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/648">#648</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/8fb7af85c064fc3ccc6ceba8136aeea2ac672594"><code>8fb7af8</code></a> chore(deps): update npm to v10.8.0 (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/647">#647</a>)</li> <li>Additional commits viewable in <a href="https://github.com/semantic-release/commit-analyzer/compare/v12.0.0...v13.0.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@semantic-release/commit-analyzer&package-manager=npm_and_yarn&previous-version=12.0.0&new-version=13.0.0)](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>