Skip to content

chore(deps): update dependency wrangler to v3.114.15 #89

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.

Sign up for GitHub

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

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

chore(deps): update dependency wrangler to v3.114.15 #89

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 3, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) 3.62.0 -> 3.114.15 age confidence
wrangler (source) 3.62.0 -> 3.114.15 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.15

Compare Source

Patch Changes

v3.114.14

Compare Source

Patch Changes

  • #​10330 dab7683 Thanks @​petebacondarwin! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

    Previously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.

  • #​10233 a00a124 Thanks @​veggiedefender! - Increase the maxBuffer size for capnp uploads

  • #​10228 77a4364 Thanks @​dario-piotrowicz! - fix NonRetryableError thrown with an empty error message not stopping workflow retries locally

  • Updated dependencies []:

    • miniflare@​3.20250718.1

v3.114.13

Compare Source

Patch Changes

  • #​10015 b5d9bb0 Thanks @​dario-piotrowicz! - fix wrangler dev logs being logged on the incorrect level in some cases

    currently the way wrangler dev prints logs is faulty, for example the following code

    console.error("this is an error");
console.warn("this is a warning");
console.debug("this is a debug");

    inside a worker would cause the following logs:

    ✘ [ERROR] this is an error

✘ [ERROR] this is a warning

this is a debug

    (note that the warning is printed as an error and the debug log is printed even if by default it should not)

    the changes here make sure that the logs are instead logged to their correct level, so for the code about the following will be logged instead:

    ✘ [ERROR] this is an error

▲ [WARNING] this is a warning

    (running wrangler dev with the --log-level=debug flag will also cause the debug log to be included as well)

  • #​10187 f480ec7 Thanks @​workers-devprod! - Deleting when Pages project binds to worker requires confirmation

  • #​10182 1f686ef Thanks @​devin-ai-integration! - fix: report startup errors before workerd profiling

  • #​10226 989e17e Thanks @​petebacondarwin! - Enforce 64-character limit for Workflow binding names locally to match production validation

  • #​10216 76d3002 Thanks @​devin-ai-integration! - Add macOS version validation to prevent EPIPE errors on unsupported macOS versions (below 13.5). Miniflare and C3 fail hard while Wrangler shows warnings but continues execution.

  • #​10261 8c38b65 Thanks @​petebacondarwin! - fix: strip ANSI escape codes from log files to improve readability and parsing

  • #​10171 0d73563 Thanks @​devin-ai-integration! - Handle UTF BOM in config files - detect and remove UTF-8 BOMs, error on unsupported BOMs (UTF-16, UTF-32)

  • Updated dependencies [b5d9bb0, 76d3002]:

    • miniflare@​3.20250718.1

v3.114.12

Compare Source

Patch Changes

v3.114.11

Compare Source

Patch Changes

  • #​9685 cbea64b Thanks @​WillTaylorDev! - Select only successfully deployed deployments when tailing.

  • #​9776 6e09672 Thanks @​vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

  • #​9694 dacfc35 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

    this change makes sure that that getPlatformProxy, when the input configuration
    file contains an assets field, correctly returns the appropriate asset binding proxy

    example:

    // wrangler.jsonc
{
	"name": "my-worker",
	"assets": {
		"directory": "./public/",
		"binding": "ASSETS",
	},
}
    import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
console.log(text); // logs the content of file.txt

await dispose();

  • #​9807 4dd026b Thanks @​penalosa! - Better messaging for account owned tokens in wrangler whoami

v3.114.10

Compare Source

Patch Changes

v3.114.9

Compare Source

Patch Changes

v3.114.8

Compare Source

Patch Changes

  • #​9086 a2a56c8 Thanks @​petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

    Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

  • #​9037 d0d0025 Thanks @​CarmenPopoviciu! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.

  • #​9093 2f2f7ba Thanks @​CarmenPopoviciu! - fix: Validate input file for Vectorize inserts

  • Updated dependencies [fc04292, a01adca]:

    • miniflare@​3.20250408.1

v3.114.7

Compare Source

Patch Changes

  • #​8955 b7eba92 Thanks @​workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #​8928 8bcb257 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on
    deploy commands when an environment is specified and a redirected configuration
    is in use (the reason being that redirected configurations should not include
    any environment), this check is problematic with pages commands where the
    "production" environment is anyways set by default, to address this the validation
    check is being relaxed here on pages commands

v3.114.6

Compare Source

Patch Changes

  • #​8783 7bcf352 Thanks @​petebacondarwin! - Improve error message when request to obtain membership info fails

    Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

  • #​8866 db673d6 Thanks @​edmundhung! - improve error message when redirected config contains environments

    this change improves that validation error message that users see
    when a redirected config file contains environments, by:

    • cleaning the message formatting and displaying the
      offending environments in a list
    • prompting the user to report the issue to the author
      of the tool which has generated the config

  • #​8600 91cf028 Thanks @​workers-devprod! - add validation to redirected configs in regards to environments

    add the following validation behaviors to wrangler deploy commands, that relate
    to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

    • redirected configs are supposed to be already flattened configurations without any
      environment (i.e. a build tool should generate redirected configs already targeting specific
      environments), so if wrangler encounters a redirected config with some environments defined
      it should error
    • given the point above, specifying an environment (--env=my-env) when using redirected
      configs is incorrect, so these environments should be ignored and a warning should be
      presented to the user

v3.114.5

Compare Source

Patch Changes

v3.114.4

Compare Source

Patch Changes

v3.114.3

Compare Source

Patch Changes

v3.114.2

Compare Source

Patch Changes

v3.114.1

Compare Source

Patch Changes

  • #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

    The bulk put api has an optional "base64" boolean property for each key.
    Before storing the key, the value should be decoded from base64.

    For real (remote) kv, this is handled by the rest api. For local kv, it
    seems the base64 field was ignored, meaning encoded base64 content was
    stored locally rather than the raw values.

    To fix, we need to decode each value before putting to the local
    miniflare namespace when base64 is true.

  • #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

  • #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

    Fixes #​8407
    Fixes #​8409
    Fixes #​8411

  • #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

  • #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

    In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

    Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

  • Updated dependencies [8242e07, 53e6323]:

    • miniflare@​3.20250310.0

v3.114.0

Compare Source

Minor Changes
  • #​8367 7b6b0c2 Thanks @​jonesphillip! - Deprecated --id parameter in favor of --name for both the wrangler r2 bucket lifecycle and wrangler r2 bucket lock commands

v3.113.0

Compare Source

Minor Changes
Patch Changes

  • #​8338 2d40989 Thanks @​GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part of wrangler deploy and wrangler versions upload.

  • #​8288 cf14e17 Thanks @​CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflare

    This commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.

    This is an experimental feature available under the --x-assets-rpc flag: wrangler dev --x-assets-rpc.

  • #​8216 af9a57a Thanks @​ns476! - Support Images binding in wrangler types

  • #​8304 fbba583 Thanks @​jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookups

    Workers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.

    This change deduplicates these requests and adds concurrency to help speed up deployments.

  • Updated dependencies [2d40989, da568e5, cf14e17, 79c7810]:

    • miniflare@​3.20250224.0

v3.112.0

Compare Source

Minor Changes

  • #​8256 f59d95b Thanks @​jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-delivery

    These new commands allow users to pause and resume the delivery of messages to Queue Consumers

Patch Changes

v3.111.0

Compare Source

Minor Changes
Patch Changes

v3.110.0

Compare Source

Minor Changes
  • #​8253 6dd1e23 Thanks @​CarmenPopoviciu! - Add --cwd global argument to the wrangler CLI to allow changing the current working directory before running any command.
Patch Changes

v3.109.3

Compare Source

Patch Changes

v3.109.2

Compare Source

Patch Changes

v3.109.1

Compare Source

Patch Changes

v3.109.0

Compare Source

Minor Changes

  • #​8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

  • #​8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

  • #​8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

    This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

  • #​8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

    This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

    Advanced usage:

    • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
    • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/
Patch Changes

  • #​8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

  • #​8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

  • #​7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

  • #​8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

  • #​8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

    User provided strings are still left redacted as always.

  • #​8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

    Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

  • Updated dependencies [4db1fb5]:

    • miniflare@​3.20250204.1

v3.108.1

Compare Source

Patch Changes

  • #​8103 a025ad2 Thanks @​emily-shen! - fix: fix bug where wrangler secret list --format=json was printing the wrangler banner.

  • Updated dependencies []:

    • miniflare@​3.20250204.0

v3.108.0

Compare Source

Minor Changes

  • #​7990 b1966df Thanks @​cmsparks! - Add WRANGLER_CI_OVERRIDE_NAME for Workers CI

  • #​8028 b2dca9a Thanks @​emily-shen! - feat: Also log when no bindings are found.

    We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case you were expecting bindings.

  • #​8037 71fd250 Thanks @​WillTaylorDev! - Provides unsafe.metadata configurations when using wrangler versions secret put.

Patch Changes

  • #​8058 1f80d69 Thanks @​WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.

  • #​7986 88514c8 Thanks @​andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev

  • #​8008 9d08af8 Thanks @​ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Adds the following new option for wrangler pipelines create and wrangler pipelines update commands:

    --cors-origins           CORS origin allowlist for HTTP endpoint (use * for any origin)  [array]

  • #​7290 0c0374c Thanks @​emily-shen! - fix: add support for workers with assets when running multiple workers in one wrangler dev instance

    #​7251 added support for running multiple Workers in one wrangler dev/miniflare session. e.g. wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.

    However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Rename wrangler pipelines <create|update> flags

    The following parameters have been renamed:

    Previous Name New Name
    access-key-id r2-access-key-id
    secret-access-key r2-secret-access-key
    transform transform-worker
    r2 r2-bucket
    prefix r2-prefix
    binding enable-worker-binding
    http enable-http
    authentication require-http-auth
    filename file-template
    filepath partition-template

  • #​8012 c412a31 Thanks @​mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the API

    This fixes an issue where only 20 configs were being listed.

  • #​8077 60310cd Thanks @​emily-shen! - feat: add telemetry to experimental auto-provisioning

  • Updated dependencies [c80dbd8, 0c0374c]:

    • miniflare@​3.20250204.0

v3.107.3

[Compare Source](https://redirect.github.com/cloudflare/workers-sdk/compar

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 becomes conflicted, or you tick the rebase/retry checkbox.

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

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

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

@github-actions
Copy link

github-actions bot commented Jul 3, 2024 •
edited
Loading

Run report for 861350ab

Total time: 28.1s | Comparison time: 26.7s | Estimated loss: 1.4s (5.1% slower)

Action Time Status Info
🟩 SyncWorkspace 0ms Passed
⬛️ SetupToolchain(node:20.15.1) 2.1s Skipped
🟩 InstallWorkspaceDeps(node:20.15.1) 13.4s Passed
🟩 SyncProject(node, site) 0.3ms Passed
🟩 RunTask(site:imports) 475.6ms Passed
🟩 RunTask(site:sync) 3s Passed
🟩 RunTask(site:format) 423.3ms Passed
🟥 RunTask(site:check) 8.9s Failed
🟩 RunTask(site:lint) 327.2ms Passed
⬛️ RunTask(site:build) 0.1ms Skipped
Touched files
.github/workflows/deployment.yml
apps/site/package.json
pnpm-lock.yaml

@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from b6445fe to 9a90149 Compare July 4, 2024 19:07
@renovate renovate bot changed the title Update dependency wrangler to v3.63.0 Update dependency wrangler to v3.63.1 Jul 4, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 9a90149 to a7315bc Compare July 9, 2024 19:43
@renovate renovate bot changed the title Update dependency wrangler to v3.63.1 Update dependency wrangler to v3.63.2 Jul 9, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from a7315bc to a0d5724 Compare July 11, 2024 16:30
@renovate renovate bot changed the title Update dependency wrangler to v3.63.2 Update dependency wrangler to v3.64.0 Jul 11, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from a0d5724 to f6a591d Compare July 16, 2024 17:46
@renovate renovate bot changed the title Update dependency wrangler to v3.64.0 Update dependency wrangler to v3.65.0 Jul 16, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from f6a591d to 0f92495 Compare July 19, 2024 16:55
@renovate renovate bot changed the title Update dependency wrangler to v3.65.0 Update dependency wrangler to v3.65.1 Jul 19, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 0f92495 to fc0dfdc Compare July 23, 2024 17:31
@renovate renovate bot changed the title Update dependency wrangler to v3.65.1 Update dependency wrangler to v3.66.0 Jul 23, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from fc0dfdc to 56a994b Compare July 25, 2024 18:32
@renovate renovate bot changed the title Update dependency wrangler to v3.66.0 Update dependency wrangler to v3.67.0 Jul 25, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 56a994b to e47f74f Compare July 26, 2024 14:24
@renovate renovate bot changed the title Update dependency wrangler to v3.67.0 Update dependency wrangler to v3.67.1 Jul 26, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from e47f74f to 03da707 Compare August 1, 2024 13:22
@renovate renovate bot changed the title Update dependency wrangler to v3.67.1 Update dependency wrangler to v3.68.0 Aug 1, 2024
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 03da707 to 607df9c Compare August 6, 2024 20:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.3 chore(deps): update dependency wrangler to v3.114.4 Apr 3, 2025
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.4 chore(deps): update dependency wrangler to v3.114.5 Apr 9, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 7b964f6 to 6d9b573 Compare April 9, 2025 18:43
@github-actions github-actions bot requested a deployment to [site] (renovate/wrangler-3.x) April 9, 2025 18:44 Abandoned
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 6d9b573 to 861350a Compare April 14, 2025 16:30
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.5 chore(deps): update dependency wrangler to v3.114.6 Apr 14, 2025
@github-actions github-actions bot requested a deployment to [site] (renovate/wrangler-3.x) April 14, 2025 16:31 Abandoned
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 861350a to 0e48f9c Compare April 22, 2025 16:59
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.6 chore(deps): update dependency wrangler to v3.114.7 Apr 22, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 0e48f9c to 1ab6e41 Compare May 1, 2025 23:31
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.7 chore(deps): update dependency wrangler to v3.114.8 May 1, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 1ab6e41 to 3e0686e Compare May 22, 2025 17:11
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.8 chore(deps): update dependency wrangler to v3.114.9 May 22, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 3e0686e to 7619b00 Compare June 25, 2025 11:34
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.9 chore(deps): update dependency wrangler to v3.114.10 Jun 25, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 7619b00 to a0c6dfd Compare July 9, 2025 16:13
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.10 chore(deps): update dependency wrangler to v3.114.11 Jul 9, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from a0c6dfd to 198f9d2 Compare July 28, 2025 17:54
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.11 chore(deps): update dependency wrangler to v3.114.12 Jul 28, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 198f9d2 to ffd301d Compare August 7, 2025 21:31
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.12 chore(deps): update dependency wrangler to v3.114.13 Aug 7, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from ffd301d to 52e8294 Compare August 10, 2025 14:16
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 52e8294 to 13ab334 Compare August 20, 2025 17:10
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.13 chore(deps): update dependency wrangler to v3.114.14 Aug 20, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 13ab334 to 4d2cba4 Compare August 31, 2025 10:20
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 4d2cba4 to 0e937c7 Compare October 6, 2025 22:45
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.114.14 chore(deps): update dependency wrangler to v3.114.15 Oct 6, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 0e937c7 to 6bfb786 Compare October 21, 2025 14:56
@renovate
Copy link
Contributor Author

renovate bot commented Oct 21, 2025 •
edited
Loading

⚠️ 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 2 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        |  WARN  Package name mismatch found while reading {"tarball":"https://codeload.github.com/actions/github-script/tar.gz/ed597411d8f924073f98dfc5c65a23a2325f34cd"} from the store.
 ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE  The lockfile is broken! A full installation will be performed in an attempt to fix it.
Progress: resolved 48, reused 0, downloaded 0, added 0
 ERR_PNPM_UNEXPECTED_PKG_CONTENT_IN_STORE  Package name mismatch found while reading {"tarball":"https://codeload.github.com/actions/github-script/tar.gz/ed597411d8f924073f98dfc5c65a23a2325f34cd"} from the store.

This error happened while installing a direct dependency of /tmp/renovate/repos/github/astrolicious/dotdev

This means that either the lockfile is broken or the package metadata (name and version) inside the package's package.json file doesn't match the metadata in the registry. Expected package: github-script@undefined. Actual package in the store with the given integrity: @actions/[email protected].

If you want to ignore this issue, set the strict-store-pkg-content-check to false.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant