chore(deps): Update production (non-major) #358

Open
renovate wants to merge 1 commit from renovate/production-(non-major) into main
Collaborator

This PR contains the following updates:

Package Change Age Confidence
@fedify/fedify (source) 2.4.5 → 2.4.6 age confidence
@garmin/fitsdk 21.221.0 → 21.222.0 age confidence
@sentry/node (source) 11.13.0 → 11.14.0 age confidence
@sentry/react (source) 11.13.0 → 11.14.0 age confidence
expo (source) 58.0.25 → 58.0.26 age confidence
i18next-browser-languagedetector 8.3.0 → 8.3.1 age confidence

Release Notes

fedify-dev/fedify (@​fedify/fedify)

v2.4.6

Compare Source

Released on November 17, 2026.

@​fedify/fedify
  • Fixed Context.sendActivity() and InboxContext.forwardActivity() giving
    up on the remaining deliveries when one recipient failed. The immediate
    delivery paths now wait for every delivery they have already started before
    propagating the error, so the remaining recipients are still reached on
    runtimes such as Cloudflare Workers, which may terminate an isolate once
    the error response is returned. This applies both to immediate: true and
    to federations without an outbox queue.
    [#​1380, #​1388]
  • Fixed CryptoKey and CryptoKeyPair values obtained from node:crypto
    being rejected by ActorKeyPairsDispatcher, SharedInboxKeyDispatcher,
    SenderKeyPair, signRequest(), createProof(), signObject(),
    createSignature(), signJsonLd(), exportJwk(), and the authenticated
    document loader APIs when @types/node 24.7.0 or later is installed.
    Those APIs now accept a structural key type that both Node.js and
    DOM/Web Worker keys satisfy, while the keys returned by Fedify keep the
    ambient CryptoKey types. SenderKeyPair and
    SharedInboxKeyDispatcher take a type parameter that defaults to
    CryptoKey, so code that reads a key pair or calls a dispatcher keeps the
    narrower type.
    [#​554, #​1391]
  • Fixed Linked Data Signature verification rejecting documents with unmapped
    extension properties, such as an undefined quoteUri, that the sender's
    JSON-LD processor discards. Discarded properties are not authenticated by
    the signature. Outbound signing still rejects lossy input, and verification
    continues to reject relative IRIs and unsafe graph structures.
    [#​1405, #​1411]
  • Fixed Linked Data Signatures being emitted with a JSON-LD context that no
    longer resolves. The attached signature object now uses
    https://w3id.org/security/v1 instead of
    https://w3id.org/identity/v1, which redirects to an unreachable host.
    Documents signed through signJsonLd() or attachSignature() whose
    context does not define signature now also get a minimal inline
    definition of that term, so the signed document remains valid JSON-LD.
    Documents that already carry a proof are left unchanged, since a new
    context definition would invalidate the proof. Activities queued for
    fanout before the upgrade also keep their original proof-covered JSON when
    replayed. Incoming signatures that still use identity/v1 continue to
    verify. [#​664]
  • Fixed automatic queue worker startup failures becoming unhandled promise
    rejections. When manuallyStartQueue was left false and a MessageQueue
    implementation could not start listening, such as WorkersMessageQueue on
    Cloudflare Workers whose listen() throws a TypeError, the rejection from
    the implicit startup in inbox handling and in Context.sendActivity() was
    discarded. It is now logged as a warning once per Federation instance,
    and a synchronous throw from one queue no longer prevents the remaining
    queues from starting. The failed worker is not retried, so restart the
    process after fixing the queue. Federation.startQueue() still rejects so
    callers that start workers deliberately see the error, and Cloudflare
    Workers deployments should set manuallyStartQueue: true to avoid the
    warning entirely.
    [#​1381, #​1390]
  • Fixed inbox handling that treated valid date-times without seconds, such
    as 2024-01-01T10:00Z or 2024-01-01T10:00.5Z, as permanently malformed.
    Activity Streams 2.0 allows seconds to be omitted, so activities with such
    date-times are no longer rejected or dropped. Activities whose
    Question.closed is a date-like but impossible value, such as
    2024-02-31T10:00.5Z, are now treated as malformed instead of being
    accepted with closed discarded.
    [#​1339, #​1347 by ChanHaeng Lee]
  • Fixed incoming Linked Data Signatures without a created field being
    treated as unsigned. Valid RsaSignature2017 signatures without that field
    now verify through the JSON-LD APIs and inbox, including queued inbox
    processing, and are forwarded when skipIfUnsigned is enabled.
    Malformed signature objects now produce a debug log with
    their property names. Invalid creator URLs now fail verification without
    throwing an exception. Outgoing signatures still include created.
    [#​1406, #​1413]
  • Fixed singleton attachment values being serialized as objects in actor,
    object, and collection responses, which caused Mastodon to ignore a single
    profile field. Served responses and newly generated activity deliveries
    now preserve attachment arrays when the JSON-LD context permits it.
    Documents containing existing proofs or Linked Data signatures are left
    unchanged by the compatibility rewrite. New normalized deliveries are
    signed over the same JSON used for queueing and transport.
    [#​1421, #​1422, mastodon/mastodon#41640]
  • Fixed the fanout worker never starting when the fanout queue was the only
    configured queue. Federation.startQueue() returned without calling
    fanoutQueue.listen(), so fanout messages were enqueued but never
    consumed; the implicit startup triggered by a fanout enqueue silently did
    nothing. Both paths now start the fanout worker, and deployments that
    configure only queue: { fanout: ... } no longer need to add an unused
    inbox or outbox queue to make fanout delivery work.
    [#​1389, #​1392]
  • Limited WebFinger lookups made through federation contexts to 10 seconds
    per lookup. [GHSA-9pmv-w936-hj3f]
  • Limited each outgoing activity delivery attempt to 30 seconds, including
    redirects and HTTP signature retries, so a slow remote inbox cannot hold a
    delivery worker indefinitely. Timed-out attempts follow the configured
    retry schedule. [GHSA-fq5h-gjhp-g75x]
  • NodeInfo lookups now stop following a redirect when its target repeats an
    earlier URL in the same chain. A self-redirect previously opened five
    fetch sessions before hitting the redirect limit; it now stops after the
    first response. The existing redirect limit still applies to chains
    without cycles.
    [GHSA-64hq-2hgr-q4pm]
  • NodeInfo lookups now time out after 10 seconds by default. A remote server
    could previously keep getNodeInfo() or Context.lookupNodeInfo() waiting
    indefinitely by delaying a response. The limit covers discovery,
    redirects, and the document body as one operation. Pass a timeout value
    in milliseconds to allow more time, or null to disable the limit; a
    timed-out lookup returns undefined.
    An optional signal can cancel the lookup, even with timeout: null.
    [GHSA-64hq-2hgr-q4pm]
  • On Node.js, NodeInfo hostname resolution now starts at most two operating
    system DNS lookups at a time. Other hosts can still resolve when one
    resolver call stalls. A queued lookup can time out or be cancelled before
    starting, so repeated abandoned NodeInfo requests cannot fill the shared
    libuv thread pool. An already-running operating system lookup cannot be
    cancelled.
    [GHSA-64hq-2hgr-q4pm]
  • Fixed signObject() and the default activity transformers,
    autoIdAssigner() and actorDehydrator(), dropping the default FEP-ef61
    portable object verifier of the object they returned a copy of. Their
    results now keep the verifier, so their accessors verify portable objects
    as the original object's accessors do, and they no longer log
    the warning that clone() logs when it drops the verifier.
    [#​1399, #​1442]
@​fedify/backfill
  • Fixed backfill accepting documentLoader results with spoofed origins.
    Results whose declared ID origin differs from the requested IRI's origin
    are now ignored, including otherwise valid cross-origin redirects.
    Custom loaders must still validate IDs against the final response URL:
    pass custom JSON-LD loaders through lookupObject() and set documentUrl
    to the final response URL after redirects.
    [GHSA-h3jv-px69-2gpj]
  • Fixed backfill trusting cross-origin embedded objects, which allowed a
    remote document to spoof content from another origin. Backfill now
    dereferences these objects by their IDs before yielding them. It also
    ignores a documentLoader result whose ID has a different origin from the
    requested IRI. Consequently, objects reached through a cross-origin
    redirect are ignored. Custom loaders should pass their JSON-LD loader to
    lookupObject() so it can validate the object's ID against the final
    response URL. Backfilled objects remain unverified remote data and should
    be authenticated before they are persisted or otherwise trusted.
    [GHSA-x58x-xx7h-7rh4]
@​fedify/cli
  • The fedify nodeinfo command now accepts -T/--timeout in seconds.
    It defaults to 10 seconds and reports a timeout separately from a missing
    or invalid NodeInfo document.
    [GHSA-64hq-2hgr-q4pm]
@​fedify/nestjs
  • Fixed require("@fedify/nestjs") failing with MODULE_NOT_FOUND, which
    broke the integration in NestJS projects compiled to CommonJS, the NestJS
    default. The package manifest pointed its CommonJS entry point and type
    declarations at files that the build no longer produced; they now point
    to the files that are actually shipped, so the integration loads with
    require() again and TypeScript finds its declarations. ESM imports were
    not affected.
    [#​1424, #​1428]
@​fedify/next
  • Fixed fedifyWith() not forwarding NodeInfo document requests such as
    GET /nodeinfo/2.1 without federation media types in their headers.
    isNodeInfoRequest() and isFederationRequest() now recognize paths under
    /nodeinfo/ regardless of their headers, so clients using
    Accept: application/json, */*, or no Accept header can reach the
    dispatcher. Existing applications must also add
    { source: "/nodeinfo/:path*" } to the matcher in their middleware.ts
    or proxy.ts. Dispatchers outside /nodeinfo/ still require explicit
    delegation to integrateFederation() and a matching matcher entry.
    [#​1402, #​1412]
@​fedify/testing
  • Fixed MockFederation.receiveActivity() dropping the default FEP-ef61
    portable object verifier of the received activity when it attaches its
    document loaders to the activity passed to inbox listeners.
    [#​1399, #​1442]
@​fedify/vocab
  • Added a warning when clone() drops the default FEP-ef61 portable object
    verifier of a vocabulary object, and documented that clone() does not
    inherit it. Objects that Fedify parses for you, such as activities that
    inboxes receive and the results of Context.lookupObject(), have
    Context.verifyPortableObject as their default, so an existing
    application that clones them now logs a warning in the
    ["fedify", "vocab", "portable"] category. A clone without a verifier
    does not verify the portable objects embedded in it, and refuses to
    dereference portable references. Pass
    verifyPortableObject: ctx.verifyPortableObject to clone() to keep
    verifying them, or verifyPortableObject: undefined to drop the verifier
    deliberately without the warning. The verifyPortableObject option of
    clone() now explicitly accepts undefined, so that the opt-out also
    type-checks with exactOptionalPropertyTypes. [#​1399, #​1442]
  • Fixed CryptographicKey and Multikey rejecting a publicKey obtained
    from node:crypto in their constructors and clone() when @types/node
    24.7.0 or later is installed. The property accepts a structural key type
    now, while the getters still return the ambient CryptoKey type.
    [#​554, #​1391]
  • Fixed an origin-check bypass that allowed crafted JSON-LD without a parent
    id to return forged embedded objects claiming another origin.
    [GHSA-r388-57j3-5fgp]
  • Fixed invalid JSON-LD when a collection page embeds a parsed item whose
    context redefines a protected parent term, such as proof. Default
    serialization now isolates independent child contexts while preserving
    their cached documents and extension meanings. The parent's @context
    array gains property-scoped definitions, including for generated children
    with matching contexts; context-aware consumers need JSON-LD 1.1 support.
    Resolving the parent context uses contextLoader; URL references alongside
    isolated children are represented as objects with id and their own
    context.
    [#​1394, #​1397]
  • Fixed parsing of date-times without seconds, such as 2024-01-01T10:00Z,
    2024-01-01T10:00+09:00, or 2024-01-01T10:00.5Z, which Activity Streams
    2.0 allows. They raised a RangeError, or were ignored in
    Question.closed when they had a fraction. Date-like but impossible
    values in Question.closed, such as 2024-02-31T10:00.5Z, now raise a
    RangeError instead of being silently dropped.
    [#​1339, #​1347 by ChanHaeng Lee]
  • Limited WebFinger lookups used by object resolution to 10 seconds each,
    and actor handle resolution to one 10-second deadline across alias checks.
    Actor handle resolution now checks at most 100 subject/alias candidates and
    skips duplicates.
    [GHSA-9pmv-w936-hj3f]
  • Replaced https://w3id.org/identity/v1 with
    https://w3id.org/security/v1 in the default JSON-LD contexts of activity
    types. The former no longer resolves, and https://w3id.org/security/v1
    defines the same terms the signatures use.
    [#​664, #​1351]
@​fedify/vocab-runtime
  • Added normalizeDateTimeLiteral() to @fedify/vocab-runtime/temporal so
    that generated vocabulary code and @fedify/fedify interpret xsd:dateTime
    literals the same way. It treats a literal without a UTC offset as UTC and
    handles literals without seconds, including those with a fraction.
    [#​1339, #​1347 by ChanHaeng Lee]
  • Added the CryptoKeyLike and CryptoKeyPairLike types for the structural
    key shape that Fedify APIs accept. They cover keys from Node.js,
    DOM/Web Workers, and Cloudflare Workers, so exportSpki(),
    exportMultibaseKey(), and getAuthenticatedDocumentLoader() no longer
    reject keys obtained from node:crypto with @types/node 24.7.0 or later.
    AuthenticatedDocumentLoaderFactory keeps the ambient CryptoKey type on
    the identity it receives, so existing implementations do not have to
    change.
    [#​554, #​1391]
@​fedify/vocab-tools
  • Changed the code generated by @fedify/vocab-tools to import the
    CryptoKeyLike type from @fedify/vocab-runtime. Regenerated code now
    requires @fedify/vocab-runtime 2.4.6 or later.
    [#​554, #​1391]
  • Fixed generated accessors bypassing origin checks for embedded objects when
    the parent has no id. Regenerate your vocabulary code to apply the fix.
    [GHSA-r388-57j3-5fgp]
  • Fixed generated default encoders combining independent child documents
    with conflicting inherited JSON-LD contexts. Child documents retain their
    original contexts and extension meanings, including in collections and
    inherited properties. Generated parents gain property-scoped definitions
    in their @context arrays even when child and parent contexts match.
    Regenerate your vocabulary code to apply the fix.
    [#​1394, #​1397]
  • Fixed generated xsd:dateTime decoders failing on date-times without
    seconds, such as 2024-01-01T10:00Z or 2024-01-01T10:00.5Z. Regenerate
    your vocabulary code to get the fix. Generated code now imports
    normalizeDateTimeLiteral() from @fedify/vocab-runtime/temporal.
    [#​1339, #​1347 by ChanHaeng Lee]
  • Generated clone() methods now log a warning in the
    ["fedify", "vocab", "portable"] category when they drop the default
    FEP-ef61 portable object verifier of the source object, i.e., when the
    source has one and the call does not pass the verifyPortableObject
    option. An explicit verifyPortableObject: undefined drops it without
    the warning. Their API documentation now states that clone() does not
    inherit the default verifier. Regenerate custom vocabularies to get
    the warning. [#​1399, #​1442]
@​fedify/webfinger
  • Limited WebFinger lookups to 10 seconds across DNS resolution, redirects,
    and response reading. A caller's abort signal can end a lookup sooner.
    This prevents slow endpoints from occupying lookup workers indefinitely.
    [GHSA-9pmv-w936-hj3f]
garmin/fit-javascript-sdk (@​garmin/fitsdk)

v21.222.0

Compare Source

See release notes for full list of changes
https://forums.garmin.com/developer/fit-sdk/b/news-announcements

getsentry/sentry-javascript (@​sentry/node)

v11.14.0

Compare Source

Important Changes
  • feat(browser): Add browserTracingCoreIntegration and standalone tracing integrations (#​26259, #​26260, #​26261, #​26262, #​26273, #​26276, #​26497)

    browserTracingIntegration now sets up fetch and XHR request spans, linked traces, long tasks and resource spans through the standalone fetchTracingIntegration, xhrTracingIntegration, linkedTracesIntegration, longTasksIntegration and resourcesIntegration. Its behavior is unchanged. To ship less code, use browserTracingCoreIntegration, which keeps pageload and navigation spans, and add only the standalone integrations you need. The CDN bundles export them too.

  • ref(server-utils): Share one cron converter across cron integrations (#​25918)

    Sentry.cron.instrumentCron, instrumentNodeCron and instrumentNodeSchedule send the server's time zone when a job has none, so monitors don't report false misses on servers that aren't on UTC. Schedules Sentry can't express exactly, such as per-second schedules, send no monitor config, so the monitor keeps the schedule set in Sentry. Sentry.cron.instrumentNodeCron is deprecated; use nodeCronIntegration instead.

  • fix(nuxt): Name the database system in db.system.name of db0 spans (#​26285)

    Nitro database (db0) spans now set db.system.name to the database system of the connector's dialect (mysql, postgresql, sqlite or libsql), as the OpenTelemetry conventions define it, instead of the connector name. For example, spans of the mysql2 and planetscale connectors now report mysql, and spans of better-sqlite3 and cloudflare-d1 now report sqlite. Update saved queries, alerts and dashboards that filter on the connector names.

Other Changes
  • feat(cloudflare): Deprecate cacheClient option (#​26494)
  • feat(cloudflare): Set server name and runtime version from the wrangler config (#​26427)
  • feat(core): add experimental SDK config integration (#​26291)
  • feat(server-utils): Instrument Google GenAI decisions as gen_ai.decide spans (#​26457)
  • feat(server-utils): Record Vercel AI Gateway cost on AI SDK spans (#​26462)
  • fix(core): Escape JSON.stringify output that goes into generated code (#​26314)
  • fix(core): Keep the longest active rate limit for each category (#​26410)
  • fix(nestjs,sveltekit,nuxt,astro): Report the framework SDK name on all runtimes (#​26302)
  • fix(nuxt): Answer managed tunnel requests on Cloudflare (#​26365)
  • fix(profiling-node): Use safeDateNow for profile envelope timestamps (#​26474)
  • fix(server-utils): Mark Mistral and Workers AI spans as cancelled when the caller aborts (#​26454)
  • fix(server-utils): Support @​google/genai v3 in auto-instrumentation (#​26441)
Internal Changes
  • chore(ci): Route e2e test apps and more packages to SDK subteams in REVIEWERS (#​26415)
  • chore(deps): Bump next from 16.3.3 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16-standalone (#​26433)
  • chore(deps): Bump next from 16.3.8 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16-tunnel (#​26438)
  • chore(deps): Bump next from 16.4.1 to 16.4.5 in /dev-packages/e2e-tests/test-applications/vinext-cf-workers (#​26436)
  • chore(deps): Bump next from 16.4.2 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16 (#​26439)
  • chore(deps): Stop Dependabot security updates for test packages (#​26443)
  • chore: Route reviews to timfish and RulaKhaled (#​26444)
  • ci: Don't count the PR's owners towards its required reviewers (#​26417)
  • ci: Fix the lockfile check, the WebKit launch, and slow unit tests (#​26458)
  • ci: Gate Junior PRs from outside the SDK team on a team or contractor review (#​26413)
  • ci: List job failures outside tests in the weekly flaky report (#​26460)
  • ci: Resolve contractors' Slack names in the Junior requester lookup (#​26463)
  • ci(deps): Bump anthropics/claude-code-action from 1.0.266 to 1.0.276 (#​26450)
  • ci(deps): Bump getsentry/craft from 3.5.0 to 3.12.0 (#​26448)
  • ci(deps): Bump getsentry/github-workflows/validate-pr from 01bcb7f to 6bf4a27 (#​26447)
  • ci(deps): Bump peter-evans/create-pull-request from 8.1.1 to 8.1.3 (#​26449)
  • perf(ci): Run Cloudflare integration tests on six ARM shards (#​26432)
  • perf(ci): Shard Node unit tests across two jobs (#​26466)
  • perf(ci): Split large Node integration test suites (#​26420)
  • test: Give each test run its own port and queue (#​26479)
  • test: Remove wall-clock and flush timing assumptions from unit tests (#​26467)
  • test: Stop slow Docker steps from failing integration and E2E tests (#​26481)
  • test(browser): Fix flaky replay and tracing integration tests (#​26478)
  • test(cloudflare): Accept either order for the two workflow errors in run-errors test (#​26446)
  • test(cloudflare): Fix the invocation-duration flake and report request errors (#​26459)
  • test(e2e): Fix flaky hono, Next.js T3, and React Router tests (#​26482)
  • test(node-integration): Collect traces that arrive in several envelopes (#​26480)
  • test(tanstackstart-react): Add CSRF middleware to the e2e fixtures (#​26451)
  • test(tanstackstart-react): Run the tunnel e2e app on TanStack Start stable (#​26456)

Work in this release was contributed by @​JavierCane. Thank you for your contribution!

expo/expo (expo)

v58.0.26

Compare Source

Patch Changes
i18next/i18next-browser-languageDetector (i18next-browser-languagedetector)

v8.3.1

Compare Source

  • fix: the cookie detector decodes the value it reads, so a language cached with an @ (like sr@latin, stored as sr%40latin) is detected again on the next load instead of being dropped by the language code check. Thanks @​SudeepGowda55 330
  • fix: the querystring and hash detectors decode the value too, so ?lng=sr%40latin (what URLSearchParams and encodeURIComponent write) is detected as sr@latin. A value that is not valid percent-encoding is still skipped.

Configuration

📅 Schedule: (in timezone Europe/Copenhagen)

  • Branch creation
    • "before 6am on monday"
  • 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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@fedify/fedify](https://fedify.dev/) ([source](https://github.com/fedify-dev/fedify/tree/HEAD/packages/fedify)) | [`2.4.5` → `2.4.6`](https://renovatebot.com/diffs/npm/@fedify%2ffedify/2.4.5/2.4.6) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@fedify%2ffedify/2.4.6?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@fedify%2ffedify/2.4.5/2.4.6?slim=true) | | [@garmin/fitsdk](https://github.com/garmin/fit-javascript-sdk) | [`21.221.0` → `21.222.0`](https://renovatebot.com/diffs/npm/@garmin%2ffitsdk/21.221.0/21.222.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@garmin%2ffitsdk/21.222.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@garmin%2ffitsdk/21.221.0/21.222.0?slim=true) | | [@sentry/node](https://github.com/getsentry/sentry-javascript/tree/master/packages/node) ([source](https://github.com/getsentry/sentry-javascript)) | [`11.13.0` → `11.14.0`](https://renovatebot.com/diffs/npm/@sentry%2fnode/11.13.0/11.14.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2fnode/11.14.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2fnode/11.13.0/11.14.0?slim=true) | | [@sentry/react](https://github.com/getsentry/sentry-javascript/tree/master/packages/react) ([source](https://github.com/getsentry/sentry-javascript)) | [`11.13.0` → `11.14.0`](https://renovatebot.com/diffs/npm/@sentry%2freact/11.13.0/11.14.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@sentry%2freact/11.14.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@sentry%2freact/11.13.0/11.14.0?slim=true) | | [expo](https://github.com/expo/expo/tree/main/packages/expo) ([source](https://github.com/expo/expo/tree/HEAD/packages/expo)) | [`58.0.25` → `58.0.26`](https://renovatebot.com/diffs/npm/expo/58.0.25/58.0.26) | ![age](https://developer.mend.io/api/mc/badges/age/npm/expo/58.0.26?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/expo/58.0.25/58.0.26?slim=true) | | [i18next-browser-languagedetector](https://github.com/i18next/i18next-browser-languageDetector) | [`8.3.0` → `8.3.1`](https://renovatebot.com/diffs/npm/i18next-browser-languagedetector/8.3.0/8.3.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/i18next-browser-languagedetector/8.3.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/i18next-browser-languagedetector/8.3.0/8.3.1?slim=true) | --- ### Release Notes <details> <summary>fedify-dev/fedify (@&#8203;fedify/fedify)</summary> ### [`v2.4.6`](https://github.com/fedify-dev/fedify/blob/HEAD/CHANGES.md#Version-246) [Compare Source](https://github.com/fedify-dev/fedify/compare/2.4.5...2.4.6) Released on November 17, 2026. ##### [@&#8203;fedify/fedify](https://github.com/fedify/fedify) - Fixed `Context.sendActivity()` and `InboxContext.forwardActivity()` giving up on the remaining deliveries when one recipient failed. The immediate delivery paths now wait for every delivery they have already started before propagating the error, so the remaining recipients are still reached on runtimes such as Cloudflare Workers, which may terminate an isolate once the error response is returned. This applies both to `immediate: true` and to federations without an outbox queue. \[[#&#8203;1380], [#&#8203;1388]] - Fixed `CryptoKey` and `CryptoKeyPair` values obtained from `node:crypto` being rejected by `ActorKeyPairsDispatcher`, `SharedInboxKeyDispatcher`, `SenderKeyPair`, `signRequest()`, `createProof()`, `signObject()`, `createSignature()`, `signJsonLd()`, `exportJwk()`, and the authenticated document loader APIs when `@types/node` 24.7.0 or later is installed. Those APIs now accept a structural key type that both Node.js and DOM/Web Worker keys satisfy, while the keys returned by Fedify keep the ambient `CryptoKey` types. `SenderKeyPair` and `SharedInboxKeyDispatcher` take a type parameter that defaults to `CryptoKey`, so code that reads a key pair or calls a dispatcher keeps the narrower type. \[[#&#8203;554], [#&#8203;1391]] - Fixed Linked Data Signature verification rejecting documents with unmapped extension properties, such as an undefined `quoteUri`, that the sender's JSON-LD processor discards. Discarded properties are not authenticated by the signature. Outbound signing still rejects lossy input, and verification continues to reject relative IRIs and unsafe graph structures. \[[#&#8203;1405], [#&#8203;1411]] - Fixed Linked Data Signatures being emitted with a JSON-LD context that no longer resolves. The attached `signature` object now uses `https://w3id.org/security/v1` instead of `https://w3id.org/identity/v1`, which redirects to an unreachable host. Documents signed through `signJsonLd()` or `attachSignature()` whose context does not define `signature` now also get a minimal inline definition of that term, so the signed document remains valid JSON-LD. Documents that already carry a `proof` are left unchanged, since a new context definition would invalidate the proof. Activities queued for fanout before the upgrade also keep their original proof-covered JSON when replayed. Incoming signatures that still use `identity/v1` continue to verify. \[[#&#8203;664]] - Fixed automatic queue worker startup failures becoming unhandled promise rejections. When `manuallyStartQueue` was left `false` and a `MessageQueue` implementation could not start listening, such as `WorkersMessageQueue` on Cloudflare Workers whose `listen()` throws a `TypeError`, the rejection from the implicit startup in inbox handling and in `Context.sendActivity()` was discarded. It is now logged as a warning once per `Federation` instance, and a synchronous throw from one queue no longer prevents the remaining queues from starting. The failed worker is not retried, so restart the process after fixing the queue. `Federation.startQueue()` still rejects so callers that start workers deliberately see the error, and Cloudflare Workers deployments should set `manuallyStartQueue: true` to avoid the warning entirely. \[[#&#8203;1381], [#&#8203;1390]] - Fixed inbox handling that treated valid date-times without seconds, such as `2024-01-01T10:00Z` or `2024-01-01T10:00.5Z`, as permanently malformed. Activity Streams 2.0 allows seconds to be omitted, so activities with such date-times are no longer rejected or dropped. Activities whose `Question.closed` is a date-like but impossible value, such as `2024-02-31T10:00.5Z`, are now treated as malformed instead of being accepted with `closed` discarded. \[[#&#8203;1339], [#&#8203;1347] by ChanHaeng Lee] - Fixed incoming Linked Data Signatures without a `created` field being treated as unsigned. Valid `RsaSignature2017` signatures without that field now verify through the JSON-LD APIs and inbox, including queued inbox processing, and are forwarded when `skipIfUnsigned` is enabled. Malformed signature objects now produce a debug log with their property names. Invalid creator URLs now fail verification without throwing an exception. Outgoing signatures still include `created`. \[[#&#8203;1406], [#&#8203;1413]] - Fixed singleton `attachment` values being serialized as objects in actor, object, and collection responses, which caused Mastodon to ignore a single profile field. Served responses and newly generated activity deliveries now preserve attachment arrays when the JSON-LD context permits it. Documents containing existing proofs or Linked Data signatures are left unchanged by the compatibility rewrite. New normalized deliveries are signed over the same JSON used for queueing and transport. \[[#&#8203;1421], [#&#8203;1422], [mastodon/mastodon#41640]] - Fixed the fanout worker never starting when the `fanout` queue was the only configured queue. `Federation.startQueue()` returned without calling `fanoutQueue.listen()`, so fanout messages were enqueued but never consumed; the implicit startup triggered by a fanout enqueue silently did nothing. Both paths now start the fanout worker, and deployments that configure only `queue: { fanout: ... }` no longer need to add an unused `inbox` or `outbox` queue to make fanout delivery work. \[[#&#8203;1389], [#&#8203;1392]] - Limited WebFinger lookups made through federation contexts to 10 seconds per lookup. \[[GHSA-9pmv-w936-hj3f]] - Limited each outgoing activity delivery attempt to 30 seconds, including redirects and HTTP signature retries, so a slow remote inbox cannot hold a delivery worker indefinitely. Timed-out attempts follow the configured retry schedule. \[[GHSA-fq5h-gjhp-g75x]] - NodeInfo lookups now stop following a redirect when its target repeats an earlier URL in the same chain. A self-redirect previously opened five fetch sessions before hitting the redirect limit; it now stops after the first response. The existing redirect limit still applies to chains without cycles. \[[GHSA-64hq-2hgr-q4pm]] - NodeInfo lookups now time out after 10 seconds by default. A remote server could previously keep `getNodeInfo()` or `Context.lookupNodeInfo()` waiting indefinitely by delaying a response. The limit covers discovery, redirects, and the document body as one operation. Pass a `timeout` value in milliseconds to allow more time, or `null` to disable the limit; a timed-out lookup returns `undefined`. An optional `signal` can cancel the lookup, even with `timeout: null`. \[[GHSA-64hq-2hgr-q4pm]] - On Node.js, NodeInfo hostname resolution now starts at most two operating system DNS lookups at a time. Other hosts can still resolve when one resolver call stalls. A queued lookup can time out or be cancelled before starting, so repeated abandoned NodeInfo requests cannot fill the shared libuv thread pool. An already-running operating system lookup cannot be cancelled. \[[GHSA-64hq-2hgr-q4pm]] - Fixed `signObject()` and the default activity transformers, `autoIdAssigner()` and `actorDehydrator()`, dropping the default [FEP-ef61] portable object verifier of the object they returned a copy of. Their results now keep the verifier, so their accessors verify portable objects as the original object's accessors do, and they no longer log the warning that `clone()` logs when it drops the verifier. \[[#&#8203;1399], [#&#8203;1442]] [mastodon/mastodon#41640]: https://github.com/mastodon/mastodon/issues/41640 [GHSA-9pmv-w936-hj3f]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-9pmv-w936-hj3f [GHSA-fq5h-gjhp-g75x]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-fq5h-gjhp-g75x [GHSA-64hq-2hgr-q4pm]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-64hq-2hgr-q4pm [FEP-ef61]: https://w3id.org/fep/ef61 [#&#8203;554]: https://github.com/fedify-dev/fedify/issues/554 [#&#8203;664]: https://github.com/fedify-dev/fedify/issues/664 [#&#8203;1339]: https://github.com/fedify-dev/fedify/issues/1339 [#&#8203;1347]: https://github.com/fedify-dev/fedify/pull/1347 [#&#8203;1380]: https://github.com/fedify-dev/fedify/issues/1380 [#&#8203;1381]: https://github.com/fedify-dev/fedify/issues/1381 [#&#8203;1388]: https://github.com/fedify-dev/fedify/pull/1388 [#&#8203;1389]: https://github.com/fedify-dev/fedify/issues/1389 [#&#8203;1390]: https://github.com/fedify-dev/fedify/pull/1390 [#&#8203;1391]: https://github.com/fedify-dev/fedify/pull/1391 [#&#8203;1392]: https://github.com/fedify-dev/fedify/pull/1392 [#&#8203;1399]: https://github.com/fedify-dev/fedify/issues/1399 [#&#8203;1405]: https://github.com/fedify-dev/fedify/issues/1405 [#&#8203;1406]: https://github.com/fedify-dev/fedify/issues/1406 [#&#8203;1411]: https://github.com/fedify-dev/fedify/pull/1411 [#&#8203;1413]: https://github.com/fedify-dev/fedify/pull/1413 [#&#8203;1421]: https://github.com/fedify-dev/fedify/issues/1421 [#&#8203;1422]: https://github.com/fedify-dev/fedify/pull/1422 [#&#8203;1442]: https://github.com/fedify-dev/fedify/pull/1442 ##### [@&#8203;fedify/backfill](https://github.com/fedify/backfill) - Fixed backfill accepting `documentLoader` results with spoofed origins. Results whose declared ID origin differs from the requested IRI's origin are now ignored, including otherwise valid cross-origin redirects. Custom loaders must still validate IDs against the final response URL: pass custom JSON-LD loaders through `lookupObject()` and set `documentUrl` to the final response URL after redirects. \[[GHSA-h3jv-px69-2gpj]] - Fixed backfill trusting cross-origin embedded objects, which allowed a remote document to spoof content from another origin. Backfill now dereferences these objects by their IDs before yielding them. It also ignores a `documentLoader` result whose ID has a different origin from the requested IRI. Consequently, objects reached through a cross-origin redirect are ignored. Custom loaders should pass their JSON-LD loader to `lookupObject()` so it can validate the object's ID against the final response URL. Backfilled objects remain unverified remote data and should be authenticated before they are persisted or otherwise trusted. \[[GHSA-x58x-xx7h-7rh4]] [GHSA-h3jv-px69-2gpj]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-h3jv-px69-2gpj [GHSA-x58x-xx7h-7rh4]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-x58x-xx7h-7rh4 ##### [@&#8203;fedify/cli](https://github.com/fedify/cli) - The `fedify nodeinfo` command now accepts `-T`/`--timeout` in seconds. It defaults to 10 seconds and reports a timeout separately from a missing or invalid NodeInfo document. \[[GHSA-64hq-2hgr-q4pm]] ##### [@&#8203;fedify/nestjs](https://github.com/fedify/nestjs) - Fixed `require("@fedify/nestjs")` failing with `MODULE_NOT_FOUND`, which broke the integration in NestJS projects compiled to CommonJS, the NestJS default. The package manifest pointed its CommonJS entry point and type declarations at files that the build no longer produced; they now point to the files that are actually shipped, so the integration loads with `require()` again and TypeScript finds its declarations. ESM imports were not affected. \[[#&#8203;1424], [#&#8203;1428]] [#&#8203;1424]: https://github.com/fedify-dev/fedify/issues/1424 [#&#8203;1428]: https://github.com/fedify-dev/fedify/pull/1428 ##### [@&#8203;fedify/next](https://github.com/fedify/next) - Fixed `fedifyWith()` not forwarding NodeInfo document requests such as `GET /nodeinfo/2.1` without federation media types in their headers. `isNodeInfoRequest()` and `isFederationRequest()` now recognize paths under `/nodeinfo/` regardless of their headers, so clients using `Accept: application/json`, `*/*`, or no `Accept` header can reach the dispatcher. Existing applications must also add `{ source: "/nodeinfo/:path*" }` to the `matcher` in their *middleware.ts* or *proxy.ts*. Dispatchers outside `/nodeinfo/` still require explicit delegation to `integrateFederation()` and a matching `matcher` entry. \[[#&#8203;1402], [#&#8203;1412]] [#&#8203;1402]: https://github.com/fedify-dev/fedify/issues/1402 [#&#8203;1412]: https://github.com/fedify-dev/fedify/pull/1412 ##### [@&#8203;fedify/testing](https://github.com/fedify/testing) - Fixed `MockFederation.receiveActivity()` dropping the default [FEP-ef61] portable object verifier of the received activity when it attaches its document loaders to the activity passed to inbox listeners. \[[#&#8203;1399], [#&#8203;1442]] ##### [@&#8203;fedify/vocab](https://github.com/fedify/vocab) - Added a warning when `clone()` drops the default [FEP-ef61] portable object verifier of a vocabulary object, and documented that `clone()` does not inherit it. Objects that Fedify parses for you, such as activities that inboxes receive and the results of `Context.lookupObject()`, have `Context.verifyPortableObject` as their default, so an existing application that clones them now logs a warning in the `["fedify", "vocab", "portable"]` category. A clone without a verifier does not verify the portable objects embedded in it, and refuses to dereference portable references. Pass `verifyPortableObject: ctx.verifyPortableObject` to `clone()` to keep verifying them, or `verifyPortableObject: undefined` to drop the verifier deliberately without the warning. The `verifyPortableObject` option of `clone()` now explicitly accepts `undefined`, so that the opt-out also type-checks with `exactOptionalPropertyTypes`. \[[#&#8203;1399], [#&#8203;1442]] - Fixed `CryptographicKey` and `Multikey` rejecting a `publicKey` obtained from `node:crypto` in their constructors and `clone()` when `@types/node` 24.7.0 or later is installed. The property accepts a structural key type now, while the getters still return the ambient `CryptoKey` type. \[[#&#8203;554], [#&#8203;1391]] - Fixed an origin-check bypass that allowed crafted JSON-LD without a parent `id` to return forged embedded objects claiming another origin. \[[GHSA-r388-57j3-5fgp]] - Fixed invalid JSON-LD when a collection page embeds a parsed item whose context redefines a protected parent term, such as `proof`. Default serialization now isolates independent child contexts while preserving their cached documents and extension meanings. The parent's `@context` array gains property-scoped definitions, including for generated children with matching contexts; context-aware consumers need JSON-LD 1.1 support. Resolving the parent context uses `contextLoader`; URL references alongside isolated children are represented as objects with `id` and their own context. \[[#&#8203;1394], [#&#8203;1397]] - Fixed parsing of date-times without seconds, such as `2024-01-01T10:00Z`, `2024-01-01T10:00+09:00`, or `2024-01-01T10:00.5Z`, which Activity Streams 2.0 allows. They raised a `RangeError`, or were ignored in `Question.closed` when they had a fraction. Date-like but impossible values in `Question.closed`, such as `2024-02-31T10:00.5Z`, now raise a `RangeError` instead of being silently dropped. \[[#&#8203;1339], [#&#8203;1347] by ChanHaeng Lee] - Limited WebFinger lookups used by object resolution to 10 seconds each, and actor handle resolution to one 10-second deadline across alias checks. Actor handle resolution now checks at most 100 subject/alias candidates and skips duplicates. \[[GHSA-9pmv-w936-hj3f]] - Replaced <https://w3id.org/identity/v1> with <https://w3id.org/security/v1> in the default JSON-LD contexts of activity types. The former no longer resolves, and <https://w3id.org/security/v1> defines the same terms the signatures use. \[[#&#8203;664], [#&#8203;1351]] [GHSA-r388-57j3-5fgp]: https://github.com/fedify-dev/fedify/security/advisories/GHSA-r388-57j3-5fgp [#&#8203;1351]: https://github.com/fedify-dev/fedify/pull/1351 [#&#8203;1394]: https://github.com/fedify-dev/fedify/issues/1394 [#&#8203;1397]: https://github.com/fedify-dev/fedify/pull/1397 ##### [@&#8203;fedify/vocab-runtime](https://github.com/fedify/vocab-runtime) - Added `normalizeDateTimeLiteral()` to `@fedify/vocab-runtime/temporal` so that generated vocabulary code and `@fedify/fedify` interpret `xsd:dateTime` literals the same way. It treats a literal without a UTC offset as UTC and handles literals without seconds, including those with a fraction. \[[#&#8203;1339], [#&#8203;1347] by ChanHaeng Lee] - Added the `CryptoKeyLike` and `CryptoKeyPairLike` types for the structural key shape that Fedify APIs accept. They cover keys from Node.js, DOM/Web Workers, and Cloudflare Workers, so `exportSpki()`, `exportMultibaseKey()`, and `getAuthenticatedDocumentLoader()` no longer reject keys obtained from `node:crypto` with `@types/node` 24.7.0 or later. `AuthenticatedDocumentLoaderFactory` keeps the ambient `CryptoKey` type on the identity it receives, so existing implementations do not have to change. \[[#&#8203;554], [#&#8203;1391]] ##### [@&#8203;fedify/vocab-tools](https://github.com/fedify/vocab-tools) - Changed the code generated by `@fedify/vocab-tools` to import the `CryptoKeyLike` type from `@fedify/vocab-runtime`. Regenerated code now requires `@fedify/vocab-runtime` 2.4.6 or later. \[[#&#8203;554], [#&#8203;1391]] - Fixed generated accessors bypassing origin checks for embedded objects when the parent has no `id`. Regenerate your vocabulary code to apply the fix. \[[GHSA-r388-57j3-5fgp]] - Fixed generated default encoders combining independent child documents with conflicting inherited JSON-LD contexts. Child documents retain their original contexts and extension meanings, including in collections and inherited properties. Generated parents gain property-scoped definitions in their `@context` arrays even when child and parent contexts match. Regenerate your vocabulary code to apply the fix. \[[#&#8203;1394], [#&#8203;1397]] - Fixed generated `xsd:dateTime` decoders failing on date-times without seconds, such as `2024-01-01T10:00Z` or `2024-01-01T10:00.5Z`. Regenerate your vocabulary code to get the fix. Generated code now imports `normalizeDateTimeLiteral()` from `@fedify/vocab-runtime/temporal`. \[[#&#8203;1339], [#&#8203;1347] by ChanHaeng Lee] - Generated `clone()` methods now log a warning in the `["fedify", "vocab", "portable"]` category when they drop the default [FEP-ef61] portable object verifier of the source object, i.e., when the source has one and the call does not pass the `verifyPortableObject` option. An explicit `verifyPortableObject: undefined` drops it without the warning. Their API documentation now states that `clone()` does not inherit the default verifier. Regenerate custom vocabularies to get the warning. \[[#&#8203;1399], [#&#8203;1442]] ##### [@&#8203;fedify/webfinger](https://github.com/fedify/webfinger) - Limited WebFinger lookups to 10 seconds across DNS resolution, redirects, and response reading. A caller's abort signal can end a lookup sooner. This prevents slow endpoints from occupying lookup workers indefinitely. \[[GHSA-9pmv-w936-hj3f]] </details> <details> <summary>garmin/fit-javascript-sdk (@&#8203;garmin/fitsdk)</summary> ### [`v21.222.0`](https://github.com/garmin/fit-javascript-sdk/releases/tag/21.222.0) [Compare Source](https://github.com/garmin/fit-javascript-sdk/compare/21.221.0...21.222.0) See release notes for full list of changes <https://forums.garmin.com/developer/fit-sdk/b/news-announcements> </details> <details> <summary>getsentry/sentry-javascript (@&#8203;sentry/node)</summary> ### [`v11.14.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#11140) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/11.13.0...11.14.0) ##### Important Changes - **feat(browser): Add `browserTracingCoreIntegration` and standalone tracing integrations ([#&#8203;26259](https://github.com/getsentry/sentry-javascript/pull/26259), [#&#8203;26260](https://github.com/getsentry/sentry-javascript/pull/26260), [#&#8203;26261](https://github.com/getsentry/sentry-javascript/pull/26261), [#&#8203;26262](https://github.com/getsentry/sentry-javascript/pull/26262), [#&#8203;26273](https://github.com/getsentry/sentry-javascript/pull/26273), [#&#8203;26276](https://github.com/getsentry/sentry-javascript/pull/26276), [#&#8203;26497](https://github.com/getsentry/sentry-javascript/pull/26497))** `browserTracingIntegration` now sets up fetch and XHR request spans, linked traces, long tasks and resource spans through the standalone `fetchTracingIntegration`, `xhrTracingIntegration`, `linkedTracesIntegration`, `longTasksIntegration` and `resourcesIntegration`. Its behavior is unchanged. To ship less code, use `browserTracingCoreIntegration`, which keeps pageload and navigation spans, and add only the standalone integrations you need. The CDN bundles export them too. - **ref(server-utils): Share one cron converter across cron integrations ([#&#8203;25918](https://github.com/getsentry/sentry-javascript/pull/25918))** `Sentry.cron.instrumentCron`, `instrumentNodeCron` and `instrumentNodeSchedule` send the server's time zone when a job has none, so monitors don't report false misses on servers that aren't on UTC. Schedules Sentry can't express exactly, such as per-second schedules, send no monitor config, so the monitor keeps the schedule set in Sentry. `Sentry.cron.instrumentNodeCron` is deprecated; use `nodeCronIntegration` instead. - **fix(nuxt): Name the database system in `db.system.name` of db0 spans ([#&#8203;26285](https://github.com/getsentry/sentry-javascript/pull/26285))** Nitro database (db0) spans now set `db.system.name` to the database system of the connector's dialect (`mysql`, `postgresql`, `sqlite` or `libsql`), as the OpenTelemetry conventions define it, instead of the connector name. For example, spans of the `mysql2` and `planetscale` connectors now report `mysql`, and spans of `better-sqlite3` and `cloudflare-d1` now report `sqlite`. Update saved queries, alerts and dashboards that filter on the connector names. ##### Other Changes - feat(cloudflare): Deprecate `cacheClient` option ([#&#8203;26494](https://github.com/getsentry/sentry-javascript/pull/26494)) - feat(cloudflare): Set server name and runtime version from the wrangler config ([#&#8203;26427](https://github.com/getsentry/sentry-javascript/pull/26427)) - feat(core): add experimental SDK config integration ([#&#8203;26291](https://github.com/getsentry/sentry-javascript/pull/26291)) - feat(server-utils): Instrument Google GenAI decisions as gen\_ai.decide spans ([#&#8203;26457](https://github.com/getsentry/sentry-javascript/pull/26457)) - feat(server-utils): Record Vercel AI Gateway cost on AI SDK spans ([#&#8203;26462](https://github.com/getsentry/sentry-javascript/pull/26462)) - fix(core): Escape `JSON.stringify` output that goes into generated code ([#&#8203;26314](https://github.com/getsentry/sentry-javascript/pull/26314)) - fix(core): Keep the longest active rate limit for each category ([#&#8203;26410](https://github.com/getsentry/sentry-javascript/pull/26410)) - fix(nestjs,sveltekit,nuxt,astro): Report the framework SDK name on all runtimes ([#&#8203;26302](https://github.com/getsentry/sentry-javascript/pull/26302)) - fix(nuxt): Answer managed tunnel requests on Cloudflare ([#&#8203;26365](https://github.com/getsentry/sentry-javascript/pull/26365)) - fix(profiling-node): Use safeDateNow for profile envelope timestamps ([#&#8203;26474](https://github.com/getsentry/sentry-javascript/pull/26474)) - fix(server-utils): Mark Mistral and Workers AI spans as cancelled when the caller aborts ([#&#8203;26454](https://github.com/getsentry/sentry-javascript/pull/26454)) - fix(server-utils): Support [@&#8203;google/genai](https://github.com/google/genai) v3 in auto-instrumentation ([#&#8203;26441](https://github.com/getsentry/sentry-javascript/pull/26441)) <details> <summary><strong>Internal Changes</strong></summary> - chore(ci): Route e2e test apps and more packages to SDK subteams in REVIEWERS ([#&#8203;26415](https://github.com/getsentry/sentry-javascript/pull/26415)) - chore(deps): Bump next from 16.3.3 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16-standalone ([#&#8203;26433](https://github.com/getsentry/sentry-javascript/pull/26433)) - chore(deps): Bump next from 16.3.8 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16-tunnel ([#&#8203;26438](https://github.com/getsentry/sentry-javascript/pull/26438)) - chore(deps): Bump next from 16.4.1 to 16.4.5 in /dev-packages/e2e-tests/test-applications/vinext-cf-workers ([#&#8203;26436](https://github.com/getsentry/sentry-javascript/pull/26436)) - chore(deps): Bump next from 16.4.2 to 16.4.5 in /dev-packages/e2e-tests/test-applications/nextjs-16 ([#&#8203;26439](https://github.com/getsentry/sentry-javascript/pull/26439)) - chore(deps): Stop Dependabot security updates for test packages ([#&#8203;26443](https://github.com/getsentry/sentry-javascript/pull/26443)) - chore: Route reviews to timfish and RulaKhaled ([#&#8203;26444](https://github.com/getsentry/sentry-javascript/pull/26444)) - ci: Don't count the PR's owners towards its required reviewers ([#&#8203;26417](https://github.com/getsentry/sentry-javascript/pull/26417)) - ci: Fix the lockfile check, the WebKit launch, and slow unit tests ([#&#8203;26458](https://github.com/getsentry/sentry-javascript/pull/26458)) - ci: Gate Junior PRs from outside the SDK team on a team or contractor review ([#&#8203;26413](https://github.com/getsentry/sentry-javascript/pull/26413)) - ci: List job failures outside tests in the weekly flaky report ([#&#8203;26460](https://github.com/getsentry/sentry-javascript/pull/26460)) - ci: Resolve contractors' Slack names in the Junior requester lookup ([#&#8203;26463](https://github.com/getsentry/sentry-javascript/pull/26463)) - ci(deps): Bump anthropics/claude-code-action from 1.0.266 to 1.0.276 ([#&#8203;26450](https://github.com/getsentry/sentry-javascript/pull/26450)) - ci(deps): Bump getsentry/craft from 3.5.0 to 3.12.0 ([#&#8203;26448](https://github.com/getsentry/sentry-javascript/pull/26448)) - ci(deps): Bump getsentry/github-workflows/validate-pr from [`01bcb7f`](https://github.com/getsentry/sentry-javascript/commit/01bcb7fe69bb48bacd83e675840e3dc95b33c730) to [`6bf4a27`](https://github.com/getsentry/sentry-javascript/commit/6bf4a27612e388f9c113d64f75e25190e814b414) ([#&#8203;26447](https://github.com/getsentry/sentry-javascript/pull/26447)) - ci(deps): Bump peter-evans/create-pull-request from 8.1.1 to 8.1.3 ([#&#8203;26449](https://github.com/getsentry/sentry-javascript/pull/26449)) - perf(ci): Run Cloudflare integration tests on six ARM shards ([#&#8203;26432](https://github.com/getsentry/sentry-javascript/pull/26432)) - perf(ci): Shard Node unit tests across two jobs ([#&#8203;26466](https://github.com/getsentry/sentry-javascript/pull/26466)) - perf(ci): Split large Node integration test suites ([#&#8203;26420](https://github.com/getsentry/sentry-javascript/pull/26420)) - test: Give each test run its own port and queue ([#&#8203;26479](https://github.com/getsentry/sentry-javascript/pull/26479)) - test: Remove wall-clock and flush timing assumptions from unit tests ([#&#8203;26467](https://github.com/getsentry/sentry-javascript/pull/26467)) - test: Stop slow Docker steps from failing integration and E2E tests ([#&#8203;26481](https://github.com/getsentry/sentry-javascript/pull/26481)) - test(browser): Fix flaky replay and tracing integration tests ([#&#8203;26478](https://github.com/getsentry/sentry-javascript/pull/26478)) - test(cloudflare): Accept either order for the two workflow errors in run-errors test ([#&#8203;26446](https://github.com/getsentry/sentry-javascript/pull/26446)) - test(cloudflare): Fix the invocation-duration flake and report request errors ([#&#8203;26459](https://github.com/getsentry/sentry-javascript/pull/26459)) - test(e2e): Fix flaky hono, Next.js T3, and React Router tests ([#&#8203;26482](https://github.com/getsentry/sentry-javascript/pull/26482)) - test(node-integration): Collect traces that arrive in several envelopes ([#&#8203;26480](https://github.com/getsentry/sentry-javascript/pull/26480)) - test(tanstackstart-react): Add CSRF middleware to the e2e fixtures ([#&#8203;26451](https://github.com/getsentry/sentry-javascript/pull/26451)) - test(tanstackstart-react): Run the tunnel e2e app on TanStack Start stable ([#&#8203;26456](https://github.com/getsentry/sentry-javascript/pull/26456)) </details> Work in this release was contributed by [@&#8203;JavierCane](https://github.com/JavierCane). Thank you for your contribution! </details> <details> <summary>expo/expo (expo)</summary> ### [`v58.0.26`](https://github.com/expo/expo/releases/tag/expo%4058.0.26) [Compare Source](https://github.com/expo/expo/compare/expo@58.0.25...expo@58.0.26) ##### Patch Changes - \[iOS] Connect to the development server's `/message` socket and network inspector on port 443 when the bundle URL is `https` with no port, such as an `expo start --tunnel` URL. ([#&#8203;53466](https://github.com/expo/expo/pull/53466) by [@&#8203;vonovak](https://github.com/vonovak)) - Updated dependencies. ([#&#8203;53385](https://github.com/expo/expo/pull/53385), [#&#8203;53384](https://github.com/expo/expo/pull/53384), [#&#8203;53235](https://github.com/expo/expo/pull/53235), [#&#8203;53565](https://github.com/expo/expo/pull/53565), [#&#8203;53054](https://github.com/expo/expo/pull/53054), [#&#8203;53052](https://github.com/expo/expo/pull/53052), [#&#8203;53274](https://github.com/expo/expo/pull/53274), [#&#8203;53578](https://github.com/expo/expo/pull/53578)) - expo-file-system\@&#8203;58.0.14 - [@&#8203;expo/cli](https://github.com/expo/cli)@58.1.21 - [@&#8203;expo/metro-config](https://github.com/expo/metro-config)@58.0.23 - babel-preset-expo\@&#8203;58.0.26 </details> <details> <summary>i18next/i18next-browser-languageDetector (i18next-browser-languagedetector)</summary> ### [`v8.3.1`](https://github.com/i18next/i18next-browser-languageDetector/blob/HEAD/CHANGELOG.md#831) [Compare Source](https://github.com/i18next/i18next-browser-languageDetector/compare/v8.3.0...v8.3.1) - fix: the cookie detector decodes the value it reads, so a language cached with an `@` (like `sr@latin`, stored as `sr%40latin`) is detected again on the next load instead of being dropped by the language code check. Thanks [@&#8203;SudeepGowda55](https://github.com/SudeepGowda55) [330](https://github.com/i18next/i18next-browser-languageDetector/pull/330) - fix: the `querystring` and `hash` detectors decode the value too, so `?lng=sr%40latin` (what `URLSearchParams` and `encodeURIComponent` write) is detected as `sr@latin`. A value that is not valid percent-encoding is still skipped. </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Copenhagen) - Branch creation - "before 6am on monday" - 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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [x] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMzIuNSIsInVwZGF0ZWRJblZlciI6IjQ0LjEzMi41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
chore(deps): Update production (non-major)
Some checks are pending
CD Staging / Build & Push journal Image (pull_request) Has been skipped
CD Staging / Build & Push planner Image (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CD Staging / Tear Down PR Preview (pull_request) Has been skipped
renovate/stability-days Updates have not met minimum release age requirement
CI / Security Scan (pull_request) Successful in 10s
CI / Dockerfile Package Check (pull_request) Successful in 10s
CI / Visual Tests (pull_request) Successful in 43s
CI / Checks (pull_request) Successful in 2m25s
CI / Journal Image Smoke Test (pull_request) Successful in 2m48s
CI / E2E Tests (pull_request) Successful in 4m31s
9241b2a1ae
Author
Collaborator

⚠️ Rebase not applied

This branch has not been rebased, as its update has not yet met the internal checks configured for it, such as minimumReleaseAge. Rebasing it now would add a dependency version which is still within its configured observation period.

Renovate will rebase this branch once its update has met those checks.

### ⚠️ Rebase not applied This branch has not been rebased, as its update has not yet met the internal checks configured for it, such as `minimumReleaseAge`. Rebasing it now would add a dependency version which is still within its configured observation period. Renovate will rebase this branch once its update has met those checks.
Some checks are pending
CD Staging / Build & Push journal Image (pull_request) Has been skipped
CD Staging / Build & Push planner Image (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CD Staging / Tear Down PR Preview (pull_request) Has been skipped
renovate/stability-days Updates have not met minimum release age requirement
CI / Security Scan (pull_request) Successful in 10s
Required
Details
CI / Dockerfile Package Check (pull_request) Successful in 10s
Required
Details
CI / Visual Tests (pull_request) Successful in 43s
Required
Details
CI / Checks (pull_request) Successful in 2m25s
Required
Details
CI / Journal Image Smoke Test (pull_request) Successful in 2m48s
Required
Details
CI / E2E Tests (pull_request) Successful in 4m31s
Required
Details
This pull request has changes conflicting with the target branch.
  • pnpm-lock.yaml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/production-(non-major):renovate/production-(non-major)
git switch renovate/production-(non-major)
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
trails-cool/trails!358
No description provided.