Skip to content

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

Merged
northword merged 1 commit intomainfrom
renovate/all-minor-patch
Aug 1, 2025
Merged

fix(deps): update all non-major dependencies#129
northword merged 1 commit intomainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Aug 1, 2025

This PR contains the following updates:

Package Change Age Confidence
@antfu/eslint-config ^4.16.1 -> ^4.19.0 age confidence
@shikijs/vitepress-twoslash (source) ^3.7.0 -> ^3.9.0 age confidence
@swc/core (source) ^1.12.9 -> ^1.13.3 age confidence
@types/node (source) ^22.15.34 -> ^22.17.0 age confidence
bumpp ^10.2.0 -> ^10.2.1 age confidence
c12 ^3.0.4 -> ^3.2.0 age confidence
changelogen ^0.6.1 -> ^0.6.2 age confidence
es-toolkit (source) ^1.39.5 -> ^1.39.8 age confidence
esbuild ^0.25.5 -> ^0.25.8 age confidence
eslint (source) ^9.30.0 -> ^9.32.0 age confidence
pnpm (source) 10.12.4 -> 10.14.0 age confidence
typescript (source) ^5.8.3 -> ^5.9.2 age confidence
unbuild ^3.5.0 -> ^3.6.0 age confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v4.19.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.18.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.17.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.16.2

Compare Source

No significant changes

    View changes on GitHub
shikijs/shiki (@​shikijs/vitepress-twoslash)

v3.9.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.8.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.8.0

Compare Source

   🚀 Features
    View changes on GitHub
swc-project/swc (@​swc/core)

v1.13.3

Compare Source

Bug Fixes
Performance

v1.13.2

Compare Source

Bug Fixes
Features
Miscellaneous Tasks
  • (claude) Use Opus and allow assigning to the claude-bot (3275b9c)
Performance
Refactor
Testing

v1.13.1

Compare Source

Bug Fixes
Testing

v1.13.0

Compare Source

Bug Fixes
Features
Performance
Refactor

v1.12.14

Compare Source

Bug Fixes
Features

  • (es/parser) Enable support for dynamic import with defer phase (#​10845) (097d29d)

  • (plugin) Remove bytecheck to make Wasm plugins backward compatible (#​10842) (30ad808)

Miscellaneous Tasks
Performance
Refactor
Testing

v1.12.11

Compare Source

Bug Fixes
Features
Miscellaneous Tasks
Performance
Refactor
Testing
Pref
antfu-collective/bumpp (bumpp)

v10.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
unjs/c12 (c12)

v3.2.0

Compare Source

compare changes

🚀 Enhancements
  • Support scoped env files (#​256)
  • Support context for function config (#​258)
  • Support configFileRequired (#​241)
🏡 Chore
✅ Tests
❤️ Contributors

v3.1.0

Compare Source

compare changes

🚀 Enhancements
  • Pass raw configs to function sources (#​253)
📖 Documentation
🏡 Chore
❤️ Contributors
unjs/changelogen (changelogen)

v0.6.2

Compare Source

compare changes

🩹 Fixes
  • cli: Accept hideAuthorEmail arg (#​275)
📖 Documentation
  • Add note about version number interpretation (#​272)
🌊 Types
  • config.types accept boolean value (#​278)
🏡 Chore
❤️ Contributors
toss/es-toolkit (es-toolkit)

v1.39.8

Compare Source

Released on July 25th, 2025.

  • Aligned the types of fill, pullAll, pullAllBy, pullAllWith, pullAt, remove, and reverse in our compatibility library with the latest Lodash types (@types/lodash v4.17.20).

v1.39.7

Compare Source

Released on July 9th, 2025.

  • Fixed a compatibility issue with Lodash's debounce and throttle functions.
  • Remove useless source map for reduce bundle size.
  • Fix some of the documentation issues.

We sincerely thank @​dayongkr, @​cobocho, @​raon0211, and @​D-Sketon for their contributions. We appreciate your great efforts!

v1.39.6

Compare Source

Released on July 2th, 2025.

  • Fixed handling of null/undefined values in values function.
  • Fixed type safety in compat/get by adding GetFieldType utility type.

We sincerely thank @​raon0211, @​dayongkr, @​yhb-flydream, @​ssi02014, @​JeongHwan-dev, and @​guesung for their contributions. We appreciate your great efforts!

evanw/esbuild (esbuild)

v0.25.8

Compare Source

  • Fix another TypeScript parsing edge case (#​4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}

  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

Compare Source

  • Parse and print JavaScript imports with an explicit phase (#​4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
const bar = await import.source("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

    This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

  • Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

    This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

    Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

  • Fix a TypeScript parsing edge case (#​4241)

    This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

    x = a ? (b) : c => d;
y = a ? (b) : c => d : e;

    The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

  • Inline small constant strings when minifying

    Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

    // Original code
const foo = 'foo'
console.log({ [foo]: true })

// Old output (with --minify --bundle --format=esm)
var o="foo";console.log({[o]:!0});

// New output (with --minify --bundle --format=esm)
console.log({foo:!0});

    Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

v0.25.6

Compare Source

  • Fix a memory leak when cancel() is used on a build context (#​4231)

    Calling rebuild() followed by cancel() in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.

  • Support empty :is() and :where() syntax in CSS (#​4232)

    Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.

  • Improve tree-shaking of try statements in dead code (#​4224)

    With this release, esbuild will now remove certain try statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:

    // Original code
return 'foo'
try { return 'bar' } catch {}

// Old output (with --minify)
return"foo";try{return"bar"}catch{}

// New output (with --minify)
return"foo";

  • Consider negated bigints to have no side effects

    While esbuild currently considers 1, -1, and 1n to all have no side effects, it didn't previously consider -1n to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:

    // Original code
let a = 1, b = -1, c = 1n, d = -1n

// Old output (with --bundle --minify)
(()=>{var n=-1n;})();

// New output (with --bundle --minify)
(()=>{})();

  • Support a configurable delay in watch mode before rebuilding (#​3476, #​4178)

    The watch() API now takes a delay option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the --watch-delay= flag.

    This should also help avoid confusion about the watch() API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the watch() API has an option.

  • Allow mixed array for entryPoints API option (#​4223)

    The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the entryPoints API option, such as ['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.

  • Update Go from 1.23.8 to 1.23.10 (#​4204, #​4207)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4673 and CVE-2025-22874) from vulnerability scanners that only detect

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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 added the dependencies label Aug 1, 2025
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Aug 1, 2025 

npm i https://pkg.pr.new/zotero-plugin-scaffold@129

commit: 558fac4

@northword northword merged commit c3d3675 into main Aug 1, 2025
7 checks passed
@northword northword deleted the renovate/all-minor-patch branch August 1, 2025 00:39
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Dec 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@northword