Skip to content

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

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/all-minor-patch
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Sep 13, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@changesets/cli (source) ^3.0.1^3.0.3 age confidence devDependencies patch
@changesets/get-github-info (source) ^1.0.0^1.0.1 age confidence devDependencies patch
@swc/core (source) ^1.16.1^1.16.2 age confidence devDependencies patch
@vitest/coverage-v8 (source) ^5.0.0^5.0.1 age confidence devDependencies patch
@wolfstar/http-framework (source) ^3.2.1^3.6.0 age confidence devDependencies minor
@wolfstar/http-framework (source) ^3.4.0^3.6.0 age confidence devDependencies minor
@wolfstar/http-framework-test-utils (source) ^3.0.6^3.0.7 age confidence devDependencies patch
@wolfstar/i18next-backend (source) ^2.0.11^2.0.12 age confidence dependencies patch
@wolfstar/i18next-type-generator (source) 3.1.03.1.3 age confidence devDependencies patch
changesets/action v2.1.1v2.1.2 age confidence action patch
codecov/codecov-action v7.0.0v7.1.0 age confidence action minor v7.1.1
evlog (source) ^2.28.1^2.29.0 age confidence devDependencies minor
knip (source) 6.34.06.35.1 age confidence devDependencies minor 6.37.0 (+1)
oxfmt (source) 0.66.00.68.0 age confidence devDependencies minor
oxlint (source) 1.81.01.83.0 age confidence devDependencies minor
pnpm (source) 12.3.112.4.2 age confidence packageManager minor
pnpm/action-setup v6.0.10v6.1.0 age confidence action minor
tsdown (source) ^0.22.14^0.23.0 age confidence devDependencies minor
turbo (source) ^2.10.12^2.10.13 age confidence devDependencies patch
vitest (source) ^5.0.0^5.0.1 age confidence devDependencies patch
zizmorcore/zizmor-action v0.6.3v0.6.4 age confidence action patch

Release Notes

changesets/changesets (@​changesets/cli)

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes
changesets/changesets (@​changesets/get-github-info)

v1.0.1

Compare Source

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

v1.16.2

Compare Source

Bug Fixes
Features
  • (es/minifier) Evaluate Math.floor, Math.ceil, Math.round and Mat… (#​12117) (e876e80)

  • (es/parser) Add opt-in parser-only TSRX lowering (#​12120) (61ff097)

Miscellaneous Tasks
Refactor
Testing
Ci
vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
wolfstar-project/stars-components (@​wolfstar/http-framework)

v3.6.0

Compare Source

Minor Changes
  • #​168 b516cad - feat: align the stars dev terminal UI with Nuxt's pinned panel and folded logs

    The tsdown builder now leaves dependencies external with deps.neverBundle, removing the deprecated option and
    keeping shared dependencies external for dynamically loaded pieces. Its entry list, target and output-size table
    are suppressed; warnings and errors remain available in the log browser and log file.

    The bottom-aligned panel displays an animated Stars wordmark, aligned URLs, actual build-phase progress and elapsed
    time, then readiness timing and diagnostic counts. dev.banner accepts custom text/lines or false to hide the
    wordmark. Log, help and session-info views use the alternate screen and restore the panel when closed. Logs support
    search, source/level filters, selection, copying, and jumping to the last error with context. Stack frames are dimmed
    and no longer counted as separate errors; Node warnings are classified as warnings rather than errors.

    Rebuild state and duration now reset on Rolldown's per-build hook, including recovery from a failed build. Reduced
    motion preserves the elapsed clock, and redirected input, dumb terminals and small panes get a safe plain fallback. Thanks @​RedStar071!

Patch Changes

v3.5.0

Compare Source

Minor Changes
  • #​164 05fca34 - feat(config): configure the tsdown build from stars.config

    The tsdown block is now the project's build configuration rather than a bag of options merged into a separate
    tsdown.config.ts, and it is typed with the options a bot actually reaches for (entry, format, unbundle,
    plugins, alias, define, deps, hooks, …) instead of Record<string, unknown>. What stars.config already
    says — the entry's directory, build.outDir, build.tsconfig, the extension build.output implies — fills in the
    rest, so most projects need nothing in it at all.

    build.tsconfig is now resolved for tsdown builds too, not only tsc ones (src/tsconfig.json, else
    tsconfig.json): tsdown alone looks only next to the project root, so a bot keeping its sources' tsconfig in
    src/ — the layout the scaffold and the examples use — silently built without its paths and target.

    build.configFile on the resolved configuration reports which file the build tool is configured from
    (tsdown.config.*, package.json#tsdown, vite.config.*), or null when stars.config is the only one.

    Two options are also validated against the build tool they belong to: a non-empty tsdown block with another tool
    raises TSDOWN_OPTIONS_REQUIRE_TSDOWN, and vite likewise raises VITE_OPTIONS_REQUIRE_VITE. A project that only
    declares tsdown: {} now resolves build.tool: 'auto' to tsdown, the way depending on it already did. Thanks @​RedStar071!

  • #​164 05fca34 - feat(config): add future.compatibilityVersion, with auto imports on from 4

    future carries the defaults of the next major, the way Nuxt's own future.compatibilityVersion does: a project
    opts into them one major early, and they become the default when that major ships. Where experimental guards work
    that is still landing, everything in future is already decided.

    future: { compatibilityVersion: 4 } changes three things:

    • Auto imports are on with the tsdown build tool, and stars wires the autoImports() plugin into the build
      itself — until now the default said true but nothing injected the transform unless the project's own
      tsdown.config.ts did. At 3 they stay off unless asked for, so the promise matches what the build does.
    • tsdown is configured from stars.config alone. A tsdown.config.* (or a package.json#tsdown field) raises
      TSDOWN_CONFIG_FILE_UNSUPPORTED naming the file, rather than being silently ignored and quietly dropping the
      plugins it declares.
    • build.tool: 'auto' resolves to tsdown for any TypeScript entry, without looking for a tsdown.config.* or a
      tsdown dependency first. tsc stays available as an explicit choice.

    3 is the default and keeps today's behaviour, including loading a tsdown.config.* and merging the tsdown block
    over it. An unknown version raises INVALID_COMPATIBILITY_VERSION. Thanks @​RedStar071!

wolfstar-project/stars-components (@​wolfstar/http-framework-test-utils)

v3.0.7

Patch Changes
wolfstar-project/stars-components (@​wolfstar/i18next-backend)

v2.0.12

Patch Changes
wolfstar-project/stars-components (@​wolfstar/i18next-type-generator)

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes
  • #​163 a697108 - Enable npm provenance for published releases (publishConfig.provenance), matching every other package in this workspace. Thanks @​RedStar071!
changesets/action (changesets/action)

v2.1.2

Compare Source

Patch Changes
codecov/codecov-action (codecov/codecov-action)

v7.1.0

Compare Source

evloghq/evlog (evlog)

v2.29.0

Compare Source

What's Changed

Features 🚀
Bug Fixes 🐞
Documentation 📚
  • docs: add logger comparisons and OpenTelemetry integration guide by @​evlogai[bot] in #​680
Dependency Updates 📦

Full Changelog: https://github.com/evloghq/evlog/compare/evlog@2.28.1...evlog@2.29.0

webpro-nl/knip (knip)

v6.35.1: Release 6.35.1

Compare Source

v6.35.0: Release 6.35.0

Compare Source

oxc-project/oxc (oxfmt)

v0.68.0

Compare Source

v0.67.0

Compare Source

🛡️ Security
oxc-project/oxc (oxlint)

v1.83.0

Compare Source

v1.82.0

Compare Source

🚀 Features
  • 6a0e19c linter/eslint/no-unmodified-loop-condition: Support checkConditionalExpressions option (#​26249) (camc314)
pnpm/pnpm (pnpm)

v12.4.2

Compare Source

v12.4.1: pnpm 12.4.1

Compare Source

pnpm 12.4.1 fixes installs that failed on filesystems refusing hard links or clones, on Android, and under nodeLinker: hoisted. Repeat installs are faster.

Patch Changes

Installing packages
  • pnpm install no longer fails with Operation not permitted when the filesystem refuses a hard link or a copy-on-write clone #​14722. Under packageImportMethod: auto and clone-or-copy, pnpm copies the file instead. EdenFS checkouts, which have no hard links, and rootless containers, which refuse the clone syscall, both hit this. An explicit packageImportMethod: hardlink or clone still reports the error.

    pnpm also copies a package file whose store entry has reached the filesystem's limit on names for one file, 1024 on NTFS and 65000 on ext4. Such a file failed the install under packageImportMethod: hardlink, and under auto it stopped pnpm hard linking for the rest of the install.

  • pnpm install no longer writes a package file through a symlink left at the path it is importing to. Copying such a file overwrote whatever the link pointed at, and created that file when the link pointed nowhere. An executable package file also made the link's target executable.

  • Fixed pnpm install and pnpm dlx on Android. Registry requests crashed because pnpm found no system CA certificates, so pnpm uses bundled ones there #​14777. Imports also failed with "Permission denied" on filesystems that deny hard links and reflinks, and now fall back to copying #​14780.

  • pnpm install no longer fails with "Invalid cross-device link" while preserving a package's nested node_modules directory during a Docker build #​14758.

  • pnpm install no longer fails on a package tarball that carries a file at the archive root, such as the ._* entries macOS tar adds #​14701. The file is installed at the root of the package.

    A file: tarball packed without the usual package/ directory is now recorded under the name and version from its own package.json. It was recorded under the alias the dependency was given, at version 0.0.0.

  • Under nodeLinker: hoisted, pnpm install no longer re-imports packages that are already in place. A repeat install replaced the whole node_modules tree and reported Packages: +N. A package is still imported when its directory is missing, when its package.json no longer carries the installed version, when it is a file: dependency, and when it is patched. Lifecycle scripts no longer run again for a package left in place, and pnpm rebuild and a change to allowBuilds still reach it.

  • pnpm install now runs a dependency's build scripts again when its side-effects cache entry has no files to restore #​14717. Such builds were skipped and nothing was put in their place, so a script whose whole effect lands outside its own package directory, such as a git hook installer, never took effect. pnpm no longer publishes empty artifacts to the shared side-effects cache either.

Resolving and linking dependencies
  • pnpm install, pnpm add, and pnpm dedupe now apply ignoredOptionalDependencies #​14729. Matching optional dependencies are left out of the lockfile and are not installed. pnpm 12 installed them whenever it resolved dependencies from scratch.

  • pnpm install no longer links a transitive dependency to a workspace package when linkWorkspacePackages is true and the dependency is declared with a plain version range #​14781. Enabling preferWorkspacePackages does not change this. Set linkWorkspacePackages: deep to link them.

  • pnpm install no longer leaves dangling dependency links in workspace packages located above the workspace root #​14726.

  • pnpm install and pnpm add no longer leave a dangling symlink in node_modules when a project starts depending directly on a package that the lockfile holds only as a transitive dependency with resolved peer dependencies #​14714.

  • pnpm dedupe now keeps a compatible auto-installed peer when another workspace project depends on a newer major #​14697. Repeated runs alternated between compatible and incompatible peer versions.

  • pnpm peers check no longer reports a peer dependency declared as workspace:^, workspace:~, or a bare workspace: as unmet #​14770. pnpm reported these as unmet whatever version the linked workspace project supplied.

Performance
  • Sped up repeat installs #​14540. pnpm checks the store's files only for the packages it links into node_modules, instead of every package in the lockfile. Creating the command shims in node_modules/.bin makes about 1,500 fewer filesystem calls in a 76 project workspace. Installs that use the global virtual store read their slot paths from the cache directory instead of deriving them every time. Verifying a large lockfile also allocates less memory.

  • Sped up pnpm install in Cargo workspaces with many member crates. Repeated installs reuse verified Cargo checksum metadata.

  • Installing several packages from the same Git repository and commit now downloads the source once per install #​14725. Each package still runs its prepare scripts in its own copy of the checkout.

Running scripts and tasks
  • pnpm now passes Ctrl+C on to the script or command it started and waits for it to shut down #​14723. pnpm exited first, so a script that was still writing landed on the shell prompt.

  • pnpm run "/pattern/" --no-bail now lets every matched script finish after one of them fails #​14718. The command exits with ERR_PNPM_RUN_FAILED, and its message lists the scripts that failed in the order they were selected.

  • pnpm pipeline no longer fails on a project that tracks a symlink, such as a CLAUDE.md pointing at AGENTS.md #​14692. Changing a symlinked input's target invalidates that task's cache, and pnpm pipeline --no-cache no longer hashes task inputs.

Commands
  • pnpm add -g, pnpm update -g, and pnpm remove -g no longer change global bins or install directories after reading only part of an installed package group #​13796. If any declared package manifest is missing, malformed, or unreadable, pnpm now fails before it activates or removes anything and leaves the existing global installation intact.

  • pnpm dedupe now processes every workspace project by default, including workspaces that keep a separate lockfile per project #​14732. Workspace filters select which projects it processes, and --fail-if-no-match exits with an error when no project matches.

  • pnpm update <name>@<version> now keeps the range operator the manifest declares #​14745. Running pnpm update react@19.3.0 on "react": "^19.2.8" writes "react": "^19.3.0". A jsr: entry keeps its jsr: prefix, and a plain pnpm update now moves a jsr: range the way it moves an npm range.

  • pnpm --filter directory selectors now support ? wildcards and character classes such as [ab]. A * or ? wildcard no longer selects a directory whose name starts with a dot, as on pnpm 11.

  • pnpm deploy --legacy now prefers the dependency versions pinned in the source workspace lockfile when they still satisfy the deployed project's range #​13857.

  • pnpm sbom now leaves out a package's author field when the manifest author name is empty or contains only whitespace #​14685. In a filtered or split workspace run, only a project with no author field inherits the workspace root's author.

    pnpm sbom --sbom-format spdx now writes creationInfo.created with whole seconds, such as 2026-09-08T10:38:21Z #​14684. The fractional seconds it carried

Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 12pm on Sunday"
  • 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 requested a review from RedStar071 as a code owner September 13, 2026 01:59
@coldtea-pr-lens

coldtea-pr-lens Bot commented Sep 13, 2026

Copy link
Copy Markdown

◈ PR Lens

PR Lens could not render 57f39d9: the analysis run did not complete. Push a new commit to try again.

@wolfstarbot wolfstarbot added packages:plugin-api packages:plugin-i18next Changes in plugin-i18next packages:plugin-logger Changes in plugin-logger labels Sep 13, 2026
@socket-security

socket-security Bot commented Sep 13, 2026

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 19814b1 to ca10a4c Compare September 13, 2026 07:56
@pkg-pr-new

pkg-pr-new Bot commented Sep 13, 2026

Copy link
Copy Markdown

Open in StackBlitz

pnpm add https://pkg.pr.new/@wolfstar/plugin-api@84
pnpm add https://pkg.pr.new/@wolfstar/plugin-i18next@84
pnpm add https://pkg.pr.new/@wolfstar/plugin-logger@84
pnpm add https://pkg.pr.new/@wolfstar/plugin-subcommands-advanced@84

commit: 57f39d9

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from e86e97b to b2e6f38 Compare September 18, 2026 01:26
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from b2e6f38 to 6bbdc48 Compare September 18, 2026 15:50
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Sep 18, 2026
@renovate

renovate Bot commented Sep 19, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant