chore(deps): Update production (non-major) #358
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!358
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/production-(non-major)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.4.5→2.4.621.221.0→21.222.011.13.0→11.14.011.13.0→11.14.058.0.25→58.0.268.3.0→8.3.1Release Notes
fedify-dev/fedify (@fedify/fedify)
v2.4.6Compare Source
Released on November 17, 2026.
@fedify/fedify
Context.sendActivity()andInboxContext.forwardActivity()givingup 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: trueandto federations without an outbox queue.
[#1380, #1388]
CryptoKeyandCryptoKeyPairvalues obtained fromnode:cryptobeing rejected by
ActorKeyPairsDispatcher,SharedInboxKeyDispatcher,SenderKeyPair,signRequest(),createProof(),signObject(),createSignature(),signJsonLd(),exportJwk(), and the authenticateddocument loader APIs when
@types/node24.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
CryptoKeytypes.SenderKeyPairandSharedInboxKeyDispatchertake a type parameter that defaults toCryptoKey, so code that reads a key pair or calls a dispatcher keeps thenarrower type.
[#554, #1391]
extension properties, such as an undefined
quoteUri, that the sender'sJSON-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]
longer resolves. The attached
signatureobject now useshttps://w3id.org/security/v1instead ofhttps://w3id.org/identity/v1, which redirects to an unreachable host.Documents signed through
signJsonLd()orattachSignature()whosecontext does not define
signaturenow also get a minimal inlinedefinition of that term, so the signed document remains valid JSON-LD.
Documents that already carry a
proofare left unchanged, since a newcontext 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/v1continue toverify. [#664]
rejections. When
manuallyStartQueuewas leftfalseand aMessageQueueimplementation could not start listening, such as
WorkersMessageQueueonCloudflare Workers whose
listen()throws aTypeError, the rejection fromthe implicit startup in inbox handling and in
Context.sendActivity()wasdiscarded. It is now logged as a warning once per
Federationinstance,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 socallers that start workers deliberately see the error, and Cloudflare
Workers deployments should set
manuallyStartQueue: trueto avoid thewarning entirely.
[#1381, #1390]
as
2024-01-01T10:00Zor2024-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.closedis a date-like but impossible value, such as2024-02-31T10:00.5Z, are now treated as malformed instead of beingaccepted with
closeddiscarded.[#1339, #1347 by ChanHaeng Lee]
createdfield beingtreated as unsigned. Valid
RsaSignature2017signatures without that fieldnow verify through the JSON-LD APIs and inbox, including queued inbox
processing, and are forwarded when
skipIfUnsignedis 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]
attachmentvalues 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]
fanoutqueue was the onlyconfigured queue.
Federation.startQueue()returned without callingfanoutQueue.listen(), so fanout messages were enqueued but neverconsumed; 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 unusedinboxoroutboxqueue to make fanout delivery work.[#1389, #1392]
per lookup. [GHSA-9pmv-w936-hj3f]
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]
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]
could previously keep
getNodeInfo()orContext.lookupNodeInfo()waitingindefinitely by delaying a response. The limit covers discovery,
redirects, and the document body as one operation. Pass a
timeoutvaluein milliseconds to allow more time, or
nullto disable the limit; atimed-out lookup returns
undefined.An optional
signalcan cancel the lookup, even withtimeout: null.[GHSA-64hq-2hgr-q4pm]
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]
signObject()and the default activity transformers,autoIdAssigner()andactorDehydrator(), dropping the default FEP-ef61portable 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
documentLoaderresults 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 setdocumentUrlto the final response URL after redirects.
[GHSA-h3jv-px69-2gpj]
remote document to spoof content from another origin. Backfill now
dereferences these objects by their IDs before yielding them. It also
ignores a
documentLoaderresult whose ID has a different origin from therequested 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 finalresponse URL. Backfilled objects remain unverified remote data and should
be authenticated before they are persisted or otherwise trusted.
[GHSA-x58x-xx7h-7rh4]
@fedify/cli
fedify nodeinfocommand now accepts-T/--timeoutin seconds.It defaults to 10 seconds and reports a timeout separately from a missing
or invalid NodeInfo document.
[GHSA-64hq-2hgr-q4pm]
@fedify/nestjs
require("@fedify/nestjs")failing withMODULE_NOT_FOUND, whichbroke 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 werenot affected.
[#1424, #1428]
@fedify/next
fedifyWith()not forwarding NodeInfo document requests such asGET /nodeinfo/2.1without federation media types in their headers.isNodeInfoRequest()andisFederationRequest()now recognize paths under/nodeinfo/regardless of their headers, so clients usingAccept: application/json,*/*, or noAcceptheader can reach thedispatcher. Existing applications must also add
{ source: "/nodeinfo/:path*" }to thematcherin their middleware.tsor proxy.ts. Dispatchers outside
/nodeinfo/still require explicitdelegation to
integrateFederation()and a matchingmatcherentry.[#1402, #1412]
@fedify/testing
MockFederation.receiveActivity()dropping the default FEP-ef61portable object verifier of the received activity when it attaches its
document loaders to the activity passed to inbox listeners.
[#1399, #1442]
@fedify/vocab
clone()drops the default FEP-ef61 portable objectverifier of a vocabulary object, and documented that
clone()does notinherit it. Objects that Fedify parses for you, such as activities that
inboxes receive and the results of
Context.lookupObject(), haveContext.verifyPortableObjectas their default, so an existingapplication that clones them now logs a warning in the
["fedify", "vocab", "portable"]category. A clone without a verifierdoes not verify the portable objects embedded in it, and refuses to
dereference portable references. Pass
verifyPortableObject: ctx.verifyPortableObjecttoclone()to keepverifying them, or
verifyPortableObject: undefinedto drop the verifierdeliberately without the warning. The
verifyPortableObjectoption ofclone()now explicitly acceptsundefined, so that the opt-out alsotype-checks with
exactOptionalPropertyTypes. [#1399, #1442]CryptographicKeyandMultikeyrejecting apublicKeyobtainedfrom
node:cryptoin their constructors andclone()when@types/node24.7.0 or later is installed. The property accepts a structural key type
now, while the getters still return the ambient
CryptoKeytype.[#554, #1391]
idto return forged embedded objects claiming another origin.[GHSA-r388-57j3-5fgp]
context redefines a protected parent term, such as
proof. Defaultserialization now isolates independent child contexts while preserving
their cached documents and extension meanings. The parent's
@contextarray 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 alongsideisolated children are represented as objects with
idand their owncontext.
[#1394, #1397]
2024-01-01T10:00Z,2024-01-01T10:00+09:00, or2024-01-01T10:00.5Z, which Activity Streams2.0 allows. They raised a
RangeError, or were ignored inQuestion.closedwhen they had a fraction. Date-like but impossiblevalues in
Question.closed, such as2024-02-31T10:00.5Z, now raise aRangeErrorinstead of being silently dropped.[#1339, #1347 by ChanHaeng Lee]
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]
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
normalizeDateTimeLiteral()to@fedify/vocab-runtime/temporalsothat generated vocabulary code and
@fedify/fedifyinterpretxsd:dateTimeliterals 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]
CryptoKeyLikeandCryptoKeyPairLiketypes for the structuralkey shape that Fedify APIs accept. They cover keys from Node.js,
DOM/Web Workers, and Cloudflare Workers, so
exportSpki(),exportMultibaseKey(), andgetAuthenticatedDocumentLoader()no longerreject keys obtained from
node:cryptowith@types/node24.7.0 or later.AuthenticatedDocumentLoaderFactorykeeps the ambientCryptoKeytype onthe identity it receives, so existing implementations do not have to
change.
[#554, #1391]
@fedify/vocab-tools
@fedify/vocab-toolsto import theCryptoKeyLiketype from@fedify/vocab-runtime. Regenerated code nowrequires
@fedify/vocab-runtime2.4.6 or later.[#554, #1391]
the parent has no
id. Regenerate your vocabulary code to apply the fix.[GHSA-r388-57j3-5fgp]
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
@contextarrays even when child and parent contexts match.Regenerate your vocabulary code to apply the fix.
[#1394, #1397]
xsd:dateTimedecoders failing on date-times withoutseconds, such as
2024-01-01T10:00Zor2024-01-01T10:00.5Z. Regenerateyour vocabulary code to get the fix. Generated code now imports
normalizeDateTimeLiteral()from@fedify/vocab-runtime/temporal.[#1339, #1347 by ChanHaeng Lee]
clone()methods now log a warning in the["fedify", "vocab", "portable"]category when they drop the defaultFEP-ef61 portable object verifier of the source object, i.e., when the
source has one and the call does not pass the
verifyPortableObjectoption. An explicit
verifyPortableObject: undefineddrops it withoutthe warning. Their API documentation now states that
clone()does notinherit the default verifier. Regenerate custom vocabularies to get
the warning. [#1399, #1442]
@fedify/webfinger
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.0Compare 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.0Compare Source
Important Changes
feat(browser): Add
browserTracingCoreIntegrationand standalone tracing integrations (#26259, #26260, #26261, #26262, #26273, #26276, #26497)browserTracingIntegrationnow sets up fetch and XHR request spans, linked traces, long tasks and resource spans through the standalonefetchTracingIntegration,xhrTracingIntegration,linkedTracesIntegration,longTasksIntegrationandresourcesIntegration. Its behavior is unchanged. To ship less code, usebrowserTracingCoreIntegration, 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,instrumentNodeCronandinstrumentNodeSchedulesend 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.instrumentNodeCronis deprecated; usenodeCronIntegrationinstead.fix(nuxt): Name the database system in
db.system.nameof db0 spans (#26285)Nitro database (db0) spans now set
db.system.nameto the database system of the connector's dialect (mysql,postgresql,sqliteorlibsql), as the OpenTelemetry conventions define it, instead of the connector name. For example, spans of themysql2andplanetscaleconnectors now reportmysql, and spans ofbetter-sqlite3andcloudflare-d1now reportsqlite. Update saved queries, alerts and dashboards that filter on the connector names.Other Changes
cacheClientoption (#26494)JSON.stringifyoutput that goes into generated code (#26314)Internal Changes
01bcb7fto6bf4a27(#26447)Work in this release was contributed by @JavierCane. Thank you for your contribution!
expo/expo (expo)
v58.0.26Compare Source
Patch Changes
/messagesocket and network inspector on port 443 when the bundle URL ishttpswith no port, such as anexpo start --tunnelURL. (#53466 by @vonovak)i18next/i18next-browser-languageDetector (i18next-browser-languagedetector)
v8.3.1Compare Source
@(likesr@latin, stored assr%40latin) is detected again on the next load instead of being dropped by the language code check. Thanks @SudeepGowda55 330querystringandhashdetectors decode the value too, so?lng=sr%40latin(whatURLSearchParamsandencodeURIComponentwrite) is detected assr@latin. A value that is not valid percent-encoding is still skipped.Configuration
📅 Schedule: (in timezone Europe/Copenhagen)
🚦 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.
This PR has been generated by Mend Renovate CLI.
⚠️ 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.
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.