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.

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

Bump the build group with 4 updates #154

Merged
merged 1 commit into from
Sep 2, 2024
Merged

Bump the build group with 4 updates #154

merged 1 commit into from
Sep 2, 2024

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps the build group with 4 updates: turbo, @types/node, @bufbuild/buf and esbuild.

Updates turbo from 2.0.11 to 2.1.1

Release notes

Sourced from turbo's releases.

Turborepo v2.1.1

What's Changed

Docs

Examples

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.1.0...v2.1.1

Turborepo v2.1.1-canary.0

What's Changed

Docs

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.1.0...v2.1.1-canary.0

Turborepo v2.1.0

What's Changed

Docs

... (truncated)

Commits

Updates @types/node from 22.0.2 to 22.5.1

Commits

Updates @bufbuild/buf from 1.35.1 to 1.39.0

Release notes

Sourced from @​bufbuild/buf's releases.

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.

v1.38.0

  • Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
  • Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
  • Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
  • Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
  • Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

v1.37.0

  • Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
  • Fix plugin push failures when pushing an image built with containerd image store.

v1.36.0

  • Add --list-services and --list-methods flags to buf curl, which trigger the command to list known services or methods in the RPC schema, instead of invoking an RPC method.
  • Add clean as a top-level option in buf.gen.yaml, matching the buf generate --clean flag. If set to true, this will delete the directories, jar files, or zip files set to out for each plugin.
  • Fix git input handling of annotated tags.
  • Update buf registry login to complete the login flow in the browser by default. This allows users to login with their browser and have the token automatically provided to the CLI.
  • Add buf registry organization {create, delete, info, update} commands to manage BSR organizations. Remove buf beta registry organization commands.
  • Add buf registry module {create, delete, deprecate, info, undeprecate, update} commands to manage BSR modules. Remove buf beta registry repository commands.
  • Add buf registry label {archive, info, list, unarchive} commands to manage BSR module labels. Remove buf beta registry label commands and buf beta registry {archive, unarchive}.
  • Add buf registry commit {add-label, info, list, resolve} to manage BSR module commits. Remove buf beta registry commit commands.
Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.39.0] - 2024-08-27

  • 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.

[v1.38.0] - 2024-08-22

  • Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
  • Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
  • Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
  • Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
  • Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

[v1.37.0] - 2024-08-16

  • Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
  • Fix plugin push failures when pushing an image built with containerd image store.

[v1.36.0] - 2024-08-06

  • Add --list-services and --list-methods flags to buf curl, which trigger the command to list known services or methods in the RPC schema, instead of invoking an RPC method.
  • Add clean as a top-level option in buf.gen.yaml, matching the buf generate --clean flag. If set to true, this will delete the directories, jar files, or zip files set to out for each plugin.
  • Fix git input handling of annotated tags.
  • Update buf registry login to complete the login flow in the browser by default. This allows users to login with their browser and have the token automatically provided to the CLI.
  • Add buf registry organization {create, delete, info, update} commands to manage BSR organizations. Remove buf beta registry organization commands.
  • Add buf registry module {create, delete, deprecate, info, undeprecate, update} commands to manage BSR modules. Remove buf beta registry repository commands.
  • Add buf registry label {archive, info, list, unarchive} commands to manage BSR module labels. Remove buf beta registry label commands and buf beta registry {archive, unarchive}.
  • Add buf registry commit {add-label, info, list, resolve} to manage BSR module commits. Remove buf beta registry commit commands.
Commits

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

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

@dependabot
Bump the build group with 4 updates
deadf5f 
Bumps the build group with 4 updates: [turbo](https://github.com/vercel/turborepo), [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [@bufbuild/buf](https://github.com/bufbuild/buf) and [esbuild](https://github.com/evanw/esbuild).


Updates `turbo` from 2.0.11 to 2.1.1
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/release.md)
- [Commits](vercel/turborepo@v2.0.11...v2.1.1)

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

Updates `@bufbuild/buf` from 1.35.1 to 1.39.0
- [Release notes](https://github.com/bufbuild/buf/releases)
- [Changelog](https://github.com/bufbuild/buf/blob/main/CHANGELOG.md)
- [Commits](bufbuild/buf@v1.35.1...v1.39.0)

Updates `esbuild` from 0.23.0 to 0.23.1
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.23.0...v0.23.1)

---
updated-dependencies:
- dependency-name: turbo
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: build
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: build
- dependency-name: "@bufbuild/buf"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: build
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: build
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 1, 2024
@timostamm timostamm merged commit c97752f into main Sep 2, 2024
7 checks passed
@timostamm timostamm deleted the dependabot/npm_and_yarn/build-e1fcc892bd branch September 2, 2024 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@timostamm timostamm timostamm approved these changes

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
@timostamm