Skip to content

chore(deps): bump the production-minor-and-patch group across 1 directory with 10 updates - #3468

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/production-minor-and-patch-06fcd6642e
Open

chore(deps): bump the production-minor-and-patch group across 1 directory with 10 updates#3468
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/production-minor-and-patch-06fcd6642e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 14, 2026

Copy link
Copy Markdown
Contributor

Bumps the production-minor-and-patch group with 10 updates in the / directory:

Package From To
@shikijs/rehype 4.4.1 4.4.3
@tanstack/react-router 1.170.18 1.170.25
@tanstack/react-start 1.168.34 1.168.42
@vercel/oidc 3.8.1 3.8.4
convex-helpers 0.1.120 0.1.122
jose 6.2.3 6.2.8
lucide-react 1.28.0 1.31.0
resend 6.18.1 6.19.0
shiki 4.4.1 4.4.3
sonner 2.0.7 2.0.8

Updates @shikijs/rehype from 4.4.1 to 4.4.3

Release notes

Sourced from @​shikijs/rehype's releases.

v4.4.3

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v4.4.2

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub
Commits

Updates @tanstack/react-router from 1.170.18 to 1.170.25

Changelog

Sourced from @​tanstack/react-router's changelog.

1.170.25

Patch Changes

  • Updated dependencies [51138a8]:
    • @​tanstack/router-core@​1.171.21

1.170.24

Patch Changes

1.170.23

Patch Changes

  • #7952 95dec51 - bail out of Link re-renders when the resolved href and active state are unchanged

1.170.22

Patch Changes

  • #7992 ea3a665 - retain mounted UI during revalidation

  • Updated dependencies [ea3a665]:

    • @​tanstack/router-core@​1.171.19

1.170.21

Patch Changes

  • #7961 697ebb6 - Prevent a blank frame before zero-delay initial pending UI by using a component-scoped React transition for match publication. Pending timing, boundary selection, and rendered matches continue to come from the router core.

  • #7970 2435885 - createFileRoute does not rely on FileRoute class

  • #7971 86bf510 - clean intersection observer options in link component

  • #7967 6aefb33 - Preserve path params in their raw string form while matching routes so structured values returned by params.parse produce stable match IDs and do not reuse stale loader data.

    RouterCore.getMatchedRoutes() now returns [matchedRoutes, rawParams, foundRoute] instead of an object.

  • Updated dependencies [84db4a8, 9cac62a, 6aefb33]:

    • @​tanstack/router-core@​1.171.18
    • @​tanstack/history@​1.162.1

... (truncated)

Commits

Updates @tanstack/react-start from 1.168.34 to 1.168.42

Changelog

Sourced from @​tanstack/react-start's changelog.

1.168.42

Patch Changes

  • Updated dependencies []:
    • @​tanstack/react-router@​1.170.25
    • @​tanstack/react-start-client@​1.168.23
    • @​tanstack/react-start-rsc@​0.1.41
    • @​tanstack/react-start-server@​1.167.30
    • @​tanstack/start-client-core@​1.170.21
    • @​tanstack/start-plugin-core@​1.171.33
    • @​tanstack/start-server-core@​1.169.25

1.168.41

Patch Changes

  • Updated dependencies [c59788c]:
    • @​tanstack/start-client-core@​1.170.20
    • @​tanstack/react-router@​1.170.24
    • @​tanstack/react-start-client@​1.168.22
    • @​tanstack/react-start-rsc@​0.1.40
    • @​tanstack/react-start-server@​1.167.29
    • @​tanstack/start-plugin-core@​1.171.32
    • @​tanstack/start-server-core@​1.169.24

1.168.40

Patch Changes

  • Updated dependencies [2fbc99f, 95dec51, 6bede65]:
    • @​tanstack/start-client-core@​1.170.19
    • @​tanstack/react-router@​1.170.23
    • @​tanstack/react-start-client@​1.168.21
    • @​tanstack/react-start-rsc@​0.1.39
    • @​tanstack/start-server-core@​1.169.23
    • @​tanstack/react-start-server@​1.167.28
    • @​tanstack/start-plugin-core@​1.171.31

1.168.39

Patch Changes

  • Updated dependencies [ea3a665]:
    • @​tanstack/react-router@​1.170.22
    • @​tanstack/react-start-client@​1.168.20
    • @​tanstack/react-start-rsc@​0.1.38
    • @​tanstack/react-start-server@​1.167.27
    • @​tanstack/start-client-core@​1.170.18
    • @​tanstack/start-plugin-core@​1.171.30

... (truncated)

Commits

Updates @vercel/oidc from 3.8.1 to 3.8.4

Changelog

Sourced from @​vercel/oidc's changelog.

@​vercel/oidc

Commits

Updates convex-helpers from 0.1.120 to 0.1.122

Changelog

Sourced from convex-helpers's changelog.

0.1.122

  • Support TypeScript 7.

0.1.121

  • Support the new db.vars.commitTs variable and v.commitTs() validator added in convex 1.43.0.
  • convex-helpers/server/compare is deprecated and now re-exports compareValues from convex/values. There may be small differences in behavior in uncommon cases (NaNs, negative zero, etc.) compared with the previous implementation.
Commits
Maintainer changes

This version was pushed to npm by reece-convex, a new releaser for convex-helpers since your current version.


Updates jose from 6.2.3 to 6.2.8

Release notes

Sourced from jose's releases.

v6.2.8

Fixes

  • enforce a single recipient when decrypting dir and ECDH-ES (505c383)
  • reject a non-string "alg" in EmbeddedJWK (714f870)

Refactor

  • index the JWS and JWE registries without a wrapper (925f3bb)
  • name the "alg" source in unsupported algorithm failures (1500459)

v6.2.7

Fixes

  • require own JOSE properties for presence checks (90ab09c)

Refactor

v6.2.6

Fixes

  • types: accept host CryptoKey declarations (b48a15b)

v6.2.5

Fixes

  • compare claim values for falsy validation options (eb86956)
  • forward key management parameters for a single JWE recipient (2d4f801)
  • handle a zero-length JWE additional authenticated data (16ca398)
  • reject a generateKeyPair crv option the algorithm does not imply (76364e9)
  • reject an unencoded payload in the JWS Compact Serialization (01d053f)
  • reject characters outside the Base64URL alphabet (0ebb971), references #879
  • reject duplicate "crit" values when producing (31d60e1)
  • reject invalid UTF-8 in JOSE Headers and JWT Claims Sets (5df3fed)
  • reject truncated ASN.1 key data (7a16c66)
  • surface non-ASCII token segments as JOSE errors (194fe11)
  • types: correct JWK and CryptoKey types (62a196d)
  • types: correct key resolver and JWT header types (e95f8c4)
  • validate the clockTolerance and currentDate options are finite (ab2f18d)

Documentation

  • correct subpaths and API documentation (2daec38)
  • document consumer-supplied type parameters (9e9f66c)
  • stop claiming the JWK "use" parameter is used during import (47a07b2)
  • update CHANGELOG.md (fc51bf5)

Refactor

... (truncated)

Changelog

Sourced from jose's changelog.

6.2.8 (2026-08-03)

Fixes

  • enforce a single recipient when decrypting dir and ECDH-ES (505c383)
  • reject a non-string "alg" in EmbeddedJWK (714f870)

Refactor

  • index the JWS and JWE registries without a wrapper (925f3bb)
  • name the "alg" source in unsupported algorithm failures (1500459)

6.2.7 (2026-08-01)

Fixes

  • require own JOSE properties for presence checks (90ab09c)

Refactor

6.2.6 (2026-07-31)

Fixes

  • types: accept host CryptoKey declarations (b48a15b)

6.2.5 (2026-07-29)

Fixes

  • compare claim values for falsy validation options (eb86956)
  • forward key management parameters for a single JWE recipient (2d4f801)
  • handle a zero-length JWE additional authenticated data (16ca398)
  • reject a generateKeyPair crv option the algorithm does not imply (76364e9)
  • reject an unencoded payload in the JWS Compact Serialization (01d053f)
  • reject characters outside the Base64URL alphabet (0ebb971), references #879
  • reject duplicate "crit" values when producing (31d60e1)
  • reject invalid UTF-8 in JOSE Headers and JWT Claims Sets (5df3fed)
  • reject truncated ASN.1 key data (7a16c66)
  • surface non-ASCII token segments as JOSE errors (194fe11)
  • types: correct JWK and CryptoKey types (62a196d)
  • types: correct key resolver and JWT header types (e95f8c4)
  • validate the clockTolerance and currentDate options are finite (ab2f18d)

Documentation

  • correct subpaths and API documentation (2daec38)
  • document consumer-supplied type parameters (9e9f66c)

... (truncated)

Commits
  • 8b768eb chore(release): 6.2.8
  • 1500459 refactor: name the "alg" source in unsupported algorithm failures
  • 714f870 fix: reject a non-string "alg" in EmbeddedJWK
  • 925f3bb refactor: index the JWS and JWE registries without a wrapper
  • 505c383 fix: enforce a single recipient when decrypting dir and ECDH-ES
  • 514831d chore(deps): bump the actions group with 3 updates
  • 45965db chore: cleanup after release
  • 60b941f chore(release): 6.2.7
  • 90ab09c fix: require own JOSE properties for presence checks
  • 767d7f1 refactor: reduce bundle size
  • Additional commits viewable in compare view

Updates lucide-react from 1.28.0 to 1.31.0

Release notes

Sourced from lucide-react's releases.

Version 1.31.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.30.0...1.31.0

Version 1.30.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.29.0...1.30.0

Version 1.29.0

What's Changed

Full Changelog: lucide-icons/lucide@1.28.0...1.29.0

Commits

Updates resend from 6.18.1 to 6.19.0

Release notes

Sourced from resend's releases.

v6.19.0

What's Changed

New Contributors

Full Changelog: resend/resend-node@v6.18.1...v6.19.0

Commits

Updates shiki from 4.4.1 to 4.4.3

Release notes

Sourced from shiki's releases.

v4.4.3

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v4.4.2

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub
Commits

Updates sonner from 2.0.7 to 2.0.8

Release notes

Sourced from sonner's releases.

v2.0.8

What's Changed

New Contributors

Full Changelog: emilkowalski/sonner@v2.0.7...v2.0.8

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

…tory with 10 updates

Bumps the production-minor-and-patch group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@shikijs/rehype](https://github.com/shikijs/shiki/tree/HEAD/packages/rehype) | `4.4.1` | `4.4.3` |
| [@tanstack/react-router](https://github.com/TanStack/router/tree/HEAD/packages/react-router) | `1.170.18` | `1.170.25` |
| [@tanstack/react-start](https://github.com/TanStack/router/tree/HEAD/packages/react-start) | `1.168.34` | `1.168.42` |
| [@vercel/oidc](https://github.com/vercel/vercel/tree/HEAD/packages/oidc) | `3.8.1` | `3.8.4` |
| [convex-helpers](https://github.com/get-convex/convex-helpers/tree/HEAD/packages/convex-helpers) | `0.1.120` | `0.1.122` |
| [jose](https://github.com/panva/jose) | `6.2.3` | `6.2.8` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.28.0` | `1.31.0` |
| [resend](https://github.com/resend/resend-node) | `6.18.1` | `6.19.0` |
| [shiki](https://github.com/shikijs/shiki/tree/HEAD/packages/shiki) | `4.4.1` | `4.4.3` |
| [sonner](https://github.com/emilkowalski/sonner) | `2.0.7` | `2.0.8` |



Updates `@shikijs/rehype` from 4.4.1 to 4.4.3
- [Release notes](https://github.com/shikijs/shiki/releases)
- [Commits](https://github.com/shikijs/shiki/commits/v4.4.3/packages/rehype)

Updates `@tanstack/react-router` from 1.170.18 to 1.170.25
- [Release notes](https://github.com/TanStack/router/releases)
- [Changelog](https://github.com/TanStack/router/blob/main/packages/react-router/CHANGELOG.md)
- [Commits](https://github.com/TanStack/router/commits/@tanstack/react-router@1.170.25/packages/react-router)

Updates `@tanstack/react-start` from 1.168.34 to 1.168.42
- [Release notes](https://github.com/TanStack/router/releases)
- [Changelog](https://github.com/TanStack/router/blob/main/packages/react-start/CHANGELOG.md)
- [Commits](https://github.com/TanStack/router/commits/@tanstack/react-start@1.168.42/packages/react-start)

Updates `@vercel/oidc` from 3.8.1 to 3.8.4
- [Release notes](https://github.com/vercel/vercel/releases)
- [Changelog](https://github.com/vercel/vercel/blob/main/packages/oidc/CHANGELOG.md)
- [Commits](https://github.com/vercel/vercel/commits/@vercel/next@3.8.4/packages/oidc)

Updates `convex-helpers` from 0.1.120 to 0.1.122
- [Changelog](https://github.com/get-convex/convex-helpers/blob/main/packages/convex-helpers/CHANGELOG.md)
- [Commits](https://github.com/get-convex/convex-helpers/commits/npm/0.1.122/packages/convex-helpers)

Updates `jose` from 6.2.3 to 6.2.8
- [Release notes](https://github.com/panva/jose/releases)
- [Changelog](https://github.com/panva/jose/blob/main/CHANGELOG.md)
- [Commits](panva/jose@v6.2.3...v6.2.8)

Updates `lucide-react` from 1.28.0 to 1.31.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.31.0/packages/lucide-react)

Updates `resend` from 6.18.1 to 6.19.0
- [Release notes](https://github.com/resend/resend-node/releases)
- [Changelog](https://github.com/resend/resend-node/blob/canary/CHANGELOG.md)
- [Commits](resend/resend-node@v6.18.1...v6.19.0)

Updates `shiki` from 4.4.1 to 4.4.3
- [Release notes](https://github.com/shikijs/shiki/releases)
- [Commits](https://github.com/shikijs/shiki/commits/v4.4.3/packages/shiki)

Updates `sonner` from 2.0.7 to 2.0.8
- [Release notes](https://github.com/emilkowalski/sonner/releases)
- [Commits](emilkowalski/sonner@v2.0.7...v2.0.8)

---
updated-dependencies:
- dependency-name: "@shikijs/rehype"
  dependency-version: 4.4.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: "@tanstack/react-router"
  dependency-version: 1.170.25
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: "@tanstack/react-start"
  dependency-version: 1.168.42
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: "@vercel/oidc"
  dependency-version: 3.8.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: convex-helpers
  dependency-version: 0.1.122
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: jose
  dependency-version: 6.2.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: lucide-react
  dependency-version: 1.31.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-and-patch
- dependency-name: resend
  dependency-version: 6.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-minor-and-patch
- dependency-name: shiki
  dependency-version: 4.4.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
- dependency-name: sonner
  dependency-version: 2.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 14, 2026
@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clawhub Building Building Preview Aug 14, 2026 4:06pm

Request Review

@clawsweeper clawsweeper Bot added merge-risk: 🚨 auth-provider 🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials. merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. P2 Normal backlog priority with limited blast radius. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Aug 14, 2026
@clawsweeper

clawsweeper Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Codex review: found issues before merge. Reviewed August 14, 2026, 12:09 PM ET / 16:09 UTC.

ClawSweeper review

What this changes

The PR updates ten direct production dependencies in package.json and refreshes the corresponding Bun lockfile entries.

Merge readiness

Blocked by patch quality or review findings - 7 items remain

Keep open: the focused dependency update introduces a second, older jose resolution used by ClawHub’s authentication stack, so the auth-sensitive update is incomplete until that lockfile resolution is corrected and validated.

Priority: P2
Reviewed head: fc3479e3bd41563f4e77803c06a9dd82458ba7ba

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) PR readiness rating was derived from proof quality, review findings, security review, and reviewer confidence.
Proof confidence 🌊 off-meta tidepool Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Patch quality 🧂 unranked krab (1/6) Security review found an item that needs attention.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Evidence reviewed 5 items Current main has the older direct versions: Current main still pins the ten pre-update versions, so this PR is not already implemented or superseded on main.
Incomplete jose resolution: The PR upgrades the root jose resolution to 6.2.8 but adds a separate @auth/core/jose resolution at 6.2.3, despite @auth/core declaring compatible jose ^6.0.6.
Auth code consumes the affected package: ClawHub’s Convex authentication module imports the GitHub provider from @auth/core, making the separate old jose resolution relevant to login processing.
Findings 1 actionable finding [P2] Resolve @auth/core to the updated jose release
Security Needs attention Authentication retains an older jose resolution: @auth/core receives a new nested jose 6.2.3 entry despite the root upgrade to 6.2.8 and a compatible declared range; this leaves an auth-sensitive consumer on a separate older crypto package.

How this fits together

ClawHub’s web app and Convex backend resolve runtime packages from the root dependency manifest and Bun lockfile. Those packages support routing, authentication, token verification, email, and UI rendering in the deployed registry.

flowchart LR
  A[Package manifest] --> B[Bun lockfile]
  B --> C[Web application build]
  B --> D[Convex authentication]
  C --> E[Registry interface]
  D --> F[Login and token checks]
Loading

Before merge

  • Resolve @auth/core to the updated jose release (P2) - The root dependency moves to jose 6.2.8, but this added lock entry makes @auth/core install 6.2.3 even though its declared ^6.0.6 range accepts 6.2.8. ClawHub imports @auth/core in its authentication module, so regenerate or constrain the graph to avoid leaving login on the older divergent package version, then validate the auth path.
  • Resolve security concern: Authentication retains an older jose resolution - @auth/core receives a new nested jose 6.2.3 entry despite the root upgrade to 6.2.8 and a compatible declared range; this leaves an auth-sensitive consumer on a separate older crypto package.
  • Resolve merge risk (P1) - @auth/core will resolve its own older jose 6.2.3 while direct token code resolves 6.2.8, leaving authentication on a divergent crypto dependency.
  • Resolve merge risk (P1) - No after-update real behavior proof or completed required validation is present for the production dependency graph.
  • Complete next step (P2) - A maintainer must verify the corrected authentication resolution and real after-update validation; the missing proof cannot be supplied safely by an automated repair lane.
  • Improve patch quality - Resolve the security review concern or explain why the changed path is safe.
  • Improve patch quality - Address the highest-priority review finding and re-run the changed-surface validation.

Findings

  • [P2] Resolve @auth/core to the updated jose release — bun.lock:2027
  • [medium] Authentication retains an older jose resolution — bun.lock:2027
Agent review details

Security

Needs attention: The lockfile introduces an older jose resolution into the authentication dependency tree while upgrading the direct crypto dependency.

Review metrics

Metric Value Why it matters
Dependency surface 10 direct production updates; 2 files; +54/-76 lines The patch is narrowly scoped, but it changes packages used by routing, authentication, backend helpers, email, and the UI.

Merge-risk options

Maintainer options:

  1. Repair the auth dependency resolution (recommended)
    Regenerate or constrain the lockfile so @auth/core no longer installs jose 6.2.3 beside the direct 6.2.8 update, then run focused authentication and repository validation.
  2. Pause this grouped update
    Defer the PR if a compatible single-version jose resolution cannot be proven without changing the intended authentication dependency contract.

Technical review

Best possible solution:

Regenerate or constrain the Bun graph so direct token code and @auth/core use one compatible current jose v6 resolution, then validate the authentication path and required type/build gates before merging.

Do we have a high-confidence way to reproduce the issue?

Yes: the PR-head lockfile directly shows root jose at 6.2.8 and @auth/core/jose at 6.2.3, while current authentication code imports @auth/core.

Is this the best way to solve the issue?

No: the grouped update is appropriate, but the resulting split jose resolution is not the narrowest safe outcome for the authentication path.

Full review comments:

  • [P2] Resolve @auth/core to the updated jose release — bun.lock:2027
    The root dependency moves to jose 6.2.8, but this added lock entry makes @auth/core install 6.2.3 even though its declared ^6.0.6 range accepts 6.2.8. ClawHub imports @auth/core in its authentication module, so regenerate or constrain the graph to avoid leaving login on the older divergent package version, then validate the auth path.
    Confidence: 0.93

Overall correctness: patch is incorrect
Overall confidence: 0.93

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 36b775a6d9a0.

Labels

Label changes:

  • add P2: The lockfile issue affects a production authentication dependency and needs correction before this routine update can land.
  • add merge-risk: 🚨 auth-provider: The new nested jose resolution is consumed through @auth/core in ClawHub’s login path.
  • add merge-risk: 🚨 security-boundary: The divergent lockfile resolution leaves token and authentication code on different cryptographic package patch versions.
  • add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Label justifications:

  • P2: The lockfile issue affects a production authentication dependency and needs correction before this routine update can land.
  • merge-risk: 🚨 auth-provider: The new nested jose resolution is consumed through @auth/core in ClawHub’s login path.
  • merge-risk: 🚨 security-boundary: The divergent lockfile resolution leaves token and authentication code on different cryptographic package patch versions.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Evidence

Security concerns:

  • [medium] Authentication retains an older jose resolution — bun.lock:2027
    @auth/core receives a new nested jose 6.2.3 entry despite the root upgrade to 6.2.8 and a compatible declared range; this leaves an auth-sensitive consumer on a separate older crypto package.
    Confidence: 0.93

What I checked:

  • Current main has the older direct versions: Current main still pins the ten pre-update versions, so this PR is not already implemented or superseded on main. (package.json:118, 36b775a6d9a0)
  • Incomplete jose resolution: The PR upgrades the root jose resolution to 6.2.8 but adds a separate @auth/core/jose resolution at 6.2.3, despite @auth/core declaring compatible jose ^6.0.6. (bun.lock:2027, fc3479e3bd41)
  • Auth code consumes the affected package: ClawHub’s Convex authentication module imports the GitHub provider from @auth/core, making the separate old jose resolution relevant to login processing. (convex/auth.ts:1, 36b775a6d9a0)
  • Dependabot grouping intent: Repository configuration defines this as the daily production minor-and-patch dependency group; the current two-file scope matches that configured workflow. (.github/dependabot.yml:25, 87ca030c30f3)
  • Dependency-maintenance provenance: The production dependency group appears to date to the current configuration baseline, while recent package history includes both security-focused and grouped dependency maintenance. (.github/dependabot.yml:1, 87ca030c30f3)

Likely related people:

  • Patrick Erichsen: Introduced the current Dependabot configuration baseline and is the most frequent contributor in package-manifest history. (role: dependency-workflow author and recent package contributor; confidence: high; commits: 87ca030c30f3, 36b775a6d9a0, 60b02c09f936; files: .github/dependabot.yml, package.json, bun.lock)
  • Yiğit ERDOĞAN: Recently updated advisory-hit packages in the same dependency manifest, making them a useful adjacent reviewer for the lockfile resolution. (role: recent security dependency contributor; confidence: medium; commits: 8b31a7e6e1a5; files: package.json, bun.lock)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 auth-provider 🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials. merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. P2 Normal backlog priority with limited blast radius. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants