Home » Oreps » React Native Windows » All Pull Requests » #16472
microsoft/react-native-windows
A framework for building native Windows apps with React.
Watch
0
Commit Activity
Pull Requests
Directory Browser
Velocity History
Releases

📦 [0.85]: Bump the all-dependencies group across 1 directory with 22 updates #16472

Compare code on GitHub
Open
dependabot[bot] opened 4:18am on October 7, 2026 wants to merge 1 commit into microsoft/react-native-windows 0.85-stable from
dependabot/npm_and_yarn/0.85-stable/all-dependencies-849a08a499

Pull Request Overview

  • Opened on October 7, 2026
  • Status Open
  • Commit count 1 with first commit October 7, 2026

Total Delta

0 Total Diff Delta

Open Days

Open 23 weekdays

Test Delta

0 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time Business days Phase
 
 0.0 days Authoring 1 commit before pull request opened for review
 
 0.0 days Awaiting first review
 
 23.0 days Revising work with 0 commits in response to 1 review that left 2 comments

Total time for pull request still awaiting merge (longer than repo's target): 23.0 business days

Author avatar

📦 [0.85]: Bump the all-dependencies group across 1 directory with 22 updates

Bumps the all-dependencies group with 22 updates in the / directory:

Package
From
To

beachball
2.65.5
2.66.0

lage
2.15.12
2.17.0

ts-jest
29.4.11
29.4.14

@types/react
19.2.16
19.2.18

@rnx-kit/jest-preset
0.3.2
0.3.3

semver
7.8.2
7.8.5

@types/async
3.2.25
3.2.26

@types/lodash
4.17.24
4.17.25

@types/react-test-renderer
19.1.0
19.3.0

metro-runtime
0.84.4
0.84.6

metro-source-map
0.84.4
0.84.6

@xmldom/xmldom
0.8.13
0.8.15

@microsoft/1ds-core-js
4.4.1
4.4.4

@microsoft/1ds-post-js
4.4.1
4.4.4

@microsoft/api-extractor
7.58.7
7.59.3

eslint-plugin-jest
29.15.2
29.16.6

memfs
4.57.6
4.79.0

metro-babel-register
0.84.4
0.84.6

metro-transform-plugins
0.84.4
0.84.6

shell-quote
1.8.4
1.11.0

@rnx-kit/metro-config
2.2.4
2.2.6

screenshot-desktop
1.15.4
1.15.6

Updates beachball from 2.65.5 to 2.66.0

Changelog

Sourced from beachball's changelog.



2.66.0


Wed, 09 Sep 2026 03:05:57 GMT


Minor changes



2.65.6


Tue, 25 Aug 2026 01:40:36 GMT


Patches



Commits

Attestation changes

This version has no provenance attestation, while the previous version (2.65.5) was attested. Review the package versions before updating.


Updates lage from 2.15.12 to 2.17.0

Commits


Updates ts-jest from 29.4.11 to 29.4.14

Release notes

Sourced from ts-jest's releases.



v29.4.14


Please refer to CHANGELOG.md for details.


v29.4.13


Please refer to CHANGELOG.md for details.


v29.4.12


Please refer to CHANGELOG.md for details.


Changelog

Sourced from ts-jest's changelog.




29.4.14 (2026-09-25)


Reverts




29.4.13 (2026-09-22)


Features



Performance Improvements




29.4.12 (2026-07-22)


Features




  • compiler: support TypeScript 7 projects through compatibility aliases (#5386)


Commits



  • 2d152f6 chore(release): 29.4.14


  • 01e5a2e revert: bring back prior changes of compiler util (#5471)


  • 8e35da6 build(deps): update dependency typescript-eslint to ^8.70.1


  • 76ec454 build(deps): bump image-size from 2.0.2 to 2.0.4 in /website


  • a0c364f chore(release): 29.4.13


  • 697d337 perf(compiler): cache module resolution modes (#5419)


  • c3a0b57 feat: support Babel 8 (#5466)


  • 5fb44c4 build(deps): update dependency jest-environment-jsdom to ^30.5.2


  • 257a524 build(deps): update dependency jest to v30.5.2


  • 89ba4d9 build(deps): update dependency babel-jest to ^30.5.2

  • Additional commits viewable in compare view


Updates @types/react from 19.2.16 to 19.2.18

Commits


Updates @rnx-kit/jest-preset from 0.3.2 to 0.3.3

Release notes

Sourced from @​rnx-kit/jest-preset's releases.




@​rnx-kit/jest-preset@​0.3.3


Patch Changes



  • 57d86ad: Replaced find-up with the implementation in a transitive dependency


Changelog

Sourced from @​rnx-kit/jest-preset's changelog.



0.3.3


Patch Changes



  • 57d86ad: Replaced find-up with the implementation in a transitive dependency


Commits

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​rnx-kit/jest-preset since your current version.


Updates semver from 7.8.2 to 7.8.5

Release notes

Sourced from semver's releases.



v7.8.5



7.8.5 (2026-06-19)


Bug Fixes



v7.8.4



7.8.4 (2026-06-09)


Bug Fixes



v7.8.3



7.8.3 (2026-06-08)


Bug Fixes



Chores



Changelog

Sourced from semver's changelog.




7.8.5 (2026-06-19)


Bug Fixes




7.8.4 (2026-06-09)


Bug Fixes




7.8.3 (2026-06-08)


Bug Fixes



Chores



Commits



  • 6e05b76 chore: release 7.8.5 (#879)


  • 9c8692a fix: include prereleases in tilde range lower bound with includePrerelease (#...


  • 8640bd6 chore: release 7.8.4 (#875)


  • e583226 fix: reject numeric segments after x-ranges


  • 6b77aa8 chore: release 7.8.3 (#873)


  • 3485dda chore: bump @​npmcli/eslint-config from 6.0.1 to 7.0.0 (#866)


  • 046da7f fix: align caret includePrerelease lower bounds (#872)

  • See full diff in compare view


Updates @types/async from 3.2.25 to 3.2.26

Commits


Updates @types/lodash from 4.17.24 to 4.17.25

Commits


Updates @types/react-test-renderer from 19.1.0 to 19.3.0

Commits


Updates metro-runtime from 0.84.4 to 0.84.6

Release notes

Sourced from metro-runtime's releases.



v0.84.6


This release is on the 0.84.x branch



Full Changelog: https://github.com/facebook/metro/compare/v0.84.5...v0.84.6


v0.84.5


This release is on the 0.84.x branch



Full Changelog: https://github.com/facebook/metro/compare/v0.84.4...v0.84.5


Commits


Updates metro-source-map from 0.84.4 to 0.84.6

Release notes

Sourced from metro-source-map's releases.



v0.84.6


This release is on the 0.84.x branch



Full Changelog: https://github.com/facebook/metro/compare/v0.84.5...v0.84.6


v0.84.5


This release is on the 0.84.x branch



Full Changelog: https://github.com/facebook/metro/compare/v0.84.4...v0.84.5


Commits


Updates @xmldom/xmldom from 0.8.13 to 0.8.15

Release notes

Sourced from @​xmldom/xmldom's releases.



0.8.15


Commits


Fixed



  • Security: parsing a deeply or repeatedly namespaced document no longer consumes quadratic memory; the in-scope namespace map is inherited through the prototype chain instead of being copied for every prefix-declaring element (O(N) instead of O(N²)), preventing a denial-of-service reachable from DOMParser.parseFromString with default options. Serialized output is byte-identical. GHSA-965w-775f-mr7g

  • Security: attribute de-duplication during parsing is now O(M) instead of O(M²); the NamedNodeMap parse-time dedup path uses a null-prototype membership index, so a well-formed document with a hostile number of duplicate attributes can no longer wedge the parse. Attribute order and duplicate resolution (last value wins, first position kept) are byte-identical, preserving the XML no-duplicate-attributes well-formedness constraint. GHSA-8344-3jmq-59r6

  • Security: trimming trailing whitespace from an XML end tag (ETag) is now anchored so it runs in linear time instead of backtracking quadratically on a long whitespace run, preventing a ReDoS reachable from DOMParser.parseFromString. Trimmed output is byte-identical. GHSA-x4fp-j954-r2f4

  • Security: malformed-input recovery is now linear instead of quadratic — the malformed tag-name scan terminates at an embedded <, and Node.prototype.normalize() merges adjacent text nodes in O(K) instead of O(K²) (also reachable programmatically), per normalize() in the WHATWG DOM spec. DOM output is unchanged; only the reported error text differs. GHSA-93r5-fhx6-vmg9

  • Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now rejects a DocType name that is not a valid XML Name, throwing InvalidStateError — matching the sibling publicId/systemId/internalSubset checks and preventing XML injection via DocumentType.name. GHSA-27p8-2357-5qqv

  • Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now validates a processing-instruction target as an XML NCName and rejects a case-insensitive xml, throwing InvalidStateError — a check 0.8.x did not previously perform, preventing PI-target injection via >, ?, or whitespace. GHSA-c7q8-3ch8-vqpv

  • Security: Document.createEntityReference() now rejects an invalid XML Name at creation, and XMLSerializer.serializeToString() under { requireWellFormed: true } validates an EntityReference nodeName as an XML Name, throwing InvalidStateError — preventing XML injection via an entity-reference name. GHSA-6gmq-8vp8-gcm6

  • Security: the parser now reports a not-well-formed end tag whose valid name is followed by trailing content as a recoverable error instead of accepting it silently, per the XML ETag production; parsing recovers to the byte-identical DOM. Consumers that want strict rejection can escalate the reported error to fatal via the parser's errorHandler. GHSA-6h8r-xr42-gp59


Thank you,
@​ericchiang,
@​bhaswanthc,
@​arpitjain099,
@​Paranoidgrinch,
for your contributions


0.8.14


Commits


Fixed



  • Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm


Thank you,
@​bhaswanthc,
@​jmestwa-coder,
for your contributions


Changelog

Sourced from @​xmldom/xmldom's changelog.



0.8.15


Fixed



  • Security: parsing a deeply or repeatedly namespaced document no longer consumes quadratic memory; the in-scope namespace map is inherited through the prototype chain instead of being copied for every prefix-declaring element (O(N) instead of O(N²)), preventing a denial-of-service reachable from DOMParser.parseFromString with default options. Serialized output is byte-identical. GHSA-965w-775f-mr7g

  • Security: attribute de-duplication during parsing is now O(M) instead of O(M²); the NamedNodeMap parse-time dedup path uses a null-prototype membership index, so a well-formed document with a hostile number of duplicate attributes can no longer wedge the parse. Attribute order and duplicate resolution (last value wins, first position kept) are byte-identical, preserving the XML no-duplicate-attributes well-formedness constraint. GHSA-8344-3jmq-59r6

  • Security: trimming trailing whitespace from an XML end tag (ETag) is now anchored so it runs in linear time instead of backtracking quadratically on a long whitespace run, preventing a ReDoS reachable from DOMParser.parseFromString. Trimmed output is byte-identical. GHSA-x4fp-j954-r2f4

  • Security: malformed-input recovery is now linear instead of quadratic — the malformed tag-name scan terminates at an embedded <, and Node.prototype.normalize() merges adjacent text nodes in O(K) instead of O(K²) (also reachable programmatically), per normalize() in the WHATWG DOM spec. DOM output is unchanged; only the reported error text differs. GHSA-93r5-fhx6-vmg9

  • Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now rejects a DocType name that is not a valid XML Name, throwing InvalidStateError — matching the sibling publicId/systemId/internalSubset checks and preventing XML injection via DocumentType.name. GHSA-27p8-2357-5qqv

  • Security: XMLSerializer.serializeToString() under { requireWellFormed: true } now validates a processing-instruction target as an XML NCName and rejects a case-insensitive xml, throwing InvalidStateError — a check 0.8.x did not previously perform, preventing PI-target injection via >, ?, or whitespace. GHSA-c7q8-3ch8-vqpv

  • Security: Document.createEntityReference() now rejects an invalid XML Name at creation, and XMLSerializer.serializeToString() under { requireWellFormed: true } validates an EntityReference nodeName as an XML Name, throwing InvalidStateError — preventing XML injection via an entity-reference name. GHSA-6gmq-8vp8-gcm6

  • Security: the parser now reports a not-well-formed end tag whose valid name is followed by trailing content as a recoverable error instead of accepting it silently, per the XML ETag production; parsing recovers to the byte-identical DOM. Consumers that want strict rejection can escalate the reported error to fatal via the parser's errorHandler. GHSA-6h8r-xr42-gp59


Thank you,
@​ericchiang,
@​bhaswanthc,
@​arpitjain099,
@​Paranoidgrinch,
for your contributions


0.9.11


Fixed



  • Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm

  • Security: the processing-instruction grammar regex no longer backtracks quadratically on an unterminated processing instruction (<?… with no closing ?>), preventing a denial-of-service (ReDoS) reachable from DOMParser.parseFromString with default options. GHSA-g53g-w8rj-fmg7


  • CharacterData nodeValue and data are now kept in sync #990


Chore



  • updated dependencies


Thank you,
@​bhaswanthc,
@​jmestwa-coder,
@​stevenobiajulu,
for your contributions


0.8.14


Fixed



  • Security: XMLSerializer.serializeToString() now also rejects invalid element and attribute names when { requireWellFormed: true } is passed, throwing InvalidStateError for a name that is not a valid XML QName (this covers the namespace prefix, which surfaces in the element qualified name or in a synthesized xmlns: declaration). This prevents XML injection via createElement() / setAttribute(), extending the existing requireWellFormed checks to the serialized name set. GHSA-w2rr-34g9-rvrj GHSA-4w3w-2rp5-g8jm


Thank you,
@​bhaswanthc,
@​jmestwa-coder,
for your contributions


0.9.10


<!-- raw HTML omitted -->

... (truncated)

Commits



  • b5b8fb5 0.8.15


  • 327508e docs: add 0.8.15 CHANGELOG entry


  • f40ccb8 fix: prevent quadratic malformed-tag recovery and normalize() adjacent-text m...


  • 3abb093 fix: prevent end-tag whitespace-trim ReDoS via anchored trim (GHSA-x4fp-j954-...


  • 2c548f2 fix: prevent quadratic attribute de-duplication via null-prototype membership...


  • 08a74b4 test: characterize NamedNodeMap attribute de-duplication before the index ref...


  • 954370f fix: prevent quadratic namespace-map memory consumption via prototype-chain i...


  • 4430189 fix: report not-well-formed end-tag trailing content (GHSA-6h8r-xr42-gp59)


  • 6c3fb5f fix: prevent XML injection via unsafe EntityReference name (GHSA-6gmq-8vp8-gcm6)


  • 3b69487 fix: prevent XML injection via unsafe processing instruction target serializa...

  • Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by karfau, a new releaser for @​xmldom/xmldom since your current version.


Updates @microsoft/1ds-core-js from 4.4.1 to 4.4.4

Changelog

Sourced from @​microsoft/1ds-core-js's changelog.



Releases



Note: ES3/IE8 compatibility will be removed in the future v3.x.x releases (scheduled for mid-late 2022), so if you need to retain ES3 compatibility you will need to remain on the 2.x.x versions of the SDK or your runtime will need install polyfill's to your ES3 environment before loading / initializing the SDK.



<!-- raw HTML omitted -->

3.4.5 (October 5th, 2026)


This release enables internal SDK network statistics and routes them to a dedicated SDK Stats ingestion endpoint. The @microsoft/1ds-post-js channel is numbered 4.4.5 and requires v3.4.5.


Significant Changes (since 3.4.4)




  • Internal SDK Stats: The full SDK now records request successes, failures, retries, throttling, and request duration. Counters are persisted in session storage by customer instrumentation key and endpoint, with a default collection interval of one hour (stats.shrtInt, in seconds).


  • Dedicated Ingestion and Dynamic Configuration: Internal SDK Stats use a separate core and sender, rather than the customer's telemetry pipeline. Sending requires stats.cfgUrl, stats.iKey, and an enabled remote configuration that supplies the destination host. EU customer endpoints use the EU-prefixed configuration host. Configuration and sampling can be updated at runtime, and counters are retained while remote configuration is unavailable.


  • Feature Throttling: Added ThrottleMgr.useFeature() and string-keyed throttleMgrCfg entries for feature operations. Internal SDK Stats have a dedicated daily throttle, separate from internal diagnostic messages. Throttle sampling now honors a zero rate, interval rules are evaluated per configuration, and long-lived instances can send again on the next eligible UTC day.


  • Sender Unload Reliability: Late network responses no longer access the cleared core configuration when looking up internal SDK Stats after unload.


Potential behavioral changes


The internal SDK Stats manager is enabled by default, but it does not send statistics until the required local or CDN-delivered configuration is available and the remote configuration enables sending. Disable this feature with featureOptIn: { sdkStats: { mode: FeatureOptInMode.disable } }. The lowercase sdkStats feature is separate from the existing customer-facing SdkStats feature and its sdkStats.int collection interval.


Internal SDK Stats bypass customer telemetry initializers and plugins. Applications that use those hooks to inspect, modify, or filter customer telemetry should use the internal SDK Stats feature flag to opt out instead.


Changelog




  • #2741 Enable SDK Stats and route to the SDK Stats ingestion endpoint


Full Changelog: https://github.com/microsoft/ApplicationInsights-JS/compare/3.4.4...3.4.5


3.4.4 (September 8th, 2026)


This is a maintenance release for the 3.4.x version line containing runtime reliability and bundler compatibility fixes, build tooling and dependency security hardening, documentation corrections, and a test reliability fix. There are no SDK API changes. The @microsoft/1ds-post-js channel is numbered 4.4.4 and requires v3.4.4.


Significant Changes (since 3.4.3)




  • ESM XHR Instrumentation: Fixed tree shaking of the XHR capability check so automatic XHR instrumentation is preserved in ESM bundles.


  • Vite 8 and Rolldown Compatibility: Normalized generated PURE annotations by expression so invalid annotations on primitive literals no longer produce warnings, while valid call and new expression annotations remain tree-shakable.


  • OpenTelemetry Async Error Propagation: Fixed startActiveSpan() so promise rejections from asynchronous callbacks propagate to callers instead of being swallowed.


  • Dependency Security Hardening: Resolved the repository's npm audit and Component Governance findings by updating vulnerable transitive build dependencies and replacing Puppeteer's vulnerable extract-zip dependency with a maintained compatible package. Rush was upgraded to 5.178.1 and pnpm to 10.34.5, while API Extractor remains on the latest Node.js 18-compatible release. These are build/tooling changes and do not affect the published runtime code.


  • GitHub Actions Supply-Chain Hardening: Pinned third-party GitHub Actions to full-length commit SHAs and added grouped weekly Dependabot updates with a seven-day cooldown.


Changelog




  • #2768 Fix ESM XHR instrumentation tree shaking


  • #2767 docs: fix Offline Channel setup example


  • #2766 fix: normalize PURE annotations for Vite 8 and Rolldown


  • #2761 fix(deps): remediate Component Governance vulnerabilities


  • #2758 Pin GitHub Actions to full-length commit SHAs


  • #2757 fix(otel): propagate promise rejection from startActiveSpan async callback


  • #2754 fix(test): stabilize flaky SpanLifeCycle custom endTime test


<!-- raw HTML omitted -->

... (truncated)

Commits


Updates @microsoft/1ds-post-js from 4.4.1 to 4.4.4

Changelog

Sourced from @​microsoft/1ds-post-js's changelog.



Releases



Note: ES3/IE8 compatibility will be removed in the future v3.x.x releases (scheduled for mid-late 2022), so if you need to retain ES3 compatibility you will need to remain on the 2.x.x versions of the SDK or your runtime will need install polyfill's to your ES3 environment before loading / initializing the SDK.



<!-- raw HTML omitted -->

3.4.5 (October 5th, 2026)


This release enables internal SDK network statistics and routes them to a dedicated SDK Stats ingestion endpoint. The @microsoft/1ds-post-js channel is numbered 4.4.5 and requires v3.4.5.


Significant Changes (since 3.4.4)




  • Internal SDK Stats: The full SDK now records request successes, failures, retries, throttling, and request duration. Counters are persisted in session storage by customer instrumentation key and endpoint, with a default collection interval of one hour (stats.shrtInt, in seconds).


  • Dedicated Ingestion and Dynamic Configuration: Internal SDK Stats use a separate core and sender, rather than the customer's telemetry pipeline. Sending requires stats.cfgUrl, stats.iKey, and an enabled remote configuration that supplies the destination host. EU customer endpoints use the EU-prefixed configuration host. Configuration and sampling can be updated at runtime, and counters are retained while remote configuration is unavailable.


  • Feature Throttling: Added ThrottleMgr.useFeature() and string-keyed throttleMgrCfg entries for feature operations. Internal SDK Stats have a dedicated daily throttle, separate from internal diagnostic messages. Throttle sampling now honors a zero rate, interval rules are evaluated per configuration, and long-lived instances can send again on the next eligible UTC day.


  • Sender Unload Reliability: Late network responses no longer access the cleared core configuration when looking up internal SDK Stats after unload.


Potential behavioral changes


The internal SDK Stats manager is enabled by default, but it does not send statistics until the required local or CDN-delivered configuration is available and the remote configuration enables sending. Disable this feature with featureOptIn: { sdkStats: { mode: FeatureOptInMode.disable } }. The lowercase sdkStats feature is separate from the existing customer-facing SdkStats feature and its sdkStats.int collection interval.


Internal SDK Stats bypass customer telemetry initializers and plugins. Applications that use those hooks to inspect, modify, or filter customer telemetry should use the internal SDK Stats feature flag to opt out instead.


Changelog




  • #2741 Enable SDK Stats and route to the SDK Stats ingestion endpoint


Full Changelog: https://github.com/microsoft/ApplicationInsights-JS/compare/3.4.4...3.4.5


3.4.4 (September 8th, 2026)


This is a maintenance release for the 3.4.x version line containing runtime reliability and bundler compatibility fixes, build tooling and dependency security hardening, documentation corrections, and a test reliability fix. There are no SDK API changes. The @microsoft/1ds-post-js channel is numbered 4.4.4 and requires v3.4.4.


Significant Changes (since 3.4.3)




  • ESM XHR Instrumentation: Fixed tree shaking of the XHR capability check so automatic XHR instrumentation is preserved in ESM bundles.


  • Vite 8 and Rolldown Compatibility: Normalized generated PURE annotations by expression so invalid annotations on primitive literals no longer produce warnings, while valid call and new expression annotations remain tree-shakable.


  • OpenTelemetry Async Error Propagation: Fixed startActiveSpan() so promise rejections from asynchronous callbacks propagate to callers instead of being swallowed.


  • Dependency Security Hardening: Resolved the repository's npm audit and Component Governance findings by updating vulnerable transitive build dependencies and replacing Puppeteer's vulnerable extract-zip dependency with a maintained compatible package. Rush was upgraded to 5.178.1 and pnpm to 10.34.5, while API Extractor remains on the latest Node.js 18-compatible release. These are build/tooling changes and do not affect the published runtime code.


  • GitHub Actions Supply-Chain Hardening: Pinned third-party GitHub Actions to full-length commit SHAs and added grouped weekly Dependabot updates with a seven-day cooldown.


Changelog




  • #2768 Fix ESM XHR instrumentation tree shaking


  • #2767 docs: fix Offline Channel setup example


  • #2766 fix: normalize PURE annotations for Vite 8 and Rolldown


  • #2761 fix(deps): remediate Component Governance vulnerabilities


  • #2758 Pin GitHub Actions to full-length commit SHAs


  • #2757 fix(otel): propagate promise rejection from startActiveSpan async callback


  • #2754 fix(test): stabilize flaky SpanLifeCycle custom endTime test


<!-- raw HTML omitted -->

... (truncated)

Commits


Updates @microsoft/api-extractor from 7.58.7 to 7.59.3

Changelog

Sourced from @​microsoft/api-extractor's changelog.



7.59.3


Mon, 28 Sep 2026 20:08:26 GMT


Version update only


7.59.2


Tue, 22 Sep 2026 17:35:41 GMT


Patches



  • Update the @microsoft/tsdoc dependency to ~0.17.0 and the @microsoft/tsdoc-config dependency to ~0.18.2.


7.59.1


Sat, 05 Sep 2026 00:15:08 GMT


Version update only


7.59.0


Fri, 21 Aug 2026 15:16:34 GMT


Minor changes



  • Report a new ae-unresolved-import-path message when an inline import() type with a relative path cannot be resolved, instead of silently emitting the unusable path into the .d.ts rollup.


7.58.13


Thu, 20 Aug 2026 00:16:38 GMT


Version update only


7.58.12


Tue, 21 Jul 2026 02:53:22 GMT


Patches



  • Improve the performance of the internal excerpt token condensing algorithm from O(n^2) to O(n) by eliminating repeated array splicing and per-merge bookkeeping.


7.58.11


Fri, 17 Jul 2026 00:15:59 GMT


Version update only


7.58.10


Thu, 16 Jul 2026 00:16:13 GMT


Version update only


7.58.9


Sat, 13 Jun 2026 00:16:18 GMT


Version update only


<!-- raw HTML omitted -->

... (truncated)

Commits

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for @​microsoft/api-extractor since your current version.


Updates eslint-plugin-jest from 29.15.2 to 29.16.6

Release notes

Sourced from eslint-plugin-jest's releases.



v29.16.6



29.16.6 (2026-08-30)


Bug Fixes




  • prefer-to-have-been-called: don't crash on matcher without an argument (#2016) (58e487f)


  • prefer-to-have-length: don't crash on expect chain without a value (#2014) (3629019)


v29.16.5



29.16.5 (2026-08-27)


Bug Fixes




  • no-export: handle literal property accessors (#2011) (d848f70)


v29.16.4



29.16.4 (2026-08-27)


Bug Fixes




  • no-export: handle nested assignment chains (#2009) (14b559a)


v29.16.3



29.16.3 (2026-08-27)


Bug Fixes



v29.16.2



29.16.2 (2026-08-25)


Bug Fixes




  • prefer-equality-matcher: don't crash on expect chain without a value (#2006) (27665cd)


v29.16.1



29.16.1 (2026-08-12)


Bug Fixes




  • prefer-comparison-matcher: don't crash on expect chain without a value (#2001) (a4d20e0)


  • prefer-expect-resolves: don't crash on expect chain without a value (#2002) (0cf65de)


<!-- raw HTML omitted -->

... (truncated)

Changelog

Sourced from eslint-plugin-jest's changelog.




29.16.6 (2026-08-30)


Bug Fixes




  • prefer-to-have-been-called: don't crash on matcher without an argument (#2016) (58e487f)


  • prefer-to-have-length: don't crash on expect chain without a value (#2014) (3629019)



29.16.5 (2026-08-27)


Bug Fixes




  • no-export: handle literal property accessors (#2011) (d848f70)


<a href="https://github.com/jest-community/eslint-plugin-j...


Description has been truncated
###### Microsoft Reviewers: Open in CodeFlow

Comments Threads Pending Resolution

ljharb reviewed on October 7, 2026
ljharb left a comment

Copilot wasn't able to review any files in this pull request. Check if the **Files changed** in this pull request are included in [default exclusions](https://docs.github.com/en/copilot/reference/review-excluded-files).

Resolved Comment Threads

No resolved comments have been left on this PR.

GitClear uses cookies to ensure you get the best experience on our website. Learn more about our cookie policy