chore(deps): bump @tootallnate/once, semantic-release and @semantic-release/npm in /packages/fetch#11042
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Conversation
…elease/npm Removes [@tootallnate/once](https://github.com/TooTallNate/once). It's no longer used after updating ancestor dependencies [@tootallnate/once](https://github.com/TooTallNate/once), [semantic-release](https://github.com/semantic-release/semantic-release) and [@semantic-release/npm](https://github.com/semantic-release/npm). These dependencies need to be updated together. Removes `@tootallnate/once` Updates `semantic-release` from 21.1.2 to 25.0.3 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v21.1.2...v25.0.3) Updates `@semantic-release/npm` from 10.0.6 to 13.1.5 - [Release notes](https://github.com/semantic-release/npm/releases) - [Commits](semantic-release/npm@v10.0.6...v13.1.5) --- updated-dependencies: - dependency-name: "@tootallnate/once" dependency-version: dependency-type: indirect - dependency-name: semantic-release dependency-version: 25.0.3 dependency-type: direct:development - dependency-name: "@semantic-release/npm" dependency-version: 13.1.5 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dosubot
bot
added
the
size:XS
Contributor
Documentation ReviewNo documentation updates needed for this PR. Reason: This PR bumps internal dev dependencies ( |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/fetch/package.json">
<violation number="1" location="packages/fetch/package.json:29">
P1: Upgrading to `semantic-release` v25 is incompatible with this package’s release workflow Node runtime (`.nvmrc` is Node 20), so `npx semantic-release` can fail in CI. Update the release job to Node >=22.14 (preferably current LTS) before this dependency bump.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "@semantic-release/npm": "^10.0.6", | ||
| "semantic-release": "^21.1.2" | ||
| "@semantic-release/npm": "^13.1.5", | ||
| "semantic-release": "^25.0.3" |
Contributor
There was a problem hiding this comment.
P1: Upgrading to semantic-release v25 is incompatible with this package’s release workflow Node runtime (.nvmrc is Node 20), so npx semantic-release can fail in CI. Update the release job to Node >=22.14 (preferably current LTS) before this dependency bump.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/fetch/package.json, line 29:
<comment>Upgrading to `semantic-release` v25 is incompatible with this package’s release workflow Node runtime (`.nvmrc` is Node 20), so `npx semantic-release` can fail in CI. Update the release job to Node >=22.14 (preferably current LTS) before this dependency bump.</comment>
<file context>
@@ -25,7 +25,7 @@
- "@semantic-release/npm": "^10.0.6",
- "semantic-release": "^21.1.2"
+ "@semantic-release/npm": "^13.1.5",
+ "semantic-release": "^25.0.3"
}
}
</file context>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes @tootallnate/once. It's no longer used after updating ancestor dependencies @tootallnate/once, semantic-release and @semantic-release/npm. These dependencies need to be updated together.
Removes
@tootallnate/onceUpdates
semantic-releasefrom 21.1.2 to 25.0.3Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
f404124fix(deps): remove deprecated semver-diff (#3980)fef7e34docs: warn against using registry-url in setup-node (#4024)699d470chore(deps): update dependency lockfile-lint to v5 (#4022)c7c6f7achore(deps): update dependency tempy to v3.1.2 (#4021)1ce5088ci(action): update github/codeql-action action to v4.32.0 (#4019)9bb0d87chore(deps): lock file maintenance (#4016)490171cchore(deps): update npm to v11.8.0 (#4015)f6411e9chore(deps): update dependency prettier to v3.8.1 (#4014)c71c576chore(deps): update dependency publint to v0.3.17 (#4013)989e18cchore(deps): update dependency tempy to v3.1.1 (#4012)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for semantic-release since your current version.
Updates
@semantic-release/npmfrom 10.0.6 to 13.1.5Release notes
Sourced from
@semantic-release/npm's releases.... (truncated)
Commits
daec492fix(deps): update dependency normalize-url to v9 (#1095)af8362fchore(deps): update dependency strip-ansi to v7.2.0 (#1098)7354e11chore(deps): update node.js to v24 (#1027)2c4d2c9chore(deps): update npm to v11.11.0 (#1097)95ba689chore(deps): update dependency c8 to v11 (#1096)5d32912chore(deps): update npm to v11.10.1 (#1094)54f908cchore(deps): lock file maintenance (#1093)91e1f14chore(deps): update npm to v11.10.0 (#1092)0d7d37echore(deps): lock file maintenance (#1089)c5411ccchore(deps): update npm to v11.9.0 (#1088)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@semantic-release/npmsince your current version.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Continue Tasks: ✅ 7 no changes — View all
Summary by cubic
Update release tooling in packages/fetch by bumping semantic-release and @semantic-release/npm, and removing the unused @tootallnate/once. This keeps our release pipeline current and reduces unnecessary dependencies.
Written for commit 15ab4e4. Summary will update on new commits.