Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency pino-pretty to v13 #196

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pino-pretty 11.3.0 -> 13.0.0 age adoption passing confidence

Release Notes

pinojs/pino-pretty (pino-pretty)

v13.0.0

Compare Source

v12.1.0

Compare Source

What's Changed

Full Changelog: pinojs/pino-pretty@v12.0.0...v12.1.0

v12.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: pinojs/pino-pretty@v11.3.0...v12.0.0


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 force-pushed the renovate/pino-pretty-13.x branch from 6853910 to 809c4fa Compare November 11, 2024 04:27
Copy link
Contributor Author

renovate bot commented Nov 11, 2024

⚠️ 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: yarn.lock
node:fs:1371
  const result = binding.mkdir(
                         ^

Error: ENOENT: no such file or directory, mkdir '/home/ubuntu/.cache/node/corepack/v1'
    at mkdirSync (node:fs:1371:26)
    at getTemporaryFolder (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:21486:27)
    at download (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:21760:21)
    at installVersion (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:21854:61)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:22310:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:22410:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/20.18.0/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/ubuntu/.cache/node/corepack/v1'
}

Node.js v20.18.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants