[PR #67] [MERGED] chore(deps-dev): bump @semantic-release/github from 10.0.5 to 10.0.6 #65

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/AppacYazilim/zamanejs/pull/67
Author: @dependabot[bot]
Created: 6/10/2024
Status: ✅ Merged
Merged: 6/28/2024
Merged by: @mehmeteminkartal

Base: main ← Head: dependabot/npm_and_yarn/semantic-release/github-10.0.6

📝 Commits (1)

2bf1a6d chore(deps-dev): bump @semantic-release/github from 10.0.5 to 10.0.6

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 package-lock.json (+3 -3)

📄 Description

Bumps @semantic-release/github from 10.0.5 to 10.0.6.

Release notes

Sourced from @semantic-release/github's releases.

v10.0.6

10.0.6 (2024-06-05)

Bug Fixes

corrected homepage link in package.json so the generated links in the errors are valid (#848) (865762d)

Commits

865762d fix: corrected homepage link in package.json so the generated links in the er...
c150f3d chore(deps): lock file maintenance (#847)
80bb1d1 chore(deps): update dependency prettier to v3.3.0 (#845)
2ace0e6 chore(deps): update dependency semantic-release to v24 (#844)
0fd9192 chore(deps): update npm to v10.8.1 (#842)
1660909 chore(deps): lock file maintenance (#841)
See full diff 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/67 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/10/2024 **Status:** ✅ Merged **Merged:** 6/28/2024 **Merged by:** [@mehmeteminkartal](https://github.com/mehmeteminkartal) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/semantic-release/github-10.0.6` --- ### 📝 Commits (1) - [`2bf1a6d`](https://github.com/AppacYazilim/zamanejs/commit/2bf1a6dbe052d41f97dea617722f9bac5de2dcd9) chore(deps-dev): bump @semantic-release/github from 10.0.5 to 10.0.6 ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+3 -3) </details> ### 📄 Description Bumps [@semantic-release/github](https://github.com/semantic-release/github) from 10.0.5 to 10.0.6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/semantic-release/github/releases"><code>@semantic-release/github</code>'s releases</a>.</em></p> <blockquote> <h2>v10.0.6</h2> <h2><a href="https://github.com/semantic-release/github/compare/v10.0.5...v10.0.6">10.0.6</a> (2024-06-05)</h2> <h3>Bug Fixes</h3> <ul> <li>corrected homepage link in package.json so the generated links in the errors are valid (<a href="https://redirect.github.com/semantic-release/github/issues/848">#848</a>) (<a href="https://github.com/semantic-release/github/commit/865762db8e90530b45f3009bc15ab88166e25405">865762d</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/semantic-release/github/commit/865762db8e90530b45f3009bc15ab88166e25405"><code>865762d</code></a> fix: corrected homepage link in package.json so the generated links in the er...</li> <li><a href="https://github.com/semantic-release/github/commit/c150f3dbf6f1d67988fcee7f27278739b9a227d6"><code>c150f3d</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/semantic-release/github/issues/847">#847</a>)</li> <li><a href="https://github.com/semantic-release/github/commit/80bb1d1af68dee9f4c77ca4abcce0a6b27264701"><code>80bb1d1</code></a> chore(deps): update dependency prettier to v3.3.0 (<a href="https://redirect.github.com/semantic-release/github/issues/845">#845</a>)</li> <li><a href="https://github.com/semantic-release/github/commit/2ace0e64f7aa3edf196fed7e50f4f6f9c10d11ec"><code>2ace0e6</code></a> chore(deps): update dependency semantic-release to v24 (<a href="https://redirect.github.com/semantic-release/github/issues/844">#844</a>)</li> <li><a href="https://github.com/semantic-release/github/commit/0fd9192b36499da66cfc221d314425143732d505"><code>0fd9192</code></a> chore(deps): update npm to v10.8.1 (<a href="https://redirect.github.com/semantic-release/github/issues/842">#842</a>)</li> <li><a href="https://github.com/semantic-release/github/commit/1660909f70c4c05b3e6ed79d6afddd8b499ad784"><code>1660909</code></a> chore(deps): lock file maintenance (<a href="https://redirect.github.com/semantic-release/github/issues/841">#841</a>)</li> <li>See full diff in <a href="https://github.com/semantic-release/github/compare/v10.0.5...v10.0.6">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@semantic-release/github&package-manager=npm_and_yarn&previous-version=10.0.5&new-version=10.0.6)](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>