Skip to content
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.

fix(deps): update all non-major dependencies #461

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

fix(deps): update all non-major dependencies #461

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 22, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@changesets/cli (source) ^2.27.5 -> ^2.27.7 age adoption passing confidence dependencies patch
@swc/cli ^0.3.12 -> ^0.4.0 age adoption passing confidence devDependencies minor
@swc/core (source) ^1.6.3 -> ^1.6.13 age adoption passing confidence devDependencies patch
@types/better-sqlite3 (source) ^7.6.10 -> ^7.6.11 age adoption passing confidence dependencies patch
@types/node (source) ^20.14.7 -> ^20.14.10 age adoption passing confidence devDependencies patch
@vladfrangu/async_event_emitter ^2.3.0 -> ^2.4.3 age adoption passing confidence devDependencies minor
actions/setup-node v4.0.2 -> v4.0.3 age adoption passing confidence action patch
better-sqlite3 ^11.0.0 -> ^11.1.2 age adoption passing confidence dependencies minor
discord-api-types (source) ^0.37.90 -> ^0.37.92 age adoption passing confidence dependencies patch
docker/build-push-action v6.1.0 -> v6.4.0 age adoption passing confidence action minor
docker/setup-buildx-action v3.3.0 -> v3.4.0 age adoption passing confidence action minor
drizzle-kit ^0.22.7 -> ^0.23.0 age adoption passing confidence devDependencies minor
drizzle-orm (source) ^0.31.2 -> ^0.32.0 age adoption passing confidence dependencies minor
fastify (source) ^4.28.0 -> ^4.28.1 age adoption passing confidence dependencies patch
pino (source) ^9.2.0 -> ^9.3.1 age adoption passing confidence dependencies minor
pnpm (source) 9.4.0 -> 9.5.0 age adoption passing confidence packageManager minor
prometheus-middleware ^1.3.6 -> ^1.3.7 age adoption passing confidence dependencies patch
rimraf ^5.0.7 -> ^5.0.9 age adoption passing confidence devDependencies patch
turbo (source) ^2.0.4 -> ^2.0.6 age adoption passing confidence devDependencies patch

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes
swc-project/swc (@​swc/core)

v1.6.13

Compare Source

Bug Fixes
Features
Testing

v1.6.12

Compare Source

Bug Fixes
Features
Performance
Refactor

v1.6.7

Compare Source

Bug Fixes
Documentation
  • Use @swc/counter for 3rd-party download count (026ff7e)
Features
Performance
Refactor
  • (es/typescript) Extract type annotation proposal out (#​9127) (dfee5f8)
Testing
Build

v1.6.6

Compare Source

Bug Fixes
Performance

v1.6.5

Compare Source

v1.6.4

Compare Source

Features
Miscellaneous Tasks
Performance
Refactor
vladfrangu/async_event_emitter (@​vladfrangu/async_event_emitter)

v2.4.3

Compare Source

v2.4.2

Compare Source

🐛 Bug Fixes

  • Built types were wrong, causing inference issues (28e9247)

v2.4.1

Compare Source

🐛 Bug Fixes

  • Correct strictness of types and overloads for certain methods (75c7e19)

v2.4.0

Compare Source

🚀 Features

  • Cleaner types, more correct types, the usual (c1b0f75)
actions/setup-node (actions/setup-node)

v4.0.3

Compare Source

WiseLibs/better-sqlite3 (better-sqlite3)

v11.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: WiseLibs/better-sqlite3@v11.1.1...v11.1.2

v11.1.1

Compare Source

What's Changed
New Contributors

Full Changelog: WiseLibs/better-sqlite3@v11.1.0...v11.1.1

discordjs/discord-api-types (discord-api-types)

v0.37.92

Compare Source

Bug Fixes

v0.37.91

Compare Source

Features
docker/build-push-action (docker/build-push-action)

v6.4.0

Compare Source

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

v6.3.0

Compare Source

Full Changelog: docker/build-push-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

Full Changelog: docker/build-push-action@v6.1.0...v6.2.0

docker/setup-buildx-action (docker/setup-buildx-action)

v3.4.0

Compare Source

Full Changelog: docker/setup-buildx-action@v3.3.0...v3.4.0

drizzle-team/drizzle-kit-mirror (drizzle-kit)

v0.23.0

Compare Source

v0.22.8: 0.22.8

Compare Source

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

v0.32.0

Compare Source

Release notes for [email protected] and [email protected]

It's not mandatory to upgrade both packages, but if you want to use the new features in both queries and migrations, you will need to upgrade both packages

New Features

🎉 MySQL $returningId() function

MySQL itself doesn't have native support for RETURNING after using INSERT. There is only one way to do it for primary keys with autoincrement (or serial) types, where you can access insertId and affectedRows fields. We've prepared an automatic way for you to handle such cases with Drizzle and automatically receive all inserted IDs as separate objects

import { boolean, int, text, mysqlTable } from 'drizzle-orm/mysql-core';

const usersTable = mysqlTable('users', {
  id: int('id').primaryKey(),
  name: text('name').notNull(),
  verified: boolean('verified').notNull().default(false),
});

const result = await db.insert(usersTable).values([{ name: 'John' }, { name: 'John1' }]).$returningId();
//    ^? { id: number }[]

Also with Drizzle, you can specify a primary key with $default function that will generate custom primary keys at runtime. We will also return those generated keys for you in the $returningId() call

import { varchar, text, mysqlTable } from 'drizzle-orm/mysql-core';
import { createId } from '@​paralleldrive/cuid2';

const usersTableDefFn = mysqlTable('users_default_fn', {
  customId: varchar('id', { length: 256 }).primaryKey().$defaultFn(createId),
  name: text('name').notNull(),
});

const result = await db.insert(usersTableDefFn).values([{ name: 'John' }, { name: 'John1' }]).$returningId();
//  ^? { customId: string }[]

If there is no primary keys -> type will be {}[] for such queries

🎉 PostgreSQL Sequences

You can now specify sequences in Postgres within any schema you need and define all the available properties

Example
import { pgSchema, pgSequence } from "drizzle-orm/pg-core";

// No params specified
export const customSequence = pgSequence("name");

// Sequence with params
export const customSequence = pgSequence("name", {
      startWith: 100,
      maxValue: 10000,
      minValue: 100,
      cycle: true,
      cache: 10,
      increment: 2
});

// Sequence in custom schema
export const customSchema = pgSchema('custom_schema');

export const customSequence = customSchema.sequence("name");
🎉 PostgreSQL Identity Columns

Source: As mentioned, the serial type in Postgres is outdated and should be deprecated. Ideally, you should not use it. Identity columns are the recommended way to specify sequences in your schema, which is why we are introducing the identity columns feature

Example
import { pgTable, integer, text } from 'drizzle-orm/pg-core' 

export const ingredients = pgTable("ingredients", {
  id: integer("id").primaryKey().generatedAlwaysAsIdentity({ startWith: 1000 }),
  name: text("name").notNull(),
  description: text("description"),
});

You can specify all properties available for sequences in the .generatedAlwaysAsIdentity() function. Additionally, you can specify custom names for these sequences

PostgreSQL docs reference.

🎉 PostgreSQL Generated Columns

You can now specify generated columns on any column supported by PostgreSQL to use with generated columns

Example with generated column for tsvector

Note: we will add tsVector column type before latest release

import { SQL, sql } from "drizzle-orm";
import { customType, index, integer, pgTable, text } from "drizzle-orm/pg-core";

const tsVector = customType<{ data: string }>({
  dataType() {
    return "tsvector";
  },
});

export const test = pgTable(
  "test",
  {
    id: integer("id").primaryKey().generatedAlwaysAsIdentity(),
    content: text("content"),
    contentSearch: tsVector("content_search", {
      dimensions: 3,
    }).generatedAlwaysAs(
      (): SQL => sql`to_tsvector('english', ${test.content})`
    ),
  },
  (t) => ({
    idx: index("idx_content_search").using("gin", t.contentSearch),
  })
);

In case you don't need to reference any columns from your table, you can use just sql template or a string

export const users = pgTable("users", {
  id: integer("id"),
  name: text("name"),
  generatedName: text("gen_name").generatedAlwaysAs(sql`hello world!`),
  generatedName1: text("gen_name1").generatedAlwaysAs("hello world!"),
}),
🎉 MySQL Generated Columns

You can now specify generated columns on any column supported by MySQL to use with generated columns

You can specify both stored and virtual options, for more info you can check MySQL docs

Also MySQL has a few limitation for such columns usage, which is described here

Drizzle Kit will also have limitations for push command:

  1. You can't change the generated constraint expression and type using push. Drizzle-kit will ignore this change. To make it work, you would need to drop the column, push, and then add a column with a new expression. This was done due to the complex mapping from the database side, where the schema expression will be modified on the database side and, on introspection, we will get a different string. We can't be sure if you changed this expression or if it was changed and formatted by the database. As long as these are generated columns and push is mostly used for prototyping on a local database, it should be fast to drop and create generated columns. Since these columns are generated, all the data will be restored

  2. generate should have no limitations

Example
export const users = mysqlTable("users", {
  id: int("id"),
  id2: int("id2"),
  name: text("name"),
  generatedName: text("gen_name").generatedAlwaysAs(
    (): SQL => sql`${schema2.users.name} || 'hello'`,
    { mode: "stored" }
  ),
  generatedName1: text("gen_name1").generatedAlwaysAs(
    (): SQL => sql`${schema2.users.name} || 'hello'`,
    { mode: "virtual" }
  ),
}),

In case you don't need to reference any columns from your table, you can use just sql template or a string in .generatedAlwaysAs()

🎉 SQLite Generated Columns

You can now specify generated columns on any column supported by SQLite to use with generated columns

You can specify both stored and virtual options, for more info you can check SQLite docs

Also SQLite has a few limitation for such columns usage, which is described here

Drizzle Kit will also have limitations for push and generate command:

  1. You can't change the generated constraint expression with the stored type in an existing table. You would need to delete this table and create it again. This is due to SQLite limitations for such actions. We will handle this case in future releases (it will involve the creation of a new table with data migration).

  2. You can't add a stored generated expression to an existing column for the same reason as above. However, you can add a virtual expression to an existing column.

  3. You can't change a stored generated expression in an existing column for the same reason as above. However, you can change a virtual expression.

  4. You can't change the generated constraint type from virtual to stored for the same reason as above. However, you can change from stored to virtual.

New Drizzle Kit features

🎉 Migrations support for all the new orm features

PostgreSQL sequences, identity columns and generated columns for all dialects

🎉 New flag --force for drizzle-kit push

You can auto-accept all data-loss statements using the push command. It's only available in CLI parameters. Make sure you always use it if you are fine with running data-loss statements on your database

🎉 New migrations flag prefix

You can now customize migration file prefixes to make the format suitable for your migration tools:

  • index is the default type and will result in 0001_name.sql file names;
  • supabase and timestamp are equal and will result in 20240627123900_name.sql file names;
  • unix will result in unix seconds prefixes 1719481298_name.sql file names;
  • none will omit the prefix completely;
Example: Supabase migrations format
import { defineConfig } from "drizzle-kit";

export default defineConfig({
  dialect: "postgresql",
  migrations: {
    prefix: 'supabase'
  }
});

v0.31.4

Compare Source

  • Mark prisma clients package as optional - thanks @​Cherry

v0.31.3

Compare Source

Bug fixed
  • 🛠️ Fixed RQB behavior for tables with same names in different schemas
  • 🛠️ Fixed [BUG]: Mismatched type hints when using RDS Data API - #​2097
New Prisma-Drizzle extension
import { PrismaClient } from '@&#8203;prisma/client';
import { drizzle } from 'drizzle-orm/prisma/pg';
import { User } from './drizzle';

const prisma = new PrismaClient().$extends(drizzle());
const users = await prisma.$drizzle.select().from(User);

For more info, check docs: https://orm.drizzle.team/docs/prisma

fastify/fastify (fastify)

v4.28.1

Compare Source

What's Changed

Full Changelog: fastify/fastify@v4.28.0...v4.28.1

pinojs/pino (pino)

v9.3.1

Compare Source

Full Changelog: pinojs/pino@v9.3.0...v9.3.1

v9.3.0

Compare Source

pnpm/pnpm (pnpm)

v9.5.0

Compare Source

VoodooTeam/prometheus-middleware (prometheus-middleware)

v1.3.7

Compare Source

isaacs/rimraf (rimraf)

v5.0.9

Compare Source

v5.0.8

Compare Source

vercel/turbo (turbo)

v2.0.6: Turborepo v2.0.6

Compare Source

What's Changed

Examples
Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.0.5...v2.0.6

v2.0.5

Compare Source

Configuration

📅 Schedule: Branch creation - "before 6am" in timezone Asia/Jakarta, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested review from KagChi and Hazmi35 as code owners June 22, 2024 20:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ec4893 to 1a44f7f Compare June 24, 2024 10:45
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Jun 24, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from dfefe6c to b5940a8 Compare July 1, 2024 21:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 50e39e2 to 9a6703f Compare July 9, 2024 00:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 230402b to c3fe127 Compare July 9, 2024 16:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ed6ea2d to 0938464 Compare July 15, 2024 12:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0938464 to f667a13 Compare July 15, 2024 17:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@KagChi KagChi Awaiting requested review from KagChi KagChi is a code owner

@Hazmi35 Hazmi35 Awaiting requested review from Hazmi35 Hazmi35 is a code owner

Assignees
No one assigned
Labels
meta: dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants