Skip to content

Bump the version-updates group across 1 directory with 20 updates #16

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.

Sign up for GitHub

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

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

Bump the version-updates group across 1 directory with 20 updates #16

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Dec 1, 2024

Bumps the version-updates group with 20 updates in the /web directory:

Package From To
@bufbuild/buf 1.28.1 1.47.2
@bufbuild/protobuf 1.5.1 2.2.2
@bufbuild/protoc-gen-es 1.5.1 2.2.2
@connectrpc/connect 0.13.2 2.0.0
@connectrpc/connect-web 0.13.2 2.0.0
@connectrpc/protoc-gen-connect-es 0.13.2 1.6.1
@react-sigma/core 3.4.2 4.0.3
@react-sigma/layout-forceatlas2 3.4.2 4.0.3
@types/node 20.5.7 22.10.1
autoprefixer 10.4.15 10.4.20
graphology-types 0.24.7 0.24.8
next 13.5.7 15.0.3
postcss 8.4.47 8.4.49
react 18.2.0 18.3.1
@types/react 18.2.21 18.3.12
react-dom 18.2.0 18.3.1
@types/react-dom 18.2.7 18.3.1
tailwindcss 3.3.3 3.4.15
typescript 5.2.2 5.7.2
@biomejs/biome 1.9.2 1.9.4

Updates @bufbuild/buf from 1.28.1 to 1.47.2

Release notes

Sourced from @​bufbuild/buf's releases.

v1.47.2

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.1

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

v1.47.0

  • Move buf registry commit to buf registry module commit. Command buf registry commit is now deprecated.
  • Move buf registry label to buf registry module label. Command buf registry label is now deprecated.

v1.46.0

  • Add buf registry whoami command, which checks if you are logged in to the Buf Schema Registry at a given domain.

v1.45.0

  • Update buf registry module info --format=json to add default_label_name, which provides the name of the default label of a module.

v1.44.0

  • Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that they satisfy the field constraints, and are only present if constraints are present.
  • Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked that they compile.
  • Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the .wasm file extension to specify a path to a Wasm plugin.

v1.43.0

  • Add new experimental LSP support under buf beta lsp.

v1.42.0

  • Add support for custom lint and breaking change plugins. See our launch blog post for more details!
  • Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
  • Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated to the formatted proto, empty message literals were not properly indented, and compound strings in options added an extra newline before trailing commas.

v1.41.0

  • Add HTTP/3 support for gRPC with buf curl.
  • Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

v1.40.1

  • Fix issue with buf lint where comment ignores in the shape of // buf:lint:ignore <RULE_ID> <extra comment> were not recognized due to the extra comment.

v1.40.0

  • Add concept of a default lint or breaking rule, which is printed out as a property when running buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint or breaking rules are explicitly configured in your buf.yaml.
  • Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced, having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT lint category are also default rules, the name has become overloaded. As with all buf changes, this change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We recommend changing to STANDARD, however.

v1.39.0

  • Fix git input handling of relative HEAD refs without branch names.
  • Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
    • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
    • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
  • Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

... (truncated)

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.47.2] - 2024-11-14

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

[v1.47.1] - 2024-11-14

  • Update the patch version to resolve NPM packaging issues. No command updates or user changes.

[v1.47.0] - 2024-11-13

  • Move buf registry commit to buf registry module commit. Command buf registry commit is now deprecated.
  • Move buf registry label to buf registry module label. Command buf registry label is now deprecated.

[v1.46.0] - 2024-10-29

  • Add buf registry whoami command, which checks if you are logged in to the Buf Schema Registry at a given domain.

[v1.45.0] - 2024-10-08

  • Update buf registry module info --format=json to add default_label_name, which provides the name of the default label of a module.

[v1.44.0] - 2024-10-03

  • Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that they satisfy the field constraints, and are only present if constraints are present.
  • Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked that they compile.
  • Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the .wasm file extension to specify a path to a Wasm plugin.

[v1.43.0] - 2024-09-30

  • Add new experimental LSP support under buf beta lsp.

[v1.42.0] - 2024-09-18

  • Add support for custom lint and breaking change plugins. See our launch blog post for more details!
  • Add buf dep graph --format flag that defaults to dot, and adds the option json, to print the dependency graph in JSON format.
  • Fix bugs in buf format where trailing comments on commas in message literals were not properly propagated to the formatted proto, empty message literals were not properly indented, and compound strings in options added an extra newline before trailing commas.

[v1.41.0] - 2024-09-11

... (truncated)

Commits

Updates @bufbuild/protobuf from 1.5.1 to 2.2.2

Release notes

Sourced from @​bufbuild/protobuf's releases.

v2.2.2

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.2.1...v2.2.2

v2.2.1

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.0...v2.2.1

v2.2.0

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.1.0...v2.2.0

v2.1.0

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.0.0...v2.1.0

v2.0.0

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";
let user = create(UserSchema, {
firstName: "Homer",
lastName: "Simpson",
active: true,
});
</tr></table>

... (truncated)

Commits

Updates @bufbuild/protoc-gen-es from 1.5.1 to 2.2.2

Release notes

Sourced from @​bufbuild/protoc-gen-es's releases.

v2.2.2

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.2.1...v2.2.2

v2.2.1

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.2.0...v2.2.1

v2.2.0

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.1.0...v2.2.0

v2.1.0

What's Changed

Full Changelog: bufbuild/protobuf-es@v2.0.0...v2.1.0

v2.0.0

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";
let user = create(UserSchema, {
firstName: "Homer",
lastName: "Simpson",
active: true,
});
</tr></table>

... (truncated)

Commits

Updates @connectrpc/connect from 0.13.2 to 2.0.0

Release notes

Sourced from @​connectrpc/connect's releases.

v2.0.0

What's Changed

  • We're upgrading to Protobuf-ES version 2. It's the largest change in this release.
  • Connect-ES no longer needs its own code generator plugin.
  • We're adding support for Next.js 15, Fastify 5, and Express 5.
  • We're dropping support for old versions of Node.js and TypeScript. You'll need at least Node.js 18.14.1 and TypeScript 4.9.6.

The upgrade of the Protobuf runtime brings support for Editions and new APIs for Protobuf messages with support for custom options. Messages are now plain TypeScript types, which greatly improves compatibility with the ecosystem. For example, messages can be passed from a server-side component in Next.js to a client-side component without losing any data or types. To learn more about the enhancements, see the release blog post for Protobuf-ES v2.

[!TIP] If you are already using Connect, see our migration guide to upgrade to version 2.

Full Changelog

Full Changelog: connectrpc/connect-es@v1.6.1...v2.0.0

v2.0.0-rc.3

What's Changed

This is a release candidate for version 2. See here for an introduction.

Full Changelog: connectrpc/connect-es@v2.0.0-rc.2...v2.0.0-rc.3

v2.0.0-rc.2

What's Changed

This is a release candidate for version 2. See here for an introduction.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by srikrsna-buf, a new releaser for @​connectrpc/connect since your current version.


Updates @connectrpc/connect-web from 0.13.2 to 2.0.0

Release notes

Sourced from @​connectrpc/connect-web's releases.

v2.0.0

What's Changed

  • We're upgrading to Protobuf-ES version 2. It's the largest change in this release.
  • Connect-ES no longer needs its own code generator plugin.
  • We're adding support for Next.js 15, Fastify 5, and Express 5.
  • We're dropping support for old versions of Node.js and TypeScript. You'll need at least Node.js 18.14.1 and TypeScript 4.9.6.

The upgrade of the Protobuf runtime brings support for Editions and new APIs for Protobuf messages with support for custom options. Messages are now plain TypeScript types, which greatly improves compatibility with the ecosystem. For example, messages can be passed from a server-side component in Next.js to a client-side component without losing any data or types. To learn more about the enhancements, see the release blog post for Protobuf-ES v2.

[!TIP] If you are already using Connect, see our migration guide to upgrade to version 2.

Full Changelog

Full Changelog: connectrpc/connect-es@v1.6.1...v2.0.0

v2.0.0-rc.3

What's Changed

This is a release candidate for version 2. See here for an introduction.

Full Changelog: connectrpc/connect-es@v2.0.0-rc.2...v2.0.0-rc.3

v2.0.0-rc.2

What's Changed

This is a release candidate for version 2. See here for an introduction.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by srikrsna-buf, a new releaser for @​connectrpc/connect-web since your current version.


Updates @connectrpc/protoc-gen-connect-es from 0.13.2 to 1.6.1

Release notes

Sourced from @​connectrpc/protoc-gen-connect-es's releases.

v1.6.1

What's Changed

Full Changelog: connectrpc/connect-es@v1.6.0...v1.6.1

v1.6.0

What's Changed

Promises are more widely adopted than ever before. We're renaming the function createPromiseClient to the more succinct createClient. For backwards compatibility, we keep the existing signature and mark it as deprecated.

After updating to this release, you can run npx @connectrpc/connect-migrate to automatically refactor your code to import and use createClient instead of createPromiseClient.

Full Changelog: connectrpc/connect-es@v1.5.0...v1.6.0

v1.5.0

What's Changed

New Contributors

Full Changelog: connectrpc/connect-es@v1.4.0...v1.5.0

v1.4.0

What's Changed

This release includes support for server-side interceptors! Here's a quick example:

import * as http from "http";
</tr></table>

... (truncated)

Commits

Updates @react-sigma/core from 3.4.2 to 4.0.3

Release notes

Sourced from @​react-sigma/core's releases.

v4.0.3

  • Upgrade to lastest beta of Sigma 3
  • Review events definition in core, and adding missing Sigma events (like the resize one)

v4.0.2

Fixes

  • 65: Sigma: could not find a suitable program for node type "circle"!

v4.0.1

Fixes

  • #64: fail to import in vite project because of lodash

v4.0.0

Features

  • Upgrade to sigma v3
  • Upgrade all project dependencies
  • Refacto project structure
  • Replace example project by a storybook
  • Replace E2E framework by playwright, and run it on the storybook
  • Using stories in website example
  • Fully graph typed API (see #58). Component & hooks take generic types for node, edge & graph attributs. Exemple for the load graph hook :
const loadGraph = useLoadGraph<{label:string, x:number, y:number}, {label:string, size:number}>();

Breaking changes

  • React-sigma doesn't depends anymore to lodash. It was use to make a deep equal on the settings provided to the SigmaContainer. Now you have to handle that :
// Sigma settings are outside the react lifecycle to avoid the change of its ref at every render
// which triggers a full render of sigma. An other way is to use the `useMemo` hook inside the component.
const sigmaSettings = {
  allowInvalidContainer: true,
};
export const Example: FC = () => {
return (
<SigmaContainer settings={sigmaSettings}>
<SampleGraph />
</SigmaContainer>
);
};

  • The sigma setting allowInvalidContainer is no more set per default. You have to pass it to the container (check above).

... (truncated)

Changelog

Sourced from @​react-sigma/core's changelog.

Version 4.0.3

  • Upgrade to lastest beta of Sigma 3
  • Review events definition in core, and adding missing Sigma events (like the resize one)

Version 4.0.2

Fixes

  • 65: Sigma: could not find a suitable program for node type "circle"!

Version 4.0.1

Fixes

  • #64: fail to import in vite project because of lodash

Version 4.0.0 (not be used !)

Features

  • Upgrade to sigma v3
  • Upgrade all project dependencies
  • Refacto project structure
  • Replace example project by a storybook
  • Replace E2E framework by playwright, and run it on the storybook
  • Using stories in website example
  • Fully graph typed API (see #58). Component & hooks take generic types for node, edge & graph attributs. Exemple for the load graph hook :
const loadGraph = useLoadGraph<{label:string, x:number, y:number}, {label:string, size:number}>();

Breaking changes

  • React-sigma doesn't depends anymore to lodash.

  • The sigma setting allowInvalidContainer is no more set per default. You have to pass it to the container (check above).

  • When you register events on edges, we don't set the correspondig settings anymore, like enableEdgeClickEvents (see #49).

Commits

Updates @react-sigma/layout-forceatlas2 from 3.4.2 to 4.0.3

Release notes

Sourced from @​react-sigma/layout-forceatlas2's releases.

v4.0.3

  • Upgrade to lastest beta of Sigma 3
  • Review events definition in core, and adding missing Sigma events (like the resize one)

v4.0.2

Fixes

  • 65: Sigma: could not find a suitable program for node type "circle"!

v4.0.1

Fixes

  • #64: fail to import in vite project because of lodash

v4.0.0

Features

  • Upgrade to sigma v3
  • Upgrade all project dependencies
  • Refacto project structure
  • Replace example project by a storybook
  • Replace E2E framework by playwright, and run it on the storybook
  • Using stories in website example
  • Fully graph typed API (see #58). Component & hooks take generic types for node, edge & graph attributs. Exemple for the load graph hook :
const loadGraph = useLoadGraph<{label:string, x:number, y:number}, {label:string, size:number}>();

Breaking changes

  • React-sigma doesn't depends anymore to lodash. It was use to make a deep equal on the settings provided to the SigmaContainer. Now you have to handle that :
// Sigma settings are outside the react lifecycle to avoid the change of its ref at every render
// which triggers a full render of sigma. An other way is to use the `useMemo` hook inside the component.
const sigmaSettings = {
  allowInvalidContainer: true,
};
export const Example: FC = () => {
return (
<SigmaContainer settings={sigmaSettings}>
<SampleGraph />
</SigmaContainer>
);
};

  • The sigma setting allowInvalidContainer is no more set per default. You have to pass it to the container (check above).

... (truncated)

Changelog

Sourced from @​react-sigma/layout-forceatlas2's changelog.

Version 4.0.3

  • Upgrade to lastest beta of Sigma 3
  • Review events definition in core, and adding missing Sigma events (like the resize one)

Version 4.0.2

Fixes

  • 65: Sigma: could not find a suitable program for node type "circle"!

Version 4.0.1

Fixes

  • #64: fail to import in vite project because of lodash

Version 4.0.0 (not be used !)

Features

  • Upgrade to sigma v3
  • Upgrade all project dependencies
  • Refacto project structure
  • Replace example project by a storybook
  • Replace E2E framework by playwright, and run it on the storybook
  • Using stories in website example
  • Fully graph typed API (see #58). Component & hooks take generic types for node, edge & graph attributs. Exemple for the load graph hook :
const loadGraph = useLoadGraph<{label:string, x:number, y:number}, {label:string, size:number}>();

Breaking changes

  • React-sigma doesn't depends anymore to lodash.

  • The sigma setting allowInvalidContainer is no more set per default. You have to pass it to the container (check above).

  • When you register events on edges, we don't set the correspondig settings anymore, like enableEdgeClickEvents (see #49).

...

Description has been truncated

@dependabot
Bump the version-updates group across 1 directory with 20 updates
9c70be4 
Bumps the version-updates group with 20 updates in the /web directory:

| Package | From | To |
| --- | --- | --- |
| [@bufbuild/buf](https://github.com/bufbuild/buf) | `1.28.1` | `1.47.2` |
| [@bufbuild/protobuf](https://github.com/bufbuild/protobuf-es/tree/HEAD/packages/protobuf) | `1.5.1` | `2.2.2` |
| [@bufbuild/protoc-gen-es](https://github.com/bufbuild/protobuf-es/tree/HEAD/packages/protoc-gen-es) | `1.5.1` | `2.2.2` |
| [@connectrpc/connect](https://github.com/connectrpc/connect-es/tree/HEAD/packages/connect) | `0.13.2` | `2.0.0` |
| [@connectrpc/connect-web](https://github.com/connectrpc/connect-es/tree/HEAD/packages/connect-web) | `0.13.2` | `2.0.0` |
| [@connectrpc/protoc-gen-connect-es](https://github.com/connectrpc/connect-es/tree/HEAD/packages/protoc-gen-connect-es) | `0.13.2` | `1.6.1` |
| [@react-sigma/core](https://github.com/sim51/react-sigma) | `3.4.2` | `4.0.3` |
| [@react-sigma/layout-forceatlas2](https://github.com/sim51/react-sigma) | `3.4.2` | `4.0.3` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.5.7` | `22.10.1` |
| [autoprefixer](https://github.com/postcss/autoprefixer) | `10.4.15` | `10.4.20` |
| [graphology-types](https://github.com/graphology/graphology) | `0.24.7` | `0.24.8` |
| [next](https://github.com/vercel/next.js) | `13.5.7` | `15.0.3` |
| [postcss](https://github.com/postcss/postcss) | `8.4.47` | `8.4.49` |
| [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `18.2.0` | `18.3.1` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `18.2.21` | `18.3.12` |
| [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `18.2.0` | `18.3.1` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `18.2.7` | `18.3.1` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss) | `3.3.3` | `3.4.15` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.2.2` | `5.7.2` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `1.9.2` | `1.9.4` |



Updates `@bufbuild/buf` from 1.28.1 to 1.47.2
- [Release notes](https://github.com/bufbuild/buf/releases)
- [Changelog](https://github.com/bufbuild/buf/blob/main/CHANGELOG.md)
- [Commits](bufbuild/buf@v1.28.1...v1.47.2)

Updates `@bufbuild/protobuf` from 1.5.1 to 2.2.2
- [Release notes](https://github.com/bufbuild/protobuf-es/releases)
- [Commits](https://github.com/bufbuild/protobuf-es/commits/v2.2.2/packages/protobuf)

Updates `@bufbuild/protoc-gen-es` from 1.5.1 to 2.2.2
- [Release notes](https://github.com/bufbuild/protobuf-es/releases)
- [Commits](https://github.com/bufbuild/protobuf-es/commits/v2.2.2/packages/protoc-gen-es)

Updates `@connectrpc/connect` from 0.13.2 to 2.0.0
- [Release notes](https://github.com/connectrpc/connect-es/releases)
- [Commits](https://github.com/connectrpc/connect-es/commits/v2.0.0/packages/connect)

Updates `@connectrpc/connect-web` from 0.13.2 to 2.0.0
- [Release notes](https://github.com/connectrpc/connect-es/releases)
- [Commits](https://github.com/connectrpc/connect-es/commits/v2.0.0/packages/connect-web)

Updates `@connectrpc/protoc-gen-connect-es` from 0.13.2 to 1.6.1
- [Release notes](https://github.com/connectrpc/connect-es/releases)
- [Commits](https://github.com/connectrpc/connect-es/commits/v1.6.1/packages/protoc-gen-connect-es)

Updates `@react-sigma/core` from 3.4.2 to 4.0.3
- [Release notes](https://github.com/sim51/react-sigma/releases)
- [Changelog](https://github.com/sim51/react-sigma/blob/main/CHANGELOG.md)
- [Commits](sim51/react-sigma@v3.4.2...v4.0.3)

Updates `@react-sigma/layout-forceatlas2` from 3.4.2 to 4.0.3
- [Release notes](https://github.com/sim51/react-sigma/releases)
- [Changelog](https://github.com/sim51/react-sigma/blob/main/CHANGELOG.md)
- [Commits](sim51/react-sigma@v3.4.2...v4.0.3)

Updates `@types/node` from 20.5.7 to 22.10.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `autoprefixer` from 10.4.15 to 10.4.20
- [Release notes](https://github.com/postcss/autoprefixer/releases)
- [Changelog](https://github.com/postcss/autoprefixer/blob/main/CHANGELOG.md)
- [Commits](postcss/autoprefixer@10.4.15...10.4.20)

Updates `graphology-types` from 0.24.7 to 0.24.8
- [Release notes](https://github.com/graphology/graphology/releases)
- [Changelog](https://github.com/graphology/graphology/blob/master/CHANGELOG.md)
- [Commits](https://github.com/graphology/graphology/commits)

Updates `next` from 13.5.7 to 15.0.3
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v13.5.7...v15.0.3)

Updates `postcss` from 8.4.47 to 8.4.49
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.4.47...8.4.49)

Updates `react` from 18.2.0 to 18.3.1
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v18.3.1/packages/react)

Updates `@types/react` from 18.2.21 to 18.3.12
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-dom` from 18.2.0 to 18.3.1
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v18.3.1/packages/react-dom)

Updates `@types/react-dom` from 18.2.7 to 18.3.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `tailwindcss` from 3.3.3 to 3.4.15
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/v3.4.15/CHANGELOG.md)
- [Commits](tailwindlabs/tailwindcss@v3.3.3...v3.4.15)

Updates `typescript` from 5.2.2 to 5.7.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.2.2...v5.7.2)

Updates `@biomejs/biome` from 1.9.2 to 1.9.4
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/cli/v1.9.4/packages/@biomejs/biome)

---
updated-dependencies:
- dependency-name: "@bufbuild/buf"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: "@bufbuild/protobuf"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@bufbuild/protoc-gen-es"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@connectrpc/connect"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@connectrpc/connect-web"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@connectrpc/protoc-gen-connect-es"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@react-sigma/core"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@react-sigma/layout-forceatlas2"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: "@types/node"
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: autoprefixer
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: version-updates
- dependency-name: graphology-types
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: version-updates
- dependency-name: next
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: version-updates
- dependency-name: postcss
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: version-updates
- dependency-name: react
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: "@types/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: react-dom
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: "@types/react-dom"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: tailwindcss
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: typescript
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: version-updates
- dependency-name: "@biomejs/biome"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: version-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant