Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@aptre/common ^0.18.0 -> ^0.20.0 age adoption passing confidence devDependencies minor
@aptre/protobuf-es-lite 0.4.7 -> 0.4.8 age adoption passing confidence resolutions patch
@aptre/protobuf-es-lite 0.4.7 -> 0.4.8 age adoption passing confidence dependencies patch
@types/node (source) ^20.11.5 -> ^22.0.0 age adoption passing confidence devDependencies major
actions/checkout v4.2.0 -> v4.2.2 age adoption passing confidence action patch
actions/dependency-review-action v4.3.4 -> v4.5.0 age adoption passing confidence action minor
actions/setup-go v5.0.2 -> v5.2.0 age adoption passing confidence action minor
actions/setup-node v4.0.4 -> v4.1.0 age adoption passing confidence action minor
esbuild 0.24.0 -> 0.24.2 age adoption passing confidence devDependencies patch
github.com/aperturerobotics/common v0.18.7 -> v0.20.3 age adoption passing confidence require minor
github.com/aperturerobotics/protobuf-go-lite v0.7.0 -> v0.8.0 age adoption passing confidence require minor
github.com/urfave/cli/v2 v2.27.4 -> v2.27.5 age adoption passing confidence require patch
github/codeql-action v3.26.10 -> v3.28.0 age adoption passing confidence action minor
go (source) 1.23.2 -> 1.23.4 age adoption passing confidence toolchain patch
golang.org/x/tools v0.25.0 -> v0.28.0 age adoption passing confidence require minor
graphql 16.9.0 -> 16.10.0 age adoption passing confidence dependencies minor
typescript (source) 5.6.2 -> 5.7.2 age adoption passing confidence devDependencies minor
vitest (source) 2.1.2 -> 2.1.8 age adoption passing confidence devDependencies patch

Release Notes

aperturerobotics/common (@​aptre/common)

v0.20.3

Compare Source

v0.20.2

Compare Source

v0.20.1

Compare Source

v0.20.0

Compare Source

v0.19.1

Compare Source

v0.18.8

Compare Source

aperturerobotics/protobuf-es-lite (@​aptre/protobuf-es-lite)

v0.4.8

Compare Source

actions/checkout (actions/checkout)

v4.2.2

Compare Source

v4.2.1

Compare Source

actions/dependency-review-action (actions/dependency-review-action)

v4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/dependency-review-action@v4...v4.5.0

v4.4.0

Compare Source

What's Changed

Full Changelog: actions/dependency-review-action@v4.3.5...v4.4.0

v4.3.5

Compare Source

What's Changed

New Contributors

Full Changelog: actions/dependency-review-action@v4.3.4...v4.3.5

actions/setup-go (actions/setup-go)

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-go@v5...v5.2.0

v5.1.0

Compare Source

What's Changed

Bug Fixes

New Contributors

Full Changelog: actions/setup-go@v5...v5.1.0

actions/setup-node (actions/setup-node)

v4.1.0

Compare Source

evanw/esbuild (esbuild)

v0.24.2

Compare Source

  • Fix regression with --define and import.meta (#​4010, #​4012, #​4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

v0.24.1

Compare Source

  • Allow es2024 as a target in tsconfig.json (#​4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
      "compilerOptions": {
        "target": "ES2024"
      }
    }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
      get
      *x() {}
      set
      *y() {}
    }

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#​4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    // The following code now transforms to "return true;\n"
    console.log(esbuild.transformSync(
      `return process.env['SOME-TEST-VAR']`,
      { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
    ))

    Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

  • Minify empty try/catch/finally blocks (#​4003)

    With this release, esbuild will now attempt to minify empty try blocks:

    // Original code
    try {} catch { foo() } finally { bar() }
    
    // Old output (with --minify)
    try{}catch{foo()}finally{bar()}
    
    // New output (with --minify)
    bar();

    This can sometimes expose additional minification opportunities.

  • Include entryPoint metadata for the copy loader (#​3985)

    Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

  • Source mappings may now contain null entries (#​3310, #​3878)

    With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

    This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

  • Avoid using the parent directory name for determinism (#​3998)

    To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

    This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

  • Experimental support for esbuild on NetBSD (#​3974)

    With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

aperturerobotics/protobuf-go-lite (github.com/aperturerobotics/protobuf-go-lite)

v0.8.0

Compare Source

urfave/cli (github.com/urfave/cli/v2)

v2.27.5

Compare Source

What's Changed

Full Changelog: urfave/cli@v2.27.4...v2.27.5

github/codeql-action (github/codeql-action)

v3.28.0

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.28.0 - 20 Dec 2024
  • Bump the minimum CodeQL bundle version to 2.15.5. #​2655
  • Don't fail in the unusual case that a file is on the search path. #​2660.

See the full CHANGELOG.md for more information.

v3.27.9

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.9 - 12 Dec 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.8

Compare Source

v3.27.7

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.7 - 10 Dec 2024
  • We are rolling out a change in December 2024 that will extract the CodeQL bundle directly to the toolcache to improve performance. #​2631
  • Update default CodeQL bundle version to 2.20.0. #​2636

See the full CHANGELOG.md for more information.

v3.27.6

Compare Source

v3.27.5

Compare Source

v3.27.4

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.4 - 14 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.3

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.3 - 12 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.2

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.2 - 12 Nov 2024
  • Fixed an issue where setting up the CodeQL tools would sometimes fail with the message "Invalid value 'undefined' for header 'authorization'". #​2590

See the full CHANGELOG.md for more information.

v3.27.1

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.1 - 08 Nov 2024
  • The CodeQL Action now downloads bundles compressed using Zstandard on GitHub Enterprise Server when using Linux or macOS runners. This speeds up the installation of the CodeQL tools. This feature is already available to GitHub.com users. #​2573
  • Update default CodeQL bundle version to 2.19.3. #​2576

See the full CHANGELOG.md for more information.

v3.27.0

Compare Source

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

3.27.0 - 22 Oct 2024
  • Bump the minimum CodeQL bundle version to 2.14.6. #​2549
  • Fix an issue where the upload-sarif Action would fail with "upload-sarif post-action step failed: Input required and not supplied: token" when called in a composite Action that had a different set of inputs to the ones expected by the upload-sarif Action. #​2557
  • Update default CodeQL bundle version to 2.19.2. #​2552

See the full CHANGELOG.md for more information.

v3.26.13

Compare Source

v3.26.12

Compare Source

v3.26.11

Compare Source

golang/go (go)

v1.23.4

v1.23.3

graphql/graphql-js (graphql)

v16.10.0: 16.10.0

Compare Source

v16.10.0 (2024-12-15)

New Feature 🚀
Bug Fix 🐞
Docs 📝
10 PRs were merged
Internal 🏠
4 PRs were merged
Committers: 5
microsoft/TypeScript (typescript)

v5.7.2

Compare Source

v5.6.3

Compare Source

vitest-dev/vitest (vitest)

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

  • Support VIte 6
    View changes on GitHub

v2.1.5

Compare Source

   🚀 Features
   🐞 Bug Fixes

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 renovate bot changed the title chore(deps): update dependency typescript to v5.5.2 chore(deps): update all dependencies Jun 20, 2024
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 3916b39 to e5dd6a8 Compare June 26, 2024 02:16
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 2c66dae to 4b56240 Compare July 4, 2024 03:17
@renovate renovate bot force-pushed the renovate/all branch 12 times, most recently from 14029a0 to 0db8246 Compare July 12, 2024 11:00
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 3f7bab6 to fe04d20 Compare July 19, 2024 16:32
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 8e4cd39 to 266195f Compare July 22, 2024 12:00
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 465b078 to cfa1890 Compare December 3, 2024 13:40
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 92cc529 to c934980 Compare December 5, 2024 01:02
@renovate renovate bot changed the title chore(deps): update all dependencies fix(deps): update all dependencies Dec 10, 2024
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from e37a89d to bf3b461 Compare December 15, 2024 12:17
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from a0cc24f to 24e7d06 Compare December 23, 2024 10:57
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 279d57b to 5dabc75 Compare January 2, 2025 01:31
Copy link
Contributor Author

renovate bot commented Jan 2, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 5 additional dependencies were updated

Details:

Package Change
github.com/aperturerobotics/json-iterator-lite v1.0.0 -> v1.0.1-0.20240713111131-be6bf89c3008
github.com/cpuguy83/go-md2man/v2 v2.0.4 -> v2.0.5
golang.org/x/mod v0.21.0 -> v0.22.0
golang.org/x/sync v0.8.0 -> v0.10.0
golang.org/x/sys v0.25.0 -> v0.28.0

@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from e57b596 to 2925f86 Compare January 2, 2025 02:17
@paralin paralin merged commit 6896448 into master Jan 2, 2025
5 checks passed
@paralin paralin deleted the renovate/all branch January 2, 2025 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant