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 all non-major dependencies #127

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 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) ^2.27.9 -> ^2.27.11 age adoption passing confidence
@vercel/build-utils (source) ^8.4.12 -> ^8.8.0 age adoption passing confidence
@vercel/edge (source) ^1.1.2 -> ^1.1.4 age adoption passing confidence
@vercel/nft ^0.27.6 -> ^0.27.10 age adoption passing confidence
@vercel/node (source) ^3.2.24 -> ^3.2.29 age adoption passing confidence
esbuild ^0.24.0 -> ^0.24.2 age adoption passing confidence
typescript (source) ^5.6.3 -> ^5.7.2 age adoption passing confidence
vike ^0.4.203 -> ^0.4.211 age adoption passing confidence
zod (source) ^3.23.8 -> ^3.24.1 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.11

Compare Source

Patch Changes

v2.27.10

Compare Source

vercel/vercel (@​vercel/build-utils)

v8.8.0

Compare Source

Minor Changes
  • Add bun detection using bun.lock (#​12740)

v8.7.0

Compare Source

Minor Changes
  • Support splitting archive deployments in parts. (#​12671)

v8.6.0

Compare Source

Minor Changes
  • Add support for NOW_EPHEMERAL_FILES_S3_URL, NOW_FILES_CLOUDFRONT_URL and NOW_FILES_S3_URL environment variables (#​12643)

v8.5.0

Compare Source

Minor Changes
  • Remove VERCEL_ALLOW_NODEJS22 env var check (#​12614)
vercel/vercel (@​vercel/edge)

v1.1.4

Compare Source

Patch Changes
  • [vercel/edge] add geolocation.postalCode (#​12755)

v1.1.3

Compare Source

Patch Changes
  • update "rollup" to resolve vulnerability report (#​12686)
vercel/nft (@​vercel/nft)

v0.27.10

Compare Source

Bug Fixes

v0.27.9

Compare Source

Bug Fixes

v0.27.8

Compare Source

Bug Fixes

v0.27.7

Compare Source

Bug Fixes
vercel/vercel (@​vercel/node)

v3.2.29

Compare Source

Patch Changes

v3.2.28

Compare Source

Patch Changes

v3.2.27

Compare Source

Patch Changes

v3.2.26

Compare Source

Patch Changes

v3.2.25

Compare Source

Patch Changes
evanw/esbuild (esbuild)

v0.24.2

Compare Source

  • Fix regression with --define and import.meta (#​4010, #​4012, #​4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

v0.24.1

Compare Source

  • Allow es2024 as a target in tsconfig.json (#​4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
      "compilerOptions": {
        "target": "ES2024"
      }
    }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
      get
      *x() {}
      set
      *y() {}
    }

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#​4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    // The following code now transforms to "return true;\n"
    console.log(esbuild.transformSync(
      `return process.env['SOME-TEST-VAR']`,
      { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
    ))

    Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

  • Minify empty try/catch/finally blocks (#​4003)

    With this release, esbuild will now attempt to minify empty try blocks:

    // Original code
    try {} catch { foo() } finally { bar() }
    
    // Old output (with --minify)
    try{}catch{foo()}finally{bar()}
    
    // New output (with --minify)
    bar();

    This can sometimes expose additional minification opportunities.

  • Include entryPoint metadata for the copy loader (#​3985)

    Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

  • Source mappings may now contain null entries (#​3310, #​3878)

    With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

    This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

  • Avoid using the parent directory name for determinism (#​3998)

    To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

    This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

  • Experimental support for esbuild on NetBSD (#​3974)

    With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

microsoft/TypeScript (typescript)

v5.7.2

Compare Source

vikejs/vike (vike)

v0.4.211

Compare Source

Bug Fixes
  • add hint for window is not defined (7e270e9)
  • fix wrong alias assertion (07fd3f1)
  • remove assets from dist/server/ (fix #​2034) (c1cd2d9)
  • set host: true if inside docker container (cac186d)
  • stabilize extends order (fix #​2037) (d93dfe1)
  • support .{client,server.shared}.js for pointer imports (285fedb)

v0.4.210

Compare Source

Bug Fixes
  • change Vite 6 default port from 5731 to 3000 (9d68312)
Features

v0.4.209

Compare Source

Bug Fixes

v0.4.208

Compare Source

Bug Fixes

v0.4.207

Compare Source

Bug Fixes
Features
  • [experimental] getMiddlewares() (0d8ef7e)
  • [experimental] new config +middleware (d19051a)

v0.4.206

Compare Source

Bug Fixes

v0.4.205

Compare Source

Bug Fixes
Features

v0.4.204

Compare Source

Bug Fixes
  • fix export assertion (fix #​1964) (162a660)
  • fix resolving of relative URL with hash (9f54397)
  • improve client-side init execution order (fix #​1962) (#​1965) (1b14559)
  • improve detection of hash navigation link (953f625)
  • improve type of hashOriginal and searchOriginal (6c69cb5)
  • minor hash scrolling fix (b4c0f11)
  • workaround Firefox bug upon clicking hash link that doesn't change URL (fix #​1962) (cb7f3ff)
colinhacks/zod (zod)

v3.24.1

Compare Source

Commits:

v3.24.0

Compare Source

Implement @standard-schema/spec

This is the first version of Zod to implement the Standard Schema spec. This is a new community effort among several validation library authors to implement a common interface, with the goal of simplifying the process of integrating schema validators with the rest of the ecosystem. Read more about the project and goals here.

z.string().jwt()

Thanks to @​Mokshit06 and @​Cognition-Labs for this contribution!

To verify that a string is a valid 3-part JWT.

z.string().jwt();

⚠️ This does not verify your JWT cryptographically! It merely ensures its in the proper format. Use a library like jsonwebtoken to verify the JWT signature, parse the token, and read the claims.

To constrain the JWT to a specific algorithm:

z.string().jwt({ alg: "RS256" });

z.string().base64url()

Thank you to @​marvinruder!

To complement the JWT validation, Zod 3.24 implements a standalone .base64url() string validation API. (The three elements of JWTs are base64url-encoded JSON strings.)

z.string().base64url()

This functionality is available along the standard z.string().base64() validator added in Zod 3.23.

z.string().cidr()

Thanks to @​wataryooou for their work on this!

A validator for CIDR notation for specifying IP address ranges, e.g. 192.24.12.0/22.

z.string().cidr()

To specify an IP version:

z.string().cidr({ version: "v4" })
z.string().cidr({ version: "v6" })

View the full diff from 3.23.8: colinhacks/zod@v3.23.8...v3.24.0


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (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.

Copy link

vercel bot commented Nov 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
test-vite-vercel-plugin ✅ Ready (Inspect) Visit Preview Dec 28, 2024 0:53am

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4d6a114 to 1bf2640 Compare November 26, 2024 13:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1bf2640 to 5fd7dca Compare November 26, 2024 22:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5fd7dca to 292bc3a Compare November 27, 2024 16:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 292bc3a to 85ef6df Compare November 29, 2024 16:30
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 85ef6df to 4c1ab3e Compare November 30, 2024 22:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4c1ab3e to 149aeb2 Compare December 4, 2024 23:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 149aeb2 to cdef1f0 Compare December 9, 2024 15:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cdef1f0 to 253d53d Compare December 9, 2024 23:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 253d53d to 0df06e4 Compare December 10, 2024 02:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0df06e4 to e130521 Compare December 10, 2024 10:36
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Dec 10, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e130521 to cb86c3f Compare December 11, 2024 03:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cb86c3f to 42b9bee Compare December 12, 2024 15:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 42b9bee to c38fd76 Compare December 12, 2024 19:17
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