[net8.0] Merge main into net8.0. #18609
Conversation
…1: Build ID 8130882
xamarin#18567) … the Build Agent and remote tasks DOTNET_ROOT and DOTNET_HOST_PATH are being deprecated as a mechanism to store the location of dotnet. PATH will be used instead, so we should ensure that the existing code that makes usage of these variables is adapted to the new guidelines. More information: dotnet/roslyn@f454d69 dotnet/runtime#88754 (comment) Additionally, to avoid confusion, we are using a dedicate DOTNET_CUSTOM_PATH variable with the path of the dotnet used by the XMA Build Agent, so it can be used internally by the tasks without mixing it with the existing dotnet variables --------- Co-authored-by: GitHub Actions Autoformatter <[email protected]>
…k on CI. This commit fixes the code that was added in xamarin#16361. The previous change uses the version number that is part of the config file in the current build machine. That is correct when we are working when we are running the tests in the same machine that built them. That IS NOT THE CASE when building on CI. Back when the CI did the separation to accommodate the EO we noticed that if the workload is built in a diff machine, the versions were not to be trusted, that is why the CI sets and enviroment variable to track the version that was built in the original step. This change check if we are on the CI, if we are we trust the version given by the previos machine, else we use the config one.
Co-authored-by: Haritha Mohan <[email protected]>
…rin-macios into fix-mlaunch-location
…1: Build ID 8130882 (xamarin#18574) This is the pull request automatically created by the OneLocBuild task in the build process to check-in localized files generated based upon translation source files (.lcl files) handed-back from the downstream localization pipeline. If there are issues in translations, visit https://aka.ms/icxLocBug and log bugs for fixes. The OneLocBuild wiki is https://aka.ms/onelocbuild and the localization process in general is documented at https://aka.ms/AllAboutLoc.
…k on CI. (xamarin#18600) This commit fixes the code that was added in xamarin#16361. The previous change uses the version number that is part of the config file in the current build machine. That is correct when we are working when we are running the tests in the same machine that built them. That IS NOT THE CASE when building on CI. Back when the CI did the separation to accommodate the EO we noticed that if the workload is built in a diff machine, the versions were not to be trusted, that is why the CI sets and enviroment variable to track the version that was built in the original step. This change check if we are on the CI, if we are we trust the version given by the previos machine, else we use the config one.
…ot decommissioning (xamarin#18541) Add prIssueManagement.yml to onboard repo to GitOps.ResourceManagement as FabricBot replacement Owners of the FabricBot configuration should have received email notification. The same information contained in the email is published internally at: https://aka.ms/gim/fabricbot. Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html
rolfbjarne
requested review from
mandel-macaque,
emaf and
mauroa
as code owners
💻 [CI Build] Windows Integration Tests passed 💻✅ All Windows Integration Tests passed. Pipeline on Agent |
📚 [PR Build] Artifacts 📚Packages generatedView packagesPipeline on Agent |
💻 [PR Build] Tests on macOS M1 - Mac Big Sur (11.5) passed 💻✅ All tests on macOS M1 - Mac Big Sur (11.5) passed. Pipeline on Agent |
💻 [PR Build] Tests on macOS M1 - Mac Ventura (13.0) passed 💻✅ All tests on macOS M1 - Mac Ventura (13.0) passed. Pipeline on Agent |
✅ API diff for current PR / commitNET (empty diffs)
❗ API diff vs stable (Breaking changes).NET (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:)
ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
🚀 [CI Build] Test results 🚀Test results✅ All tests passed on VSTS: simulator tests. 🎉 All 92 tests passed 🎉 Tests counts
Pipeline on Agent |
No description provided.