[PR #25] [MERGED] chore(deps-dev): bump @semantic-release/commit-analyzer from 11.1.0 to 12.0.0 #28

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/AppacYazilim/zamanejs/pull/25
Author: @dependabot[bot]
Created: 3/25/2024
Status: ✅ Merged
Merged: 4/4/2024
Merged by: @mehmeteminkartal

Base: main ← Head: dependabot/npm_and_yarn/semantic-release/commit-analyzer-12.0.0

📝 Commits (1)

ebbfb86 chore(deps-dev): bump @semantic-release/commit-analyzer

📊 Changes

2 files changed (+28 additions, -6 deletions)

View changed files

📝 package-lock.json (+27 -5)
📝 package.json (+1 -1)

📄 Description

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

Release notes

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

v12.0.0

12.0.0 (2024-03-18)

Features

exports: defined exports to point at ./index.js (f3358dd)

node-versions: dropped support for node v18 and v19 (0a23b82)

BREAKING CHANGES

exports: exports has been defined, which prevents access to private apis (which arent intended for consumption anyway)

node-versions: node v18 and v19 are no longer supported

Commits

820d6f4 Merge pull request #608 from semantic-release/corepack
f3358dd feat(exports): defined exports to point at ./index.js
5b6c43f chore(gitattributes): ensured consistent line endings across OSs
0a23b82 feat(node-versions): dropped support for node v18 and v19
e6e432d ci(verify): updated to modern conventions
cb0c6c4 ci(corepack): pinned the expected dev version of npm and explicitly used it f...
c25c252 chore(deps): update dependency ava to v6.1.2 (#603)
97ac9d5 chore(deps): lock file maintenance (#601)
698df9d chore(deps): lock file maintenance (#600)
a7116e8 chore(deps): lock file maintenance
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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/AppacYazilim/zamanejs/pull/25 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 3/25/2024 **Status:** ✅ Merged **Merged:** 4/4/2024 **Merged by:** [@mehmeteminkartal](https://github.com/mehmeteminkartal) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/semantic-release/commit-analyzer-12.0.0` --- ### 📝 Commits (1) - [`ebbfb86`](https://github.com/AppacYazilim/zamanejs/commit/ebbfb86137ca22112d1b586aff046e4365a1639a) chore(deps-dev): bump @semantic-release/commit-analyzer ### 📊 Changes **2 files changed** (+28 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+27 -5) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer) from 11.1.0 to 12.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>v12.0.0</h2> <h1><a href="https://github.com/semantic-release/commit-analyzer/compare/v11.1.0...v12.0.0">12.0.0</a> (2024-03-18)</h1> <h3>Features</h3> <ul> <li><strong>exports:</strong> defined <code>exports</code> to point at ./index.js (<a href="https://github.com/semantic-release/commit-analyzer/commit/f3358dd0ad0af2c7426fbc14077463fbadf47821">f3358dd</a>)</li> <li><strong>node-versions:</strong> dropped support for node v18 and v19 (<a href="https://github.com/semantic-release/commit-analyzer/commit/0a23b828fae80d083a59439101bea11e7e50fbc5">0a23b82</a>)</li> </ul> <h3>BREAKING CHANGES</h3> <ul> <li><strong>exports:</strong> <code>exports</code> has been defined, which prevents access to private apis (which arent intended for consumption anyway)</li> <li><strong>node-versions:</strong> node v18 and v19 are no longer supported</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/820d6f423a8c37bcfd5890729ff368f7fe64aa04"><code>820d6f4</code></a> Merge pull request <a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/608">#608</a> from semantic-release/corepack</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/f3358dd0ad0af2c7426fbc14077463fbadf47821"><code>f3358dd</code></a> feat(exports): defined <code>exports</code> to point at ./index.js</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/5b6c43fa6bca97029f3bb23c365a9ac1b3f590e5"><code>5b6c43f</code></a> chore(gitattributes): ensured consistent line endings across OSs</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/0a23b828fae80d083a59439101bea11e7e50fbc5"><code>0a23b82</code></a> feat(node-versions): dropped support for node v18 and v19</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/e6e432d7800699d0c40539b9be72d25e61d9d3ea"><code>e6e432d</code></a> ci(verify): updated to modern conventions</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/cb0c6c4c8616a3696b84c50c278ca18f0bb13139"><code>cb0c6c4</code></a> ci(corepack): pinned the expected dev version of npm and explicitly used it f...</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/c25c252cd0ab63caa37db5d155d7ce69d87e0821"><code>c25c252</code></a> chore(deps): update dependency ava to v6.1.2 (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/603">#603</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/97ac9d54e2416d4fdc0bc12c0adad2e6b86b9cb4"><code>97ac9d5</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/601">#601</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/698df9d339e75cb6615d7177c33205df5d8717d4"><code>698df9d</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/semantic-release/commit-analyzer/issues/600">#600</a>)</li> <li><a href="https://github.com/semantic-release/commit-analyzer/commit/a7116e8a652487a5e7772e9492a05c62b219ab97"><code>a7116e8</code></a> chore(deps): lock file maintenance</li> <li>Additional commits viewable in <a href="https://github.com/semantic-release/commit-analyzer/compare/v11.1.0...v12.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=11.1.0&new-version=12.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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>