Update all non-major dependencies #75

renovate · 2024-10-04T22:28:41Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cloudflare/vitest-pool-workers (source)	`0.5.14` -> `0.5.21`
@cloudflare/workers-types	`4.20240925.0` -> `4.20241022.0`
@dotenvx/dotenvx	`1.14.2` -> `1.20.1`
@playwright/test (source)	`1.47.2` -> `1.48.1`
@sveltejs/adapter-cloudflare (source)	`4.7.2` -> `4.7.3`
@sveltejs/kit (source)	`2.6.1` -> `2.7.2`
@sveltejs/vite-plugin-svelte (source)	`4.0.0-next.7` -> `4.0.0`
@unocss/reset	`0.63.3` -> `0.63.6`
better-sqlite3	`11.3.0` -> `11.5.0`
drizzle-kit (source)	`0.24.2` -> `0.26.2`
drizzle-orm (source)	`0.33.0` -> `0.35.3`
lucia (source)	`3.2.0` -> `3.2.2`
pnpm (source)	`9.12.0` -> `9.12.2`
sass-embedded	`1.79.4` -> `1.80.4`
svelte (source)	`5.0.0-next.262` -> `5.1.0`
svelte-check	`4.0.4` -> `4.0.5`
tslib (source)	`2.7.0` -> `2.8.0`
typescript (source)	`5.6.2` -> `5.6.3`
unocss	`0.63.3` -> `0.63.6`
vite (source)	`5.4.8` -> `5.4.10`
vitest (source)	`2.1.2` -> `2.1.3`
wrangler (source)	`3.80.0` -> `3.82.0`

Release Notes

cloudflare/workers-sdk (@cloudflare/vitest-pool-workers)

Patch Changes

Updated dependencies [a5ac45d, 586c253, b8ab809]:
- wrangler@3.81.0

`v0.5.19`

Compare Source

Patch Changes

Updated dependencies [5761020, 7859a04]:
- miniflare@3.20241011.0
- wrangler@3.80.5

`v0.5.18`

Compare Source

Patch Changes

Updated dependencies [51aedd4, c863183]:
- wrangler@3.80.4
- miniflare@3.20241004.0

`v0.5.17`

Compare Source

Patch Changes

Updated dependencies [2af75ed, eaf71b8, 2e64968, 4c6aad0]:
- wrangler@3.80.3

`v0.5.16`

Compare Source

Patch Changes

Updated dependencies [1320f20]:
- wrangler@3.80.2

`v0.5.15`

Compare Source

Patch Changes

#6835 5c50949 Thanks @emily-shen! - feature: enable asset routing in the vitest integration for Workers + static assets

Integration tests (using the SELF binding) in Workers + assets projects will now return static assets if present on that path. Previously all requests went to the user worker regardless of whether static assets would have been served in production.

Unit style tests intentionally do not return static assets.
Updated dependencies [d696850, 5c50949, dc92af2, 82180a7, 54924a4, 30b7328]:
- wrangler@3.80.1
- miniflare@3.20240925.1

cloudflare/workerd (@cloudflare/workers-types)

`v4.20241022.0`

Compare Source

`v4.20241018.0`

Compare Source

`v4.20241011.0`

Compare Source

`v4.20241004.0`

Compare Source

dotenvx/dotenvx (@dotenvx/dotenvx)

`v1.20.1`

Compare Source

Changed

update eciesjs (#421)
remove default values for ts interface - no longer permitted by latest ts (#419)

`v1.20.0`

Compare Source

see CHANGELOG

`v1.19.3`

Compare Source

Changed

🐞 fix decrypt re-encrypt of values containing backslashes (#406)

`v1.19.2`

Compare Source

Changed

forward additional signals like SIGUSR2 (#403)

`v1.19.1`

Compare Source

Changed

if SIGTERM or SIGINT sent, don't bubble wrapped process error (#402)

`v1.19.0`

Compare Source

Added

support key glob filtering for encrypt and decrypt. example: dotenvx encrypt -ek "NEXT_PUBLIC_*" (#397)

`v1.18.1`

Compare Source

Added

escape user inputted regex groupings like $1 or $2. (#396)

`v1.18.0`

Compare Source

Added

set and encrypt preserve leading spaces (#395)

     HELLO=world

Changed

improve escape and quote handling for set, encrypt, and decrypt (#395)
🐞 fix encrypt, then decrypt, then encrypt on a json value (#377)

Note: the underlying replace engine to support these changes now wraps your values in single quotes. the prior replace engine wrapped in double quotes.

So where your .env used to look like this with double quotes:

HELLO="encrypted:1234"
API_KEY="encrypted:5678"

It will now begin looking like this with single quotes:

HELLO='encrypted:1234'
API_KEY='encrypted:5678'

It's an aesthetic side effect only. Your values will continue to be decrypted and encrypted correctly.

`v1.17.0`

Compare Source

Added

add --format=eval option for get (#393)

`v1.16.1`

Compare Source

Changed

suppress stderr using options.stdio (#391)

`v1.16.0`

Compare Source

Changed

for dotenvx keypair call out to dotenvx pro keypair if pro installed (#390)

`v1.15.0`

Compare Source

Added

add --format=shell option for keypair (#389)

microsoft/playwright (@playwright/test)

`v1.48.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33023 - [Bug]: command line flag --headed has no effect in ui modehttps://github.com/microsoft/playwright/issues/331077 - [REGRESSION]: page.waitForRequest does not get resolved since 1.48.https://github.com/microsoft/playwright/issues/3308585 - [Bug]: WebSocket route does not handle full URLs in Playwrighttps://github.com/microsoft/playwright/issues/33052052 - [Regression]: Inspector not showing recorded sthttps://github.com/microsoft/playwright/issues/331323132 - [Bug]: Wrong Ubuntu release name in Dockerfile.nhttps://github.com/microsoft/playwright/pull/3299632996 - [BUG] Trace attachments have small unusable height

Browser Versions

Chromium 130.0.6723.19
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 129
Microsoft Edge 129

`v1.48.0`

Compare Source

sveltejs/kit (@sveltejs/adapter-cloudflare)

`v4.7.3`

Compare Source

Patch Changes

fix: correctly handle relative paths when fetching assets on the server (#12113)
Updated dependencies [df48fc6ede3859beabaae9fd7c6f722215bb8a42, 5780deba8e3ebd0e2b0abea029068ad0c6daf6ad, 6f9aefdb8699fc126d76a88471602cb9a80822eb, 8aa95b4b3431e79f62f580abdcdcb157b4de86cd]:
- @sveltejs/kit @2.7.0

sveltejs/kit (@sveltejs/kit)

`v2.7.2`

Compare Source

Patch Changes

fix: use absolute links in JSDoc comments (#12718)

`v2.7.1`

Compare Source

Patch Changes

chore: upgrade to sirv 3.0 (#12796)
fix: warn when form action responses are lost because SSR is off (#12063)

`v2.7.0`

Compare Source

Minor Changes

feat: update service worker when new version is detected (#12448)

Patch Changes

fix: correctly handle relative paths when fetching assets on the server (#12113)
fix: decode non ASCII anchor hashes when scrolling into view (#12699)
fix: page response missing CSP and Link headers when return promise in load (#12418)

`v2.6.4`

Compare Source

Patch Changes

fix: only preload links that have a different URL than the current page (#12773)
fix: revert change to replace version in generateBundle (#12779)
fix: catch stack trace fixing errors thrown in web containers (#12775)
fix: use absolute links in JSDoc comments (#12772)

`v2.6.3`

Compare Source

Patch Changes

fix: ensure a changing version doesn't affect the hashes for chunks without any actual code changes (#12700)
fix: prevent crash when logging URL search params in a server load function (#12763)
chore: revert update dependency cookie to ^0.7.0 (#12767)

`v2.6.2`

Compare Source

Patch Changes

chore(deps): update dependency cookie to ^0.7.0 (#12746)

sveltejs/vite-plugin-svelte (@sveltejs/vite-plugin-svelte)

`v4.0.0`

Compare Source

Major Changes

only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#901)
remove support for Svelte 4 (#892)
breaking(types): some types that have been unintentionally public are now private (#934)
disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)
replaced svelte-hmr with Svelte 5 compiler hmr integration (#892)

Minor Changes

allow infix notation for svelte modules (#901)

Previously, only suffix notation .svelte.js was allowed, now you can also use .svelte.test.js or .svelte.stories.js.
This helps when writing testcases or other auxillary code where you may want to use runes too.
feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#941)
feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#989)

Patch Changes

fix: make defaultHandler a required argument for onwarn in plugin options (#895)
prebundle with dev: true by default (#901)
fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#950)
fix: ensure svelte modules correctly run in DEV mode (#906)
ensure consistent use of compileOptions.hmr also for prebundling (#956)
fix(optimizeDeps): avoid to optimise server only entrypoints of svelte that are never used on the client (#941)
update peer on workspace packages to avoid packages bumping each other (#916)
export PluginOptions interface (#976)
Remove log about experimental status of Svelte 5. Note that breaking changes can still occur while vite-plugin-svelte 4 is in prerelease mode (#894)
fix: ensure vite config is only resolved once during lazy init of vitePreprocess (#912)
fix(vitePreprocess): default to build config so that svelte-check does not trigger dev-only plugins (#931)
fix: only apply infix filter to basename (#920)
fix: disable hmr when vite config server.hmr is false (#913)
fix(dev): make sure custom cssHash is applied consistently even for prebundled components to avoid hash mismatches during hydration (#950)
Updated dependencies [22baa25, 49324db, e9f048c, 213fedd]:
- @sveltejs/vite-plugin-svelte-inspector @3.0.0

`v4.0.0-next.8`

Compare Source

Minor Changes

feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#989)

unocss/unocss (@unocss/reset)

`v0.63.6`

Compare Source

🐞 Bug Fixes

svelte-scoped: Improve class regex for ternary expressions - by @vineryap in https://github.com/unocss/unocss/issues/4198 (c299e)

View changes on GitHub

`v0.63.5`

Compare Source

🚀 Features

inspector: Update overview page & analyzer - by @zyyv in https://github.com/unocss/unocss/issues/4214 (3d16c)
preset-wind: Default to oklch for gradients - by @rgodha24 in https://github.com/unocss/unocss/issues/4211 (1db24)

🐞 Bug Fixes

core: Don't set default value when merge content - by @zyyv in https://github.com/unocss/unocss/issues/4215 (0125f)

View changes on GitHub

`v0.63.4`

Compare Source

🐞 Bug Fixes

Temporary revert c9d2e01, fix #4189 - by @antfu in https://github.com/unocss/unocss/issues/4189 (cbf68)

View changes on GitHub

WiseLibs/better-sqlite3 (better-sqlite3)

`v11.5.0`

Compare Source

What's Changed

Added NodeJS 23 Support by @neoxpert in https://github.com/WiseLibs/better-sqlite3/pull/1283
Update SQLite to version 3.47.0 by @mceachen in https://github.com/WiseLibs/better-sqlite3/pull/1284

Full Changelog: WiseLibs/better-sqlite3@v11.4.0...v11.5.0

Update: several prebuilds failed due to a GitHub Actions network failure. Those will be retried.

`v11.4.0`

Compare Source

What's Changed

Prebuild for Electron 33 by @oliverschwendener in https://github.com/WiseLibs/better-sqlite3/pull/1279

New Contributors

@oliverschwendener made their first contribution in https://github.com/WiseLibs/better-sqlite3/pull/1279

Full Changelog: WiseLibs/better-sqlite3@v11.3.0...v11.4.0

drizzle-team/drizzle-orm (drizzle-kit)

`v0.26.2`

Compare Source

Updated internal versions for the drizzle-kit and drizzle-orm packages. Changes were introduced in the last minor release, and you are required to upgrade both packages to ensure they work as expected

`v0.26.1`

Compare Source

Fix data is malformed for views

`v0.26.0`

Compare Source

While writing this update, we found one bug that may occur with views in MySQL and SQLite, so please use the drizzle-kit@0.26.1 release

New Features

Checks support in `drizzle-kit`

You can use drizzle-kit to manage your check constraint defined in drizzle-orm schema definition

For example current drizzle table:

import { sql } from "drizzle-orm";
import { check, pgTable } from "drizzle-orm/pg-core";

export const users = pgTable(
  "users",
  (c) => ({
    id: c.uuid().defaultRandom().primaryKey(),
    username: c.text().notNull(),
    age: c.integer(),
  }),
  (table) => ({
    checkConstraint: check("age_check", sql`${table.age} > 21`),
  })
);

will be generated into

CREATE TABLE IF NOT EXISTS "users" (
  "id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
  "username" text NOT NULL,
  "age" integer,
  CONSTRAINT "age_check" CHECK ("users"."age" > 21)
);

The same is supported in all dialects

Limitations

generate will work as expected for all check constraint changes.
push will detect only check renames and will recreate the constraint. All other changes to SQL won't be detected and will be ignored.

So, if you want to change the constraint's SQL definition using only push, you would need to manually comment out the constraint, push, then put it back with the new SQL definition and push one more time.

Views support in `drizzle-kit`

You can use drizzle-kit to manage your views defined in drizzle-orm schema definition. It will work with all existing dialects and view options

PostgreSQL

For example current drizzle table:

import { sql } from "drizzle-orm";
import {
  check,
  pgMaterializedView,
  pgTable,
  pgView,
} from "drizzle-orm/pg-core";

export const users = pgTable(
  "users",
  (c) => ({
    id: c.uuid().defaultRandom().primaryKey(),
    username: c.text().notNull(),
    age: c.integer(),
  }),
  (table) => ({
    checkConstraint: check("age_check", sql`${table.age} > 21`),
  })
);

export const simpleView = pgView("simple_users_view").as((qb) =>
  qb.select().from(users)
);

export const materializedView = pgMaterializedView(
  "materialized_users_view"
).as((qb) => qb.select().from(users));

will be generated into

CREATE TABLE IF NOT EXISTS "users" (
  "id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
  "username" text NOT NULL,
  "age" integer,
  CONSTRAINT "age_check" CHECK ("users"."age" > 21)
);

CREATE VIEW "public"."simple_users_view" AS (select "id", "username", "age" from "users");

CREATE MATERIALIZED VIEW "public"."materialized_users_view" AS (select "id", "username", "age" from "users");

Views supported in all dialects, but materialized views are supported only in PostgreSQL

Limitations

generate will work as expected for all view changes
push limitations:

If you want to change the view's SQL definition using only push, you would need to manually comment out the view, push, then put it back with the new SQL definition and push one more time.

Updates for PostgreSQL enums behavior

We've updated enum behavior in Drizzle with PostgreSQL:

Add value after or before in enum: With this change, Drizzle will now respect the order of values in the enum and allow adding new values after or before a specific one.
Support for dropping a value from an enum: In this case, Drizzle will attempt to alter all columns using the enum to text, then drop the existing enum and create a new one with the updated set of values. After that, all columns previously using the enum will be altered back to the new enum.

If the deleted enum value was used by a column, this process will result in a database error.

Support for dropping an enum
Support for moving enums between schemas
Support for renaming enums

`v0.25.0`

Compare Source

Breaking changes and migrate guide for Turso users

If you are using Turso and libsql, you will need to upgrade your drizzle.config and @libsql/client package.

This version of drizzle-orm will only work with @libsql/client@0.10.0 or higher if you are using the migrate function. For other use cases, you can continue using previous versions(But the suggestion is to upgrade)
To install the latest version, use the command:

npm i @&#8203;libsql/client@latest

Previously, we had a common drizzle.config for SQLite and Turso users, which allowed a shared strategy for both dialects. Starting with this release, we are introducing the turso dialect in drizzle-kit. We will evolve and improve Turso as a separate dialect with its own migration strategies.

Before

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  dialect: "sqlite",
  schema: "./schema.ts",
  out: "./drizzle",
  dbCredentials: {
    url: "database.db",
  },
  breakpoints: true,
  verbose: true,
  strict: true,
});

After

import { defineConfig } from "drizzle-kit";

export default defineConfig({
  dialect: "turso",
  schema: "./schema.ts",
  out: "./drizzle",
  dbCredentials: {
    url: "database.db",
  },
  breakpoints: true,
  verbose: true,
  strict: true,
});

If you are using only SQLite, you can use dialect: "sqlite"

LibSQL/Turso and Sqlite migration updates

SQLite "generate" and "push" statements updates

Starting from this release, we will no longer generate comments like this:

      '/*\n SQLite does not support "Changing existing column type" out of the box, we do not generate automatic migration for that, so it has to be done manually'
      + '\n Please refer to: https://www.techonthenet.com/sqlite/tables/alter_table.php'
      + '\n                  https://www.sqlite.org/lang_altertable.html'
      + '\n                  https://stackoverflow.com/questions/2083543/modify-a-columns-type-in-sqlite3'
      + "\n\n Due to that we don't generate migration automatically and it has to be done manually"
      + '\n*/'

We will generate a set of statements, and you can decide if it's appropriate to create data-moving statements instead. Here is an example of the SQL file you'll receive now:

PRAGMA foreign_keys=OFF;
--> statement-breakpoint
CREATE TABLE `__new_worker` (
  `id` integer PRIMARY KEY NOT NULL,
  `name` text NOT NULL,
  `salary` text NOT NULL,
  `job_id` integer,
  FOREIGN KEY (`job_id`) REFERENCES `job`(`id`) ON UPDATE no action ON DELETE no action
);
--> statement-breakpoint
INSERT INTO `__new_worker`("id", "name", "salary", "job_id") SELECT "id", "name", "salary", "job_id" FROM `worker`;
--> statement-breakpoint
DROP TABLE `worker`;
--> statement-breakpoint
ALTER TABLE `__new_worker` RENAME TO `worker`;
--> statement-breakpoint
PRAGMA foreign_keys=ON;

LibSQL/Turso "generate" and "push" statements updates

Since LibSQL supports more ALTER statements than SQLite, we can generate more statements without recreating your schema and moving all the data, which can be potentially dangerous for production environments.

LibSQL and Turso will now have a separate dialect in the Drizzle config file, meaning that we will evolve Turso and LibSQL independently from SQLite and will aim to support as many features as Turso/LibSQL offer.

With the updated LibSQL migration strategy, you will have the ability to:

Change Data Type: Set a new data type for existing columns.
Set and Drop Default Values: Add or remove default values for existing columns.
Set and Drop NOT NULL: Add or remove the NOT NULL constraint on existing columns.
Add References to Existing Columns: Add foreign key references to existing columns

You can find more information in the LibSQL documentation

LIMITATIONS

Dropping foreign key will cause table recreation.

This is because LibSQL/Turso does not support dropping this type of foreign key.

CREATE TABLE `users` (
  `id` integer NOT NULL,
  `name` integer,
  `age` integer PRIMARY KEY NOT NULL
  FOREIGN KEY (`name`) REFERENCES `users1`("id") ON UPDATE no action ON DELETE no action
);

If the table has indexes, altering columns will cause index recreation:
Drizzle-Kit will drop the indexes, modify the columns, and then create the indexes.
Adding or dropping composite foreign keys is not supported and will cause table recreation.
Primary key columns can not be altered and will cause table recreation.
Altering columns that are part of foreign key will cause table recreation.

NOTES

You can create a reference on any column type, but if you want to insert values, the referenced column must have a unique index or primary key.

CREATE TABLE parent(a PRIMARY KEY, b UNIQUE, c, d, e, f);
CREATE UNIQUE INDEX i1 ON parent(c, d);
CREATE INDEX i2 ON parent(e);
CREATE UNIQUE INDEX i3 ON parent(f COLLATE nocase);

CREATE TABLE child1(f, g REFERENCES parent(a));                        -- Ok
CREATE TABLE child2(h, i REFERENCES parent(b));                        -- Ok
CREATE TABLE child3(j, k, FOREIGN KEY(j, k) REFERENCES parent(c, d));  -- Ok
CREATE TABLE child4(l, m REFERENCES parent(e));                        -- Error!
CREATE TABLE child5(n, o REFERENCES parent(f));                        -- Error!
CREATE TABLE child6(p, q, FOREIGN KEY(p, q) REFERENCES parent(b, c));  -- Error!
CREATE TABLE child7(r REFERENCES parent(c));                           -- Error!

NOTE: The foreign key for the table child5 is an error because, although the parent key column has a unique index, the index uses a different collating sequence.

See more: https://www.sqlite.org/foreignkeys.html

New `casing` param in `drizzle-orm` and `drizzle-kit`

There are more improvements you can make to your schema definition. The most common way to name your variables in a database and in TypeScript code is usually snake_case in the da

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.

👻 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 bot temporarily deployed to dev October 4, 2024 22:28 Inactive

renovate bot changed the title ~~Update devDependency @cloudflare/workers-types to v4.20241004.0~~ Update all non-major dependencies Oct 6, 2024

renovate bot force-pushed the renovate/all-minor-patch branch from 9f5bc93 to 436e7a4 Compare October 6, 2024 04:06

renovate bot temporarily deployed to dev October 6, 2024 04:06 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 436e7a4 to 7592f8c Compare October 6, 2024 07:37

renovate bot temporarily deployed to dev October 6, 2024 07:37 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 7592f8c to e68009e Compare October 7, 2024 13:44

renovate bot temporarily deployed to dev October 7, 2024 13:44 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from e68009e to 174b004 Compare October 7, 2024 17:01

renovate bot temporarily deployed to dev October 7, 2024 17:01 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 174b004 to a0504e0 Compare October 7, 2024 19:03

renovate bot temporarily deployed to dev October 7, 2024 19:03 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from a0504e0 to 7d028bc Compare October 7, 2024 21:30

renovate bot temporarily deployed to dev October 7, 2024 21:30 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 7d028bc to a71cc04 Compare October 8, 2024 10:08

renovate bot had a problem deploying to dev October 8, 2024 10:08 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from a71cc04 to 9ea404b Compare October 8, 2024 14:13

renovate bot temporarily deployed to dev October 8, 2024 14:13 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 9ea404b to 67528b7 Compare October 8, 2024 19:53

renovate bot temporarily deployed to dev October 8, 2024 19:53 Inactive

renovate bot temporarily deployed to dev October 21, 2024 10:21 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 2ddb8a8 to 5ec0262 Compare October 21, 2024 18:55

renovate bot temporarily deployed to dev October 21, 2024 18:55 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 5ec0262 to 355cea7 Compare October 21, 2024 21:40

renovate bot temporarily deployed to dev October 21, 2024 21:40 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 355cea7 to 5488dfb Compare October 22, 2024 03:49

renovate bot temporarily deployed to dev October 22, 2024 03:49 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from 5488dfb to ac6ad7c Compare October 22, 2024 11:11

renovate bot temporarily deployed to dev October 22, 2024 11:11 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from ac6ad7c to 2bd3f91 Compare October 22, 2024 21:28

renovate bot had a problem deploying to dev October 22, 2024 21:28 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 2bd3f91 to ec65f77 Compare October 23, 2024 05:14

renovate bot temporarily deployed to dev October 23, 2024 05:14 Inactive

renovate bot force-pushed the renovate/all-minor-patch branch from ec65f77 to b3bff0a Compare October 23, 2024 16:19

renovate bot had a problem deploying to dev October 23, 2024 16:19 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from b3bff0a to 16dce95 Compare October 23, 2024 19:44

renovate bot temporarily deployed to dev October 23, 2024 19:44 Inactive

Update all non-major dependencies

b7221ac

renovate bot force-pushed the renovate/all-minor-patch branch from 16dce95 to b7221ac Compare October 24, 2024 02:20

renovate bot temporarily deployed to dev October 24, 2024 02:20 Inactive

renovate bot deployed to dev October 24, 2024 02:20 Active

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update all non-major dependencies #75

Update all non-major dependencies #75

renovate bot commented Oct 4, 2024 •

edited

Loading

Update all non-major dependencies #75

Are you sure you want to change the base?

Update all non-major dependencies #75

Conversation

renovate bot commented Oct 4, 2024 • edited Loading

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Changed

Changed

Changed

Changed

Added

Added

Added

Changed

Added

Changed

Changed

Added

Highlights

Browser Versions

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Minor Changes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

What's Changed

What's Changed

New Contributors

New Features

Checks support in drizzle-kit

Limitations

Views support in drizzle-kit

PostgreSQL

Limitations

Updates for PostgreSQL enums behavior

Breaking changes and migrate guide for Turso users

LibSQL/Turso and Sqlite migration updates

SQLite "generate" and "push" statements updates

LibSQL/Turso "generate" and "push" statements updates

LIMITATIONS

NOTES

New casing param in drizzle-orm and drizzle-kit

Configuration

renovate bot commented Oct 4, 2024 •

edited

Loading

Checks support in `drizzle-kit`

Views support in `drizzle-kit`

New `casing` param in `drizzle-orm` and `drizzle-kit`