Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 11, 2025

This PR contains the following updates:

Package Change Age Confidence
semver 7.7.2 -> 7.7.3 age confidence

Release Notes

npm/node-semver (semver)

v7.7.3

Compare Source

Bug Fixes
Chores

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies help wanted Extra attention is needed labels Oct 11, 2025
Copy link
Contributor Author

renovate bot commented Oct 11, 2025

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot enabled auto-merge (squash) October 16, 2025 04:56
@renovate renovate bot force-pushed the renovate/semver-7.x branch 2 times, most recently from 8288641 to 75ae529 Compare October 16, 2025 08:48
Copy link
Contributor Author

renovate bot commented Oct 16, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @hello.nrfcloud.com/[email protected]
npm error Found: @aws-sdk/[email protected]
npm error node_modules/@aws-sdk/client-ecr
npm error   dev @aws-sdk/client-ecr@"3.901.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @aws-sdk/client-ecr@"^3.908.0" from @bifravst/[email protected]
npm error node_modules/@bifravst/aws-cdk-ecr-helpers
npm error   dev @bifravst/aws-cdk-ecr-helpers@"1.3.119" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-17T05_28_00_665Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-17T05_28_00_665Z-debug-0.log

@renovate renovate bot force-pushed the renovate/semver-7.x branch 3 times, most recently from 05315e9 to 481d574 Compare October 17, 2025 01:56
@renovate renovate bot force-pushed the renovate/semver-7.x branch from 481d574 to 35daf84 Compare October 17, 2025 05:28
@renovate renovate bot merged commit 43ab8fa into saga Oct 17, 2025
6 of 8 checks passed
@renovate renovate bot deleted the renovate/semver-7.x branch October 17, 2025 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies help wanted Extra attention is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants