Use hermes-windows version 0.0.0-2511.7001-d7ca19b3 #15337
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Why
We should switch to the new version of
hermes-windowsthat fixes the latest issues that we see in the e2etest runs.The hermes-windows version
0.0.0-2511.7001-d7ca19b3comparing to the previous version0.0.0-2511.3001-9e4cf518has the following changes:What
vnext/PropertySheets/JSEngine.propsfile to0.0.0-2511.7001-d7ca19b3.vnext\Scripts\NuGetRestoreForceEvaluateAllSolutions.ps1script to update allpackages.lock.jsonfiles.Testing
The e2etest seems to be running OK.
Changelog
Should this change be included in the release notes: yes
Microsoft Reviewers: Open in CodeFlow