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

fix(deps): update core #81

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

fix(deps): update core #81

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 18, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-sdk/client-s3 (source) 3.744.0 -> 3.750.0 age adoption passing confidence
@cloudflare/vitest-pool-workers (source) ^0.6.0 -> ^0.7.0 age adoption passing confidence
@cloudflare/workers-types 4.20250204.0 -> 4.20250224.0 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) 8.23.0 -> 8.25.0 age adoption passing confidence
@typescript-eslint/parser (source) 8.23.0 -> 8.25.0 age adoption passing confidence
tsx (source) 4.19.2 -> 4.19.3 age adoption passing confidence
wrangler (source) 3.107.3 -> 3.110.0 age adoption passing confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.750.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.749.0

Compare Source

Features
  • client-s3: Added support for Content-Range header in HeadObject response. (5b15ad8)
cloudflare/workers-sdk (@​cloudflare/vitest-pool-workers)

v0.7.3

Compare Source

Patch Changes

v0.7.2

Compare Source

Patch Changes

v0.7.1

Compare Source

Patch Changes

v0.7.0

Compare Source

Minor Changes
  • #​7923 aaa9cca Thanks @​penalosa! - Support Vitest v3. While this drops testing for Vitest v2, we expect Vitest v2 will continue to work as well.
Patch Changes

v0.6.16

Compare Source

Patch Changes

v0.6.15

Compare Source

Patch Changes

v0.6.14

Compare Source

Patch Changes

v0.6.13

Compare Source

Patch Changes
cloudflare/workerd (@​cloudflare/workers-types)

v4.20250224.0

Compare Source

v4.20250214.0

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.25.0

Compare Source

🚀 Features
  • eslint-plugin: [no-misused-spread] add suggestions (#​10719)
🩹 Fixes
  • eslint-plugin: [prefer-nullish-coalescing] report on chain expressions in a ternary (#​10708)
  • eslint-plugin: [no-deprecated] report usage of deprecated private identifiers (#​10844)
  • eslint-plugin: [unified-signatures] handle getter-setter (#​10818)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.24.1

Compare Source

🩹 Fixes
  • eslint-plugin: [class-methods-use-this] check accessor methods with a function initializer (#​10796)
  • eslint-plugin: [no-misused-promises] don't report on static accessor properties (#​10814)
  • eslint-plugin: [no-deprecated] don't report on deprecated accessor property declaration (#​10813)
  • eslint-plugin: [explicit-member-accessibility] check accessor class properties for missing accessibility modifier (#​10805)
  • eslint-plugin: [explicit-module-boundary-types] check accessor class properties with a function initializer (#​10804)
  • eslint-plugin: [prefer-return-this-type] check accessor properties with a function initializer (#​10794)
  • eslint-plugin: [consistent-generic-constructors] check accessor class properties (#​10789)
  • eslint-plugin: [no-unsafe-assignment] report on an any value assigned as an initializer of an accessor property (#​10785)
  • eslint-plugin: [no-unnecessary-template-expression] ignore enum and enum members (#​10782)
  • eslint-plugin: [no-inferrable-types] handle accessor (#​10780)
❤️ Thank You
  • Ronen Amiel
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v8.24.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unnecessary-condition] make allowConstantLoopConditions more granular (#​10639)
🩹 Fixes
  • eslint-plugin: [no-misused-spread] correct and elaborate string spread report message (#​10751)
  • eslint-plugin: [restrict-plus-operands] report adding bigints to strings when allowNumberAndString is false (#​10737)
❤️ Thank You
  • Josh Goldberg ✨
  • noah
  • Ronen Amiel

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.25.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.24.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.24.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

privatenumber/tsx (tsx)

v4.19.3

Compare Source

Bug Fixes
  • upgrade esbuild to ~0.25.0 to address vuln report (#​698) (e04e6c6)

This release is also available on:

cloudflare/workers-sdk (wrangler)

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]:

v3.108.1

Compare Source

Patch Changes

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

    https://github.com/cloudflare/workers-sdk/pull/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]:


Configuration

📅 Schedule: Branch creation - "on tuesday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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/core branch 3 times, most recently from b755d73 to f3bb8f9 Compare February 19, 2025 21:56
@renovate renovate bot changed the title chore(deps): update core fix(deps): update core Feb 19, 2025
@renovate renovate bot force-pushed the renovate/core branch 6 times, most recently from a6f436f to 4e7cbc6 Compare February 25, 2025 12:52
@renovate renovate bot force-pushed the renovate/core branch 2 times, most recently from b5708f3 to d598470 Compare March 1, 2025 17:50
@renovate renovate bot force-pushed the renovate/core branch from d598470 to dc031fa Compare March 3, 2025 03:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants