Sourced from next's releases.

v15.3.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOutput (#78488) (#78883)
• @​next/mdx: Use stable turbopack config options (#78880)
• Fix react-compiler: Fix detection of interest (#78879)
• Fix turbopack: Backport sourcemap bugfix (#78881)
• [next-server] preserve rsc query for rsc redirects (#78876)
• Update middleware public/static matching (#78875)

Credits

Huge thanks to @​ijjk, @​huozhi, @​kdy1, @​wbinnssmith, and @​bgw for helping!

• d9ec4a4 v15.3.2
• 3def5ff backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOu...
• d0b2f8a @​next/mdx: Use stable turbopack config options (#78880)
• 04176de fix(react-compiler): Fix detection of interest (#78879)
• b40778b fix(turbopack): Backport sourcemap bugfix (#78881)
• 20f3120 [next-server] preserve rsc query for rsc redirects (#78876)
• b464d18 Update middleware public/static matching (#78875)
• See full diff in compare view

Sourced from esbuild's releases.

v0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com
    

  • JS:

    const ctx = await esbuild.context({})
    await ctx.serve({
      servedir: '.',
      cors: {
        origin: 'https://example.com',
      },
    })
    

  • Go:

    ctx, _ := api.Context(api.BuildOptions{})
    ctx.Serve(api.ServeOptions{
      Servedir: ".",
      CORS: api.CORSOptions{
        Origin: []string{"https://example.com"},
      },
    })
    

  The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

• Handle exports named __proto__ in ES modules (#4162, #4163)

  In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

  This fix was contributed by @​magic-akari.

... (truncated)

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  
  class Foo extends Bar {
  
  constructor() {
  
  super();
  
  this.#private = 1;
  
  }
  
  #private;
  
  }
  // Old output (with esbuild v0.19.10)
  
  class Foo extends Bar {
  
  constructor() {
  
  this.#private = 1;
  
  super();
  
  }
  
  #private;
  
  }
  // New output
  
  class Foo extends Bar {
  
  #private = 1;
  
  constructor() {
  
  super();
  
  }
  
  }
  
  

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

• 218d29e publish 0.25.4 to npm
• e66cd0b dev server: simple support for CORS requests (#4171)
• 8bf3368 js api: validate some options as arrays of strings
• 1e7375a js api: simplify comma-separated array validation
• 5f5964d release notes for #4163
• adb5284 fix: handle __proto__ as a computed property in exports and add tests for s...
• 0aa9f7b fix #4169: keep invalid source map URLs unmodified
• 5959289 add additional guards for #4114 when using :is()
• 677910b publish 0.25.3 to npm
• a41040e fix #4110: support custom non-IP host values
• Additional commits viewable in compare view

Sourced from drizzle-kit's releases.

drizzle-kit@0.31.1

Fixed drizzle-kit pull bugs when using Gel extensions.

Because Gel extensions create schema names containing :: (for example, ext::auth), Drizzle previously handled these names incorrectly. Starting with this release, you can use Gel extensions without any problems. Here’s what you should do:

1. Enable extensions schemas in drizzle.config.ts

import  { defineConfig } from "drizzle-kit";
export default defineConfig({
dialect: 'gel',
schemaFilter: ['ext::auth', 'public']
});

2. Run drizzle-kit pull

3. Done!

drizzle-kit@0.31.0

Features and improvements

Enum DDL improvements

For situations where you drop an enum value or reorder values in an enum, there is no native way to do this in PostgreSQL. To handle these cases, drizzle-kit used to:

• Change the column data types from the enum to text
• Drop the old enum
• Add the new enum
• Change the column data types back to the new enum

However, there were a few scenarios that weren’t covered: PostgreSQL wasn’t updating default expressions for columns when their data types changed

Therefore, for cases where you either change a column’s data type from an enum to some other type, drop an enum value, or reorder enum values, we now do the following:

• Change the column data types from the enum to text
• Set the default using the ::text expression
• Drop the old enum
• Add the new enum
• Change the column data types back to the new enum
• Set the default using the :: expression

esbuild version upgrade

For drizzle-kit we upgraded the version to latest (0.25.2), thanks @​paulmarsicloud

Bug fixes

• [BUG]: Error on Malformed Array Literal - thanks @​Kratious

... (truncated)

• efb40fe Add fix for Gel Schemas (#4483)
• ad28dcd Fixed pgSchema enum types (fixes #4421) (#4450)
• 2263c3c v0.43.0 (#4397)
• 9e81def Update CI/CD to 22.04
• df6d5f7 0.41 (#4416)
• 6ab1bbe Add Arktype validation (via drizzle-arktype package) (#4314)
• See full diff in compare view

Sourced from react-email's releases.

react-email@4.0.13

Patch Changes

• 8e4afce: fix hot reloading support for users with NodeNext-style imports

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.12...react-email@4.0.13

react-email@4.0.12

Patch Changes

• aa518a3: Add an explicit error when running Node <= 17

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.11...react-email@4.0.12

react-email@4.0.11

Patch Changes

• 1a17219: fix improper require in email export
• 45ab698: update next to 15.3.1

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.10...react-email@4.0.11

react-email@4.0.10

Patch Changes

• 5ef9fe8: fix support for import ... = require(...) syntax
• 4c7f597: fix email dev not working with traversal error

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.9...react-email@4.0.10

react-email@4.0.9

Patch Changes

• 643d841: Add .json import support for hot reloading
• f21a983: fix Node 18 support
• cd02449: Ensure dependencies outside emails directory are completely resolved
• 73a31ed: Fix dependent of dependents not causing hot reloads
• bdffd8c: fix backwards compatibility with render versions
• e7fa043: Fix access to files outside static directory
• 9aa033c: Use range of versions for dependencies
• ab70556: Fix non-email files being rendered during hot reloading
• 9c9aa5d: Add error message for when an email template does not have a default export

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.8...react-email@4.0.9

react-email@4.0.8

[!NOTE] This is a release to backport fixes, it does not contain what was released in the latest canaries.

Patch changes

... (truncated)

Sourced from react-email's changelog.

4.0.13

Patch Changes

• 8e4afce: fix hot reloading support for users with NodeNext-style imports

4.0.12

Patch Changes

• aa518a3: Add an explicit error when running Node <= 17

4.0.11

Patch Changes

• 1a17219: fix improper require in email export
• 45ab698: update next to 15.3.1

4.0.10

Patch Changes

• 5ef9fe8: fix support for import ... = require(...) syntax
• 4c7f597: fix email dev not working with traversal error

4.0.9

Patch Changes

• 643d841: Add .json import support for hot reloading
• f21a983: fix Node 18 support
• cd02449: Ensure dependencies outside emails directory are completely resolved
• 73a31ed: Fix dependent of dependents not causing hot reloads
• bdffd8c: fix backwards compatibility with render versions
• e7fa043: Fix access to files outside static directory
• 9aa033c: Use range of versions for dependencies
• ab70556: Fix non-email files being rendered during hot reloading
• 9c9aa5d: Add error message for when an email template does not have a default export

4.0.8

Patch Changes

• ea579b5: Log out errors that happen when export's esbuild fails

4.0.7

Patch Changes

... (truncated)

• 9208f58 chore(root): Version packages (#2228)
• 8e4afce fix(react-email): Support for users with NodeNext-style imports (#2227)
• 221ebf7 chore(root): Version packages (#2216)
• aa518a3 fix(react-email): No explicit error when running with Node <= 17 (#1923)
• dcb8164 chore(root): Version packages (#2208)
• e42c267 chore(react-email): Remove debugging log
• 45ab698 fix(react-email): "createServerParamsForMetadata is not a function" (#2206)
• 1a17219 fix(react-email): Import compiled templates with createRequire's require (#...
• 6e33167 chore(root): Version packages (#2203)
• a41a943 fix(react-email): Tests not importing @​babel/traverse the same as raw ESM (#2...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.