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): lock file maintenance everything #321

Merged
merged 1 commit into from
Jun 10, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
@cloudflare/workers-types devDependencies minor ^4.20240423.0 -> ^4.20240605.0 age adoption passing confidence
@sanity/client (source) dependencies minor 6.15.20 -> 6.19.1 age adoption passing confidence
@sanity/ui (source) dependencies minor 2.1.4 -> 2.3.1 age adoption passing confidence
@tanstack/react-table (source) dependencies minor 8.16.0 -> 8.17.3 age adoption passing confidence
@types/react (source) devDependencies minor ^18.2.79 -> ^18.3.3 age adoption passing confidence
eslint-config-next (source) devDependencies patch ^14.2.2 -> ^14.2.3 age adoption passing confidence
wrangler (source) devDependencies minor ^3.51.2 -> ^3.60.0 age adoption passing confidence
bun-types (source) dependencies patch 1.1.4 -> 1.1.12 age adoption passing confidence
cloudflare/wrangler-action action minor v3.4.1 -> v3.6.1 age adoption passing confidence
next (source) dependencies patch 14.2.2 -> 14.2.3 age adoption passing confidence
oven-sh/setup-bun action digest 8f24390 -> f4d14e0
prettier (source) devDependencies minor ^3.2.5 -> ^3.3.1 age adoption passing confidence
react-dom (source) dependencies minor 18.2.0 -> 18.3.1 age adoption passing confidence
tailwindcss (source) devDependencies patch ^3.4.3 -> ^3.4.4 age adoption passing confidence
styled-components (source) dependencies patch 6.1.8 -> 6.1.11 age adoption passing confidence
@sanity/semantic-release-preset (source) devDependencies patch ^4.1.7 -> ^4.1.8 age adoption passing confidence
prettier-plugin-tailwindcss devDependencies minor ^0.5.14 -> ^0.6.2 age adoption passing confidence
zod (source) dependencies patch 3.23.4 -> 3.23.8 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.


Release Notes

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

v4.20240605.0

Compare Source

v4.20240603.0

Compare Source

v4.20240529.0

Compare Source

v4.20240524.0

Compare Source

v4.20240512.0

Compare Source

v4.20240502.0

Compare Source

sanity-io/client (@​sanity/client)

v6.19.1

Compare Source

Bug Fixes
  • types: adjust action types to reflect Actions API (#​830) (e116c62)

v6.19.0

Compare Source

Features

v6.18.3

Compare Source

Bug Fixes

v6.18.2

Compare Source

Bug Fixes

v6.18.1

Compare Source

Bug Fixes

v6.18.0

Compare Source

Features

v6.17.3

Compare Source

Bug Fixes

v6.17.2

Compare Source

Bug Fixes

v6.17.1

Compare Source

Bug Fixes

v6.17.0

Compare Source

Features
  • update SanityProject to include metadata.cliInitializedAt (#​779) (77bf6f6)

v6.16.0

Compare Source

Features
  • add stegaClean method, deprecate vercelStegaCleanAll (#​773) (2749586)
Bug Fixes
sanity-io/ui (@​sanity/ui)

v2.3.1

Compare Source

Bug Fixes

v2.3.0

Compare Source

Features

v2.2.0

Compare Source

Features
  • card: add muted property (f70bff6)

v2.1.14

Compare Source

Bug Fixes

v2.1.13

Compare Source

Bug Fixes

v2.1.12

Compare Source

Bug Fixes

v2.1.11

Compare Source

Bug Fixes

v2.1.10

Compare Source

Bug Fixes

v2.1.9

Compare Source

Bug Fixes

v2.1.8

Compare Source

Bug Fixes

v2.1.7

Compare Source

Bug Fixes
  • menu: remove use of isElement (68f9620)

v2.1.6

Compare Source

Bug Fixes

v2.1.5

Compare Source

Bug Fixes
  • theme: align disabled input colors with button colors (98710cc)
  • theme: improve avatar colors (4bbb42a)
  • theme: improve code and muted colors (1e33341)
  • theme: use correct base bg for avatar (618c194)
TanStack/table (@​tanstack/react-table)

v8.17.3

Compare Source

Version 8.17.3 - 5/14/2024, 2:44 PM

Changes
Fix
Packages

v8.17.0

Compare Source

Version 8.17.0 - 5/12/2024, 7:21 PM

Changes

Feat
Chore
Docs
Other

Packages

vercel/next.js (eslint-config-next)

v14.2.3

Compare Source

cloudflare/workers-sdk (wrangler)

v3.60.0

Compare Source

Minor Changes
  • #​5878 1e68fe5 Thanks @​IgorMinar! - feat: add experimental support for hybrid Node.js compatibility

    This feature is experimental and not yet available for general consumption.

    Use a combination of workerd Node.js builtins (behind the experimental:nodejs_compat_v2 flag) and
    Unenv polyfills (configured to only add those missing from the runtime) to provide a new more effective
    Node.js compatibility approach.

  • #​5988 e144f63 Thanks @​RamIdeas! - feature: rename the wrangler secret:bulk command to wrangler secret bulk

    The old command is now deprecated (but still functional) and will be removed in a future release. The new command is now more consistent with the rest of the wrangler CLI commands.

  • #​5989 35b1a2f Thanks @​RamIdeas! - feature: rename wrangler kv:... commands to wrangler kv ...

    The old commands are now deprecated (but still functional) and will be removed in a future release. The new commands are now more consistent with the rest of the wrangler CLI commands.

  • #​5861 1cc52f1 Thanks @​zebp! - feat: allow for Pages projects to upload sourcemaps

    Pages projects can now upload sourcemaps for server bundles to enable remapped stacktraces in realtime logs when deployed with upload_source_map set to true in wrangler.toml.

Patch Changes
  • #​5939 21573f4 Thanks @​penalosa! - refactor: Adds the experimental flag --x-dev-env which opts in to using an experimental code path for wrangler dev and wrangler dev --remote. There should be no observable behaviour changes when this flag is enabled.

  • #​5934 bac79fb Thanks @​dbenCF! - fix: Update create KV namespace binding details message for easier implementation

  • #​5927 6f83641 Thanks @​CarmenPopoviciu! - fix: Clean pages dev terminal ouput

    This work includes a series of improvements to the pages dev terminal output, in an attempt to make this output more structured, organised, cleaner, easier to follow, and therefore more helpful for our users <3

  • #​5960 e648825 Thanks @​petebacondarwin! - fix: avoid injecting esbuild watch stubs into production Worker code

    When we added the ability to include additional modules in the deployed bundle of a Worker,
    we inadvertently also included some boiler plate code that is only needed at development time.

    This fix ensures that this code is only injected if we are running esbuild in watch mode
    (e.g. wrangler dev) and not when building for deployment.

    It is interesting to note that this boilerplate only gets included in the production code
    if there is an import of CommonJS code in the Worker, which esbuild needs to convert to an
    ESM import.

    Fixes #​4269

  • Updated dependencies [ab95473]:

v3.59.0

Compare Source

Minor Changes
  • #​5963 bf803d7 Thanks @​Skye-31! - Feature: Add support for hiding the "unsafe" fields are experimental warning using an environment variable

    By setting WRANGLER_DISABLE_EXPERIMENTAL_WARNING to any truthy value, these warnings will be hidden.

Patch Changes

v3.58.0

Compare Source

Minor Changes
  • #​5933 93b98cb Thanks @​WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.
Patch Changes
  • #​5938 9e4d8bc Thanks @​threepointone! - fix: let "assets" in wrangler.toml be a string

    The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

  • #​5758 8e5e589 Thanks @​Jackenmen! - fix: use correct type for AI binding instead of unknown

  • Updated dependencies [e0e7725]:

v3.57.2

Compare Source

Patch Changes

v3.57.1

Compare Source

Patch Changes
  • #​5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #​5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log
    an error message, but exit successfully. It should instead throw a
    FatalError.

  • #​5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #​5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

v3.57.0

Compare Source

Minor Changes
  • #​5696 7e97ba8 Thanks @​geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

  • #​5819 63f7acb Thanks @​CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

    Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

    ✨ Deployment complete!
    

    This commit ensures that we provide users with:

    • the correct feedback with respect to their Pages deployment
    • the appropriate messaging depending on the status of their project's deployment status
    • the appropriate logs in case of a deployment failure
  • #​5814 2869e03 Thanks @​CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

    Running wrangler pages --help will list, amongst others, the following global flags:

    -j, --experimental-json-config
    -c, --config
    -e, --env
    -h, --help
    -v, --version
    

    This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

    This commit ensures we display the correct global flags that apply to Pages.

  • #​5818 df2daf2 Thanks @​WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

    If you're currently using the old binding, please move over to the new version_metadata binding by adding:

    [version_metadata]
    binding = "CF_VERSION_METADATA"

    and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes
  • #​5838 609debd Thanks @​petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

  • #​5832 86a6e09 Thanks @​petebacondarwin! - fix: do not allow non-string values in bulk secret uploads

    Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a
    JSON file that contained non-string secrets, since these are not supported
    by the Cloudflare backend.

    This change reintroduces that check to give the user a helpful error message
    rather than a cryptic workers.api.error.invalid_script_config error code.

v3.56.0

Compare Source

Minor Changes
  • #​5712 151bc3d Thanks @​penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project
Patch Changes
  • #​5813 9627cef Thanks @​GregBrimble! - fix: Upload Pages project assets with more grace

    • Reduces the maximum bucket size from 50 MiB to 40 MiB.
    • Reduces the maximum asset count from 5000 to 2000.
    • Allows for more retries (with increased sleep between attempts) when encountering an API gateway failure.
  • Updated dependencies [0725f6f, 89b6d7f]:

v3.55.0

Compare Source

Minor Changes
  • #​5570 66bdad0 Thanks @​sesteves! - feature: support delayed delivery in the miniflare's queue simulator.

    This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.

Patch Changes
  • #​5740 97741db Thanks @​WalshyDev! - chore: log "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback to support migration from the deprecated "Deployment ID". Users should update any parsing to use "Version ID" before "Deployment ID" is removed.

  • #​5754 f673c66 Thanks @​RamIdeas! - fix: when using custom builds, the wrangler dev proxy server was sometimes left in a paused state

    This could be observed as the browser loading indefinitely, after saving a source file (unchanged) when using custom builds. This is now fixed by ensuring the proxy server is unpaused after a short timeout period.

  • Updated dependencies [66bdad0, 9b4af8a]:

v3.53.1

Compare Source

Patch Changes
  • #​5091 6365c90 Thanks @​Cherry! - fix: better handle dashes and other invalid JS identifier characters in wrangler types generation for vars, bindings, etc.

    Previously, with the following in your wrangler.toml, an invalid types file would be generated:

    [vars]
    some-var = "foobar"

    Now, the generated types file will be valid:

    interface Env {
    	"some-var": "foobar";
    }
  • #​5748 27966a4 Thanks @​penalosa! - fix: Load sourcemaps relative to the entry directory, not cwd.

  • #​5746 1dd9f7e Thanks @​petebacondarwin! - fix: suggest trying to update Wrangler if there is a newer one available after an unexpected error

  • #​5226 f63e7a5 Thanks @​DaniFoldi! - fix: remove second Wrangler banner from wrangler dispatch-namespace rename

v3.53.0

Compare Source

Minor Changes
  • #​5604 327a456 Thanks @​dario-piotrowicz! - feat: add support for environments in getPlatformProxy

    allow getPlatformProxy to target environments by allowing users to specify an environment option

    Example usage:

    const { env } = await getPlatformProxy({
    	environment: "production",
    });
Patch Changes

v3.52.0

Compare Source

Minor Changes
  • #​5666 81d9615 Thanks @​CarmenPopoviciu! - fix: Fix Pages config validation around Durable Objects

    Today Pages cannot deploy Durable Objects itself. For this reason it is mandatory that when declaring Durable Objects bindings in the config file, the script_name is specified. We are currently not failing validation if
    script_name is not specified but we should. These changes fix that.

Patch Changes
oven-sh/bun (bun-types)

v1.1.12

Compare Source

[v1.1.11](https://togithub.com/oven-sh/bun/


Configuration

📅 Schedule: Branch creation - "every 12 months on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate bot requested a review from a team as a code owner June 10, 2024 09:44
Copy link

socket-security bot commented Jun 10, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@cloudflare/[email protected] None 0 3.67 MB wrangler-publisher
npm/@sanity/[email protected] Transitive: environment, network +25 7.46 MB sanity-io
npm/@sanity/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +221 31.6 MB sanity-io
npm/@sanity/[email protected] Transitive: environment +33 12 MB sanity-io
npm/@tanstack/[email protected] Transitive: environment +1 4.04 MB tannerlinsley
npm/@types/[email protected] None +1 2.04 MB types
npm/@types/[email protected] None 0 2.06 MB types
npm/@types/[email protected] None +2 1.69 MB types
npm/[email protected] None +1 385 kB robobun
npm/[email protected] unsafe Transitive: environment, eval, filesystem, shell +208 53.1 MB vercel-release-bot
npm/[email protected] environment, filesystem, network, shell, unsafe +23 1.2 GB vercel-release-bot
npm/[email protected] None 0 0 B
npm/[email protected] environment, filesystem, unsafe 0 8.25 MB prettier-bot
npm/[email protected] environment +3 4.63 MB react-bot
npm/[email protected] environment +12 3.42 MB probablyup
npm/[email protected] environment, filesystem Transitive: network, shell, unsafe +101 14 MB adamwathan
npm/[email protected] Transitive: environment, filesystem, network, shell, unsafe +74 793 MB
npm/[email protected] None 0 667 kB colinmcd94

🚮 Removed packages: npm/@cloudflare/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@tanstack/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Copy link

socket-security bot commented Jun 10, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@cloudflare/[email protected], npm/@emotion/[email protected], npm/@emotion/[email protected], npm/@eslint-community/[email protected], npm/@floating-ui/[email protected], npm/@floating-ui/[email protected], npm/@floating-ui/[email protected], npm/@floating-ui/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@next/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@rushstack/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sanity/[email protected], npm/@sec-ant/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/@sindresorhus/[email protected], npm/@tanstack/[email protected], npm/@tanstack/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@stipsan
Copy link
Member

stipsan commented Jun 10, 2024

@SocketSecurity ignore-all

@stipsan stipsan merged commit 346d2d0 into main Jun 10, 2024
7 checks passed
@stipsan stipsan deleted the renovate/everything branch June 10, 2024 09:49
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.

1 participant