Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

fix(deps): update all non-major dependencies#1557
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Mar 28, 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
@aptos-labs/ts-sdk (source) 7.2.07.3.0 age confidence pnpm-workspace.overrides minor
@aptos-labs/ts-sdk (source) 7.2.07.3.0 age confidence dependencies minor
@biomejs/biome (source) 2.5.72.5.8 age confidence devDependencies patch
@tanstack/react-router (source) 1.170.231.170.28 age confidence dependencies patch
@tanstack/react-start (source) 1.168.401.168.45 age confidence dependencies patch
@tanstack/router-cli (source) 1.167.251.167.29 age confidence devDependencies patch
@tanstack/router-plugin (source) 1.168.271.168.31 age confidence devDependencies patch
esbuild 0.28.10.28.2 age confidence pnpm-workspace.overrides patch
js-yaml 5.2.35.3.0 age confidence pnpm-workspace.overrides minor
node (source) 24.14.124.19.0 age confidence minor
pnpm (source) 11.20.011.21.0 age confidence packageManager minor
pnpm (source) 11.20.011.21.0 age confidence minor
rollup-plugin-visualizer 7.0.17.1.1 age confidence devDependencies minor

Release Notes

aptos-labs/aptos-ts-sdk (@​aptos-labs/ts-sdk)

v7.3.0

Fixed

  • CI stability: Fixed three intermittent CI failures affecting Dependabot PRs and test runs:
    1. safe-chain blocking transitive deps — Added baseline-browser-mapping and caniuse-lite to SAFE_CHAIN_MINIMUM_PACKAGE_AGE_EXCLUSIONS in setup-node-pnpm action. These packages are republished frequently by browserslist and were causing ~36% Confidential Asset test failure rate when Dependabot refreshed lockfiles.
    2. Codecov upload failures on Dependabot — Added conditional skip logic to codecov-action and bundle-analyzer when CODECOV_TOKEN is unavailable (expected on Dependabot and fork PRs where repo secrets are not accessible). This eliminated spurious 33% Codecov failure rate while preserving uploads on main branch and authenticated PRs.
    3. Missing testnet log file masking real errors — Made cat of local testnet logs graceful (2>/dev/null || echo) across all test actions so that missing logs don't fail the failure-handling step. This was hiding the actual safe-chain/Codecov errors behind spurious cat: no such file exit codes.

Added

  • generateTransactionPayload TypeScript overload for InputMultiSigScriptData (returns TransactionPayloadMultiSig), plus unit coverage for multisig script payloads. Localnet e2e for create/execute is skipped for now: indexing MultisigTransactionPayload::Script panics the current CLI indexer processor and takes down the shared localnet.
  • Automated release tooling: scripts/prepareRelease.mjs bumps a package's version and stamps its changelog, a two-phase release skill/Cursor rule (.claude/skills/release-ts-sdk/, .cursor/rules/release-ts-sdk.mdc) drives the version-bump PR and the tag + GitHub Release, and .github/workflows/publish.yaml publishes @aptos-labs/ts-sdk and @aptos-labs/confidential-asset to NPM with provenance via OIDC trusted publishing when a GitHub Release is published. See CONTRIBUTING.md and docs/superpowers/specs/2026-07-06-automated-ts-sdk-releases-design.md.
  • Retry reads of pruned history against the archival endpoint the node advertises in its 410 Gone response, so historical Node API reads keep working as fullnodes move to a rolling history window. Enabled by default; opt out with new AptosConfig({ ..., archivalFallback: false }). Credentials are only forwarded to the archival endpoint when it is on the same site as the configured node.

Changed

  • Upgrade to TypeScript 7.0 (tsc 7.0.2). The root package keeps the TypeScript 6.0 programmatic API via @typescript/typescript6 (aliased as typescript) for tools such as TypeDoc that still require it, and installs the native TypeScript 7 compiler as @typescript/native so tsc / pnpm build use 7.0. Examples and other packages that only invoke the CLI depend on typescript@^7.0.2 directly. Align tsconfig.json rootDir with the confidential-asset package (. for editor/typecheck of src + tests; ./src only in tsconfig.build.json) so full-project tsc --noEmit succeeds under TypeScript 6/7.

  • Adapt localnet e2e coverage to recent Aptos framework changes: skip the permissioned-delegation e2e (feature removed in aptos-core#20198), assert fungible-asset creator metadata by asset type rather than indexer row order, retarget table e2e tests away from the empty AptosCoin CoinInfo supply aggregator toward the genesis TypeInfo→FA metadata table, and pin account-abstraction example Move deps to mainnet so SmartTable compiles against current CLI.

  • Raise unit test line coverage threshold from 90% to 95% (vitest.config.ts) and add mocked-client unit tests across API wrappers, keyless/federated JWKS flows, MultiKeyAccount, transaction submission helpers, client aptosRequest error paths, type guards, and encrypted-payload claim handling. Tests assert forwarded arguments, parsed results, and error types/messages rather than smoke-only execution.

  • Add offline/mocked-client unit tests raising coverage of previously-untested modules: internal/faucet.ts (fundAccount), client/get.ts pagination helpers (getAptosFullNode, getAptosPepperService, paginateWithCursor, paginateWithObfuscatedCursor, getPageWithObfuscatedCursor), core/crypto/abstraction.ts (AbstractPublicKey/AbstractSignature), account/AbstractedAccount.ts, account/keylessSigner.ts (isKeylessSigner), api/account/abstraction.ts (AccountAbstraction), api/transactionSubmission/sign.ts (Sign), api/utils.ts (waitForIndexerOnVersion), and SimpleTransaction BCS round trips in transactions/instances.

biomejs/biome (@​biomejs/biome)

v2.5.8

Compare Source

Patch Changes
TanStack/router (@​tanstack/react-router)

v1.170.28

Compare Source

Patch Changes
  • #​8055 0c25a7b - Avoid wrapping root components that may render the HTML document in a Suspense boundary during SSR and hydration.

  • #​8054 31882c7 - Reuse resolved lazy route components when revisiting code-split routes, preventing unnecessary pending UI.

  • Updated dependencies [31882c7]:

v1.170.27

Compare Source

Patch Changes

v1.170.26

Compare Source

Patch Changes
  • #​8045 f500760 - Warn when an Outlet is rendered inside a pending, error, or not-found component.

  • #​8043 1aafca9 - remove the undocumented Link isTransitioning state and data-transitioning attribute

  • #​8044 aa10b65 - Apply preloadDelay to viewport link preloading and cancel pending preloads when links leave the viewport.

  • Updated dependencies [7e93431]:

v1.170.25

Compare Source

Patch Changes

v1.170.24

Compare Source

Patch Changes
TanStack/router (@​tanstack/react-start)

v1.168.45

Compare Source

Patch Changes

v1.168.44

Compare Source

Patch Changes

v1.168.43

Compare Source

Patch Changes

v1.168.42

Compare Source

Patch Changes

v1.168.41

Compare Source

Patch Changes
TanStack/router (@​tanstack/router-cli)

v1.167.29

Compare Source

Patch Changes

v1.167.28

Compare Source

Patch Changes

v1.167.27

Compare Source

Patch Changes

v1.167.26

Compare Source

Patch Changes
TanStack/router (@​tanstack/router-plugin)

v1.168.31

Compare Source

Patch Changes

v1.168.30

Compare Source

Patch Changes

v1.168.29

Compare Source

Patch Changes

v1.168.28

Compare Source

Patch Changes
evanw/esbuild (esbuild)

v0.28.2

Compare Source

  • Fix tree shaking bug due to TypeScript import alias (#​4507)

    This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

    import Base from './dep.js';
    import Alias = Base.SomeType;
  • Fix CSS minification bug involving & (#​4497)

    This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

    /* Original code */
    .a .b {
      & .b:not(& .c) {
        color: red;
      }
    }
    
    /* Old output (with --minify) */
    .a .b{.b:not(& .c){color:red}}
    
    /* New output (with --minify) */
    .a .b{& .b:not(& .c){color:red}}

    This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

  • Avoid overwriting input files without --allow-overwrite (#​4484)

    For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

    This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

  • Fix incorrect code generated when using top-level await (#​4498)

    Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

  • Fix a minification bug with lowered logical assignment operators (#​4508)

    This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

    // Original code
    function foo() {
      let x
      bar(x ||= {})
    }
    
    // Old output (with --minify-syntax --target=es6)
    function foo() {
      bar(void 0 || (x = {}));
    }
    
    // New output (with --minify-syntax --target=es6)
    function foo() {
      let x;
      bar(x || (x = {}));
    }
  • Fix a potential deadlock when the JavaScript API is used incorrectly (#​4503, #​4506)

    The JavaScript API runs the native esbuild executable as a long-lived child process and communicates with it over stdin/stdout/stderr. Each API request is asynchronous and the executable stays open as long as it has work to do, which is as long as either stdin is still open (meaning there may be more API requests) or there are currently requests being processed.

    Previously esbuild's tracking of outstanding API requests missed decrementing a reference count in an edge case where esbuild's JavaScript API was used incorrectly and the API request returned an error. This could in some cases cause esbuild's native executable to exit with an error message about a deadlock. This release fixes the reference counting bug.

    This fix was submitted by @​ZuBB.

  • Handle target collisions (#​4509)

    It's possible to specify the same target engine multiple times, such as with --target=chrome1,chrome99. This edge case wasn't anticipated and previously took the last version for the duplicated target engine instead of the minimum version (so chrome99 in this case instead of chrome1). With this release, esbuild will now pick the minimum version between all duplicated target engines.

  • Force .mp3 files to use the audio/mpeg MIME type (#​4485)

    MIME type detection for esbuild's data URLs uses Go's built-in MIME type detection, which is based on the MIME sniffing standard. This works correctly for MP3 files that start with the byte sequence ID3, which is commonly the case. However, it's possible to construct valid MP3 files that do not start with ID3, and that perhaps Go's built-in MIME type detection doesn't implement the "Signature for MP3 without ID3" part of the algorithm. This results in some .mp3 files incorrectly using the application/octet-stream MIME type instead of audio/mpeg. With this release, esbuild will now always use the audio/mpeg MIME type for files ending in .mp3.

  • Add a new TypeScript syntax warning

    TypeScript 7 turned some previously-valid TypeScript syntax into a syntax error because it was confusing. TypeScript 6 accepts 1 + 2 as number * 3 as valid syntax but confusingly converts it to (1 + 2) * 3 instead of the more intuitive conversion to 1 + (2 * 3). This syntax is now an error in TypeScript 7+. With this release, esbuild will now warn about the use of this syntax:

     [WARNING] Operator "*" should not directly follow a TypeScript type cast after the "+" operator [confusing-typescript-cast]
    
        example.ts:1:28:
          1  console.log(1 + 2 as number * 3)
                                         ^
    
      This is a syntax error in newer versions of TypeScript because the type cast has unintuitive
      precedence in this case. Surround the inner expression in parentheses to silence this warning:
    
        example.ts:1:12:
          1  console.log(1 + 2 as number * 3)
                         ~~~~~~~~~~~~~~~
                         (             )

    See microsoft/TypeScript#63527 for more information.

  • Add support for formatting errors for Visual Studio (#​4460)

    Visual Studio has a specific style that it expects log messages to be in for them to show up in the UI when esbuild is run as a custom build step. The current log style that esbuild uses doesn't conform to this specific style.

    With this release, esbuild has a new log style for Visual Studio (and other tools in the MSBuild ecosystem) that can be enabled with --log-style=visualstudio. Here is an example log message in this style:

    $ esbuild example.ts --log-style=visualstudio
    /Users/evan/dev/esbuild/example.ts(1,29): warning ES0010: Operator "*" should not directly follow a TypeScript type cast after the "+" operator
    

    This log style is also available via the JS and Go APIs, and can now be used with the existing formatMessages API.

  • Fix a bug with CSS gamut mapping (#​4488)

    Due to a typo, the fallback colors generated for CSS colors outside of the sRGB gamut weren't correct. This release fixes the generated colors to use the intended algorithm.

    This fix was submitted by @​chatman-media.

nodeca/js-yaml (js-yaml)

v5.3.0

Compare Source

This release focuses on reworking the documentation and making small
architectural improvements before moving forward.

Added
  • Added completely new documentation.
  • Exported DUMP_SCHEMA, the default schema used by the dumper.
  • Added YAMLException.throwAt() for throwing an error at a source position.
Changed
  • Changed flat constant exports to grouped exports: EVENT_ID, SCALAR_STYLE,
    COLLECTION_STYLE, and CHOMPING_MODE, along with their value types. The old
    exports are still preserved, but deprecated.
  • Made identify mandatory for custom tag definitions. Use
    identify: () => false for load-only tags.
Deprecated
  • Deprecated flat constant exports. Use grouped ones instead.
Removed
  • Removed the MERGE_KEY export (not used anymore after last fixes).
Fixed
  • Validate << sequence items at merge time, so aliased merge sources are
    checked too.
  • Resolve << outside of a mapping key as the plain string '<<', matching
    v4, instead of leaking an internal symbol into the result.
nodejs/node (node)

v24.19.0: 2026-08-03, Version 24.19.0 'Krypton' (LTS), @​aduh95

Compare Source

Notable Changes
  • [d08872b530] - (SEMVER-MINOR) buffer: implement blob.textStream() (Matthew Aitken) #​64036
  • [35222948be] - (SEMVER-MINOR) deps: update OpenSSL build config to support compression (Tim Perry) #​62217
  • [d6ab039f24] - (SEMVER-MINOR) doc: update blockList stability status to release candidate (alphaleadership) #​63050
  • [1da05fb79d] - doc: mark stream.compose stable (Matteo Collina) #​62562
  • [3c1636dabf] - (SEMVER-MINOR) esm: add --experimental-import-text flag (Efe) #​62300
  • [e323e877be] - (SEMVER-MINOR) fs: support caller-supplied readFile() buffers (Matteo Collina) #​63634
  • [c1248c9544] - (SEMVER-MINOR) http: add httpValidation option to configure header value validation (RajeshKumar11) #​61597
  • [a534b65815] - (SEMVER-MINOR) net: support TCP_KEEPINTVL and TCP_KEEPCNT in setKeepAlive (Guy Bedford) #​63825
  • [a23cdec683] - (SEMVER-MINOR) perf_hooks: sample delay per event loop iteration (Pablo Erhard) #​62935
  • [7428b57a37] - (SEMVER-MINOR) src: allow empty --experimental-config-file (Marco Ippolito) #​61610
  • [e57597173c] - (SEMVER-MINOR) stream: expose ReadableStreamTee (Matteo Collina) #​64195
  • [5396235993] - (SEMVER-MINOR) tls: report negotiated TLS groups (Filip Skokan) #​64119
  • [5e901b5cd9] - (SEMVER-MINOR) tls: add certificateCompression option (Tim Perry) #​62217
Commits

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

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

@netlify

netlify Bot commented Mar 28, 2026

Copy link
Copy Markdown

Deploy Preview for aptos-explorer ready!

Name Link
🔨 Latest commit 189481c
🔍 Latest deploy log https://app.netlify.com/projects/aptos-explorer/deploys/69ff7120d1a56a00089f6421
😎 Deploy Preview https://deploy-preview-1557--aptos-explorer.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 0766d90 to e53bcdd Compare March 28, 2026 21:30
@renovate renovate Bot changed the title chore(deps): update dependency @aptos-labs/wallet-adapter-react to v8.3.3 chore(deps): update all non-major dependencies Mar 28, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from a4fe61f to 1a40fef Compare April 6, 2026 17:17
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 2b7e502 to 2162558 Compare April 8, 2026 20:12
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 19 times, most recently from f3fd12f to 323b63b Compare April 19, 2026 12:54
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Apr 19, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 7b67eb2 to 7e808db Compare April 21, 2026 19:39
@renovate

renovate Bot commented May 11, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (1189 entries)...
✓ Lockfile passes supply-chain policies (1189 entries in 11.8s)
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 49, reused 0, downloaded 0, added 0
Progress: resolved 55, reused 0, downloaded 0, added 0
Progress: resolved 98, reused 0, downloaded 0, added 0
Progress: resolved 207, reused 0, downloaded 0, added 0
Progress: resolved 225, reused 0, downloaded 0, added 0
Progress: resolved 230, reused 0, downloaded 0, added 0
Progress: resolved 274, reused 0, downloaded 0, added 0
Progress: resolved 399, reused 0, downloaded 0, added 0
Progress: resolved 414, reused 0, downloaded 0, added 0
Progress: resolved 425, reused 0, downloaded 0, added 0
Progress: resolved 660, reused 0, downloaded 1, added 0
Progress: resolved 935, reused 0, downloaded 1, added 0
Progress: resolved 1015, reused 0, downloaded 1, added 0
Progress: resolved 1077, reused 0, downloaded 1, added 0
Progress: resolved 1078, reused 0, downloaded 1, added 0
[WARN] deprecated @telegram-apps/bridge@1.9.2: This package is not supported anymore. Use @tma.js/bridge instead
Progress: resolved 1188, reused 0, downloaded 1, added 0
Progress: resolved 1189, reused 0, downloaded 1, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 51 versions do not meet the minimumReleaseAge constraint:
  @aptos-labs/ts-sdk@7.3.0 was published at 2026-08-10T19:45:11.166Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/biome@2.5.8 was published at 2026-08-11T08:57:57.925Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-darwin-arm64@2.5.8 was published at 2026-08-11T08:50:58.195Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-darwin-x64@2.5.8 was published at 2026-08-11T08:51:07.735Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-linux-arm64-musl@2.5.8 was published at 2026-08-11T09:01:37.582Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-linux-arm64@2.5.8 was published at 2026-08-11T08:54:25.726Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-linux-x64-musl@2.5.8 was published at 2026-08-11T08:53:52.857Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-linux-x64@2.5.8 was published at 2026-08-11T08:53:42.504Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-win32-arm64@2.5.8 was published at 2026-08-11T08:51:55.213Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @biomejs/cli-win32-x64@2.5.8 was published at 2026-08-11T08:52:05.821Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-router@1.170.28 was published at 2026-08-14T12:11:28.519Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-router@1.170.28 was published at 2026-08-14T12:11:28.519Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-router@1.170.28 was published at 2026-08-14T12:11:28.519Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-router@1.170.28 was published at 2026-08-14T12:11:28.519Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-router@1.170.28 was published at 2026-08-14T12:11:28.519Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-start-client@1.168.26 was published at 2026-08-14T12:12:28.699Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-start-rsc@0.1.44 was published at 2026-08-14T12:11:28.268Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-start-server@1.167.33 was published at 2026-08-14T12:10:27.323Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/react-start@1.168.45 was published at 2026-08-14T12:11:28.066Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-cli@1.167.29 was published at 2026-08-14T12:09:21.606Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-core@1.171.23 was published at 2026-08-14T12:10:27.752Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-generator@1.167.29 was published at 2026-08-14T12:10:27.303Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-generator@1.167.29 was published at 2026-08-14T12:10:27.303Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-generator@1.167.29 was published at 2026-08-14T12:10:27.303Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-plugin@1.168.31 was published at 2026-08-14T12:10:27.693Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/router-plugin@1.168.31 was published at 2026-08-14T12:10:27.693Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-client-core@1.170.23 was published at 2026-08-14T12:11:37.377Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-client-core@1.170.23 was published at 2026-08-14T12:11:37.377Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-client-core@1.170.23 was published at 2026-08-14T12:11:37.377Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-client-core@1.170.23 was published at 2026-08-14T12:11:37.377Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-plugin-core@1.171.35 was published at 2026-08-14T12:10:35.711Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-plugin-core@1.171.35 was published at 2026-08-14T12:10:35.711Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-server-core@1.169.27 was published at 2026-08-14T12:12:37.007Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-server-core@1.169.27 was published at 2026-08-14T12:12:37.007Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-server-core@1.169.27 was published at 2026-08-14T12:12:37.007Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-storage-context@1.167.25 was published at 2026-08-14T12:10:35.171Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-storage-context@1.167.25 was published at 2026-08-14T12:10:35.171Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  @tanstack/start-storage-context@1.167.25 was published at 2026-08-14T12:10:35.171Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  js-yaml@5.3.0 was published at 2026-08-14T09:31:39.879Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  js-yaml@5.3.0 was published at 2026-08-14T09:31:39.879Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)
  rollup-plugin-visualizer@7.1.1 was published at 2026-08-14T07:53:43.553Z, within the minimumReleaseAge cutoff (2026-08-09T18:31:51.180Z)

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.

0 participants