-
Notifications
You must be signed in to change notification settings - Fork 5k
[automated] Merge branch 'release/8.0' => 'release/8.0-staging' #115577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[automated] Merge branch 'release/8.0' => 'release/8.0-staging' #115577
Conversation
…rios (COM, C++/CLI, custom component host) could try to load coreclr from CWD There is a fallback for apps with no .deps.json where the host will consider the app directory for loading coreclr. In component hosting scenarios, we do not have an app path / directory. We were incorrectly going down the path of looking for coreclr next to the empty app directory, which resulted in looking in the current directory. This change skips that path for libhost scenarios. It also adds checks that the paths we determine for loading coreclr, hostpolicy, and hostfxr are absolute.
…-merge-8.0-2025-05-13-1454
…25-05-13-1454 Merging internal commits for release/8.0
[manual] Merge release/8.0-staging into release/8.0
Co-authored-by: Oleksandr.Didyk <odidyk@microsoft.com>
* Update dependencies from https://github.com/dotnet/emsdk build 20250516.2 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.17-servicing.25266.2 * Update dependencies from https://github.com/dotnet/emsdk build 20250519.2 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.17-servicing.25269.2 * Update dependencies from https://github.com/dotnet/emsdk build 20250604.1 Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100 From Version 8.0.17-servicing.25258.1 -> To Version 8.0.18-servicing.25304.1 --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
[manual] Merge release/8.0-staging into release/8.0
…-merge-8.0-2025-06-10-1311
…rios (COM, C++/CLI, custom component host) could try to load coreclr from CWD (#116498) There is a fallback for apps with no .deps.json where the host will consider the app directory for loading coreclr. In component hosting scenarios, we do not have an app path / directory. We were incorrectly going down the path of looking for coreclr next to the empty app directory, which resulted in looking in the current directory. This change skips that path for libhost scenarios. It also adds checks that the paths we determine for loading coreclr, hostpolicy, and hostfxr are absolute. Co-authored-by: Elinor Fung <elfung@microsoft.com> Co-authored-by: Mirroring <dnceng-mirroring@microsoft.com>
…25-06-10-1311 Merging internal commits for release/8.0
da98994
to
3293017
Compare
The build in this PR is in a really bad state, @dotnet/area-infrastructure-libraries, any advice? |
runtime: browser-wasm windows Release Mono_DebuggerTests_chrome browser-wasm linux Release WasmBuildTests Libraries Test Run release coreclr linux_musl x64 Debug Libraries Test Run release coreclr windows x64 Debug |
runtime-libraries-coreclr outerloop
Being addressed by #116631. S.D.Process error is covered by BA. OS-wide: |
runtime-coreclr outerloop
|
/ba-g see above comments |
I detected changes in the release/8.0 branch which have not been merged yet to release/8.0-staging. I'm a robot and am configured to help you automatically keep release/8.0-staging up to date, so I've opened this PR.
This PR merges commits made on release/8.0 by the following committers:
Instructions for merging from UI
This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.
If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.
Instructions for merging via command line
Run these commands to merge this pull request from the command line.
or if you are using SSH
After PR checks are complete push the branch
Instructions for resolving conflicts
Instructions for updating this pull request
Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/8.0-to-release/8.0-staging'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.
or if you are using SSH
Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.