cuttingedge icon indicating copy to clipboard operation
cuttingedge copied to clipboard

chore(deps): update dependency @types/node to v20.11.16

Open renovate[bot] opened this issue 2 years ago β€’ 2 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.11.7 -> 20.11.16 age adoption passing confidence

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

πŸ“… Schedule: Branch creation - "after 1pm and before 6pm every weekend" in timezone Europe/Dublin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

β™» Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Feb 03 '24 15:02 renovate[bot]

⚠ 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: pnpm-lock.yaml
Scope: all 19 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 17, reused 0, downloaded 11, added 0
/tmp/renovate/repos/github/dagda1/cuttingedge/apps/frontendsupport:
 ERR_PNPM_FETCH_403  GET https://npm.greensock.com/@gsap/shockingly/-/shockingly-3.12.5.tgz: Forbidden - 403

This error happened while installing a direct dependency of /tmp/renovate/repos/github/dagda1/cuttingedge/apps/frontendsupport

No authorization header was set for the request.

No authorization settings were found in the configs.
Try to log in to the registry by running "pnpm login"
or add the auth tokens manually to the ~/.npmrc file.

renovate[bot] avatar Feb 03 '24 15:02 renovate[bot]

⚠️ No Changeset found

Latest commit: 77d4080e3fba4a9b63e5dcc74eef0a09de59d10f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

changeset-bot[bot] avatar Feb 03 '24 15:02 changeset-bot[bot]