Skip to content

Conversation

@vmoroz
Copy link
Member

@vmoroz vmoroz commented Nov 8, 2025

Description

Type of Change

  • New feature (non-breaking change which adds functionality)

Why

We should switch to the new version of hermes-windows that fixes the latest issues that we see in the e2etest runs.
The hermes-windows version 0.0.0-2511.7001-d7ca19b3 comparing to the previous version 0.0.0-2511.3001-9e4cf518 has the following changes:

What

  • The Hermes version is updated in the vnext/PropertySheets/JSEngine.props file to 0.0.0-2511.7001-d7ca19b3.
  • Ran vnext\Scripts\NuGetRestoreForceEvaluateAllSolutions.ps1 script to update all packages.lock.json files.

Testing

The e2etest seems to be running OK.

Changelog

Should this change be included in the release notes: yes

Use Hermes version 0.0.0-2511.7001-d7ca19b3

Microsoft Reviewers: Open in CodeFlow

@vmoroz vmoroz requested review from a team as code owners November 8, 2025 00:15
@vmoroz vmoroz merged commit 5837f91 into microsoft:main Nov 8, 2025
57 checks passed
@vmoroz vmoroz deleted the PR/use-hermes-windows-0.0.0-2511.7001-d7ca19b3 branch November 8, 2025 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants