From 7d45e4172b0440a59e2476e807fed0017a6d443a Mon Sep 17 00:00:00 2001 From: "dotnet-maestro[bot]" Date: Tue, 4 Aug 2026 02:02:52 +0000 Subject: [PATCH 1/6] Update dependencies from https://dev.azure.com/dnceng/internal/_git/dotnet-optimization build 20260803.1 On relative base path root optimization.linux-arm64.MIBC.Runtime , optimization.linux-x64.MIBC.Runtime , optimization.windows_nt-arm64.MIBC.Runtime , optimization.windows_nt-x64.MIBC.Runtime , optimization.windows_nt-x86.MIBC.Runtime From Version 1.0.0-prerelease.26318.1 -> To Version 1.0.0-prerelease.26403.1 --- eng/Version.Details.props | 10 +++++----- eng/Version.Details.xml | 20 ++++++++++---------- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/eng/Version.Details.props b/eng/Version.Details.props index 6dd4474cadb..37820e5f923 100644 --- a/eng/Version.Details.props +++ b/eng/Version.Details.props @@ -13,11 +13,11 @@ This file should be imported by eng/Versions.props 18.10.0-preview-26357-08 18.10.0-preview-26357-08 - 1.0.0-prerelease.26318.1 - 1.0.0-prerelease.26318.1 - 1.0.0-prerelease.26318.1 - 1.0.0-prerelease.26318.1 - 1.0.0-prerelease.26318.1 + 1.0.0-prerelease.26403.1 + 1.0.0-prerelease.26403.1 + 1.0.0-prerelease.26403.1 + 1.0.0-prerelease.26403.1 + 1.0.0-prerelease.26403.1 5.10.0-1.26365.3 5.10.0-1.26365.3 diff --git a/eng/Version.Details.xml b/eng/Version.Details.xml index 0932647c439..3bd742b9492 100644 --- a/eng/Version.Details.xml +++ b/eng/Version.Details.xml @@ -86,25 +86,25 @@ https://github.com/dotnet/arcade 09bc8c946f4c4ae5d031c8875b85a6b8f1876b93 - + https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - 06d09f3116a8ce9eed58e97ab167a3d1f4e1f151 + 4e59839621546daec139a776ec6510f61775e1df - + https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - 06d09f3116a8ce9eed58e97ab167a3d1f4e1f151 + 4e59839621546daec139a776ec6510f61775e1df - + https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - 06d09f3116a8ce9eed58e97ab167a3d1f4e1f151 + 4e59839621546daec139a776ec6510f61775e1df - + https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - 06d09f3116a8ce9eed58e97ab167a3d1f4e1f151 + 4e59839621546daec139a776ec6510f61775e1df - + https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - 06d09f3116a8ce9eed58e97ab167a3d1f4e1f151 + 4e59839621546daec139a776ec6510f61775e1df From 1d017eb6d661b3ec458533e0f6cf3be74ff7c8d9 Mon Sep 17 00:00:00 2001 From: Copilot Date: Tue, 4 Aug 2026 10:41:14 +0200 Subject: [PATCH 2/6] Pin transitive MessagePack to patched 2.5.302 in LSP Framework Proxy project The Microsoft.CommonLanguageServerProtocol.Framework.Proxy project pulls MessagePack 2.5.108 transitively (via the Framework package -> StreamJsonRpc), which trips NuGetAudit errors NU1902/NU1903 (WarnAsError) and fails the build across all CI jobs. Apply the same 2.5.302 pin already present in FSharp.Compiler.LanguageServer.fsproj. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- ...icrosoft.CommonLanguageServerProtocol.Framework.Proxy.csproj | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/Microsoft.CommonLanguageServerProtocol.Framework.Proxy/Microsoft.CommonLanguageServerProtocol.Framework.Proxy.csproj b/src/Microsoft.CommonLanguageServerProtocol.Framework.Proxy/Microsoft.CommonLanguageServerProtocol.Framework.Proxy.csproj index 97ac5ccaebe..91d2d4d5958 100644 --- a/src/Microsoft.CommonLanguageServerProtocol.Framework.Proxy/Microsoft.CommonLanguageServerProtocol.Framework.Proxy.csproj +++ b/src/Microsoft.CommonLanguageServerProtocol.Framework.Proxy/Microsoft.CommonLanguageServerProtocol.Framework.Proxy.csproj @@ -9,6 +9,8 @@ + + From cddcd44a0b1f68706d72a50849d702780387154e Mon Sep 17 00:00:00 2001 From: Copilot Date: Tue, 4 Aug 2026 13:43:18 +0200 Subject: [PATCH 3/6] Make release-notes comment step non-fatal (fixes check_release_notes 403) The check_release_notes workflow runs via pull_request_target and its final 'Create or update comment' step can return HTTP 403 'Resource not accessible by integration' when the Actions GITHUB_TOKEN is not permitted to create a new issue comment. This turned a passing release-notes validation into a red required check on bot/dependency PRs such as #20132. Posting the informational comment is best-effort, so mark the step continue-on-error: true; the real gate (exit 1 on missing release notes) is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/workflows/check_release_notes.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/check_release_notes.yml b/.github/workflows/check_release_notes.yml index 34a19b198c5..433adc90b3b 100644 --- a/.github/workflows/check_release_notes.yml +++ b/.github/workflows/check_release_notes.yml @@ -305,8 +305,14 @@ jobs: exit 1 fi # Keep one bot comment current without evaluating pull request content as JavaScript. + # Posting the informational comment is best-effort and must never fail the check: + # this job runs via pull_request_target, and the Actions GITHUB_TOKEN is not always + # permitted to create a new issue comment (the comment API can return HTTP 403 + # "Resource not accessible by integration"), even though release-notes validation + # above has already succeeded. - name: Create or update comment if: ${{ (success() || failure()) && steps.release_notes_changes.outputs.release-notes-check-message != '' }} + continue-on-error: true uses: actions/github-script@v9 env: COMMENT_BODY: ${{ steps.release_notes_changes.outputs.release-notes-check-message }} From 6c3da1811b1b89c4603993f11ef228085a2bf8eb Mon Sep 17 00:00:00 2001 From: Copilot Date: Tue, 4 Aug 2026 15:13:18 +0200 Subject: [PATCH 4/6] Retrigger CI (flaky NuGet package-management test 13219-bug-FSI) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> From 72a2a01a8bafe220868b047feac041f1c9f94617 Mon Sep 17 00:00:00 2001 From: Copilot Date: Tue, 4 Aug 2026 16:50:19 +0200 Subject: [PATCH 5/6] Make release-notes comment step tolerate 403 without failing check The informational bot comment in check_release_notes runs via pull_request_target, where the GITHUB_TOKEN cannot always create issue comments (HTTP 403 on darc/Dependabot PRs). Release-notes validation already passed by then, so wrap the comment logic in a try/catch that warns and continues on 403 (keeping continue-on-error as a safety net). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .github/workflows/check_release_notes.yml | 54 ++++++++++++++--------- 1 file changed, 34 insertions(+), 20 deletions(-) diff --git a/.github/workflows/check_release_notes.yml b/.github/workflows/check_release_notes.yml index 433adc90b3b..20223eb0332 100644 --- a/.github/workflows/check_release_notes.yml +++ b/.github/workflows/check_release_notes.yml @@ -320,29 +320,43 @@ jobs: github-token: ${{ github.token }} script: | const marker = ''; - const comments = await github.paginate(github.rest.issues.listComments, { - owner: context.repo.owner, - repo: context.repo.repo, - issue_number: context.issue.number, - per_page: 100 - }); - const existing = comments.find(comment => - comment.user?.login === 'github-actions[bot]' && comment.body?.includes(marker)); - - if (existing) { - const comment = await github.rest.issues.updateComment({ + try { + const comments = await github.paginate(github.rest.issues.listComments, { + owner: context.repo.owner, + repo: context.repo.repo, + issue_number: context.issue.number, + per_page: 100 + }); + const existing = comments.find(comment => + comment.user?.login === 'github-actions[bot]' && comment.body?.includes(marker)); + + if (existing) { + const comment = await github.rest.issues.updateComment({ + owner: context.repo.owner, + repo: context.repo.repo, + comment_id: existing.id, + body: process.env.COMMENT_BODY + }); + return comment.data.id; + } + + const comment = await github.rest.issues.createComment({ + issue_number: context.issue.number, owner: context.repo.owner, repo: context.repo.repo, - comment_id: existing.id, body: process.env.COMMENT_BODY }); return comment.data.id; + } catch (error) { + // The informational comment is best-effort. The GITHUB_TOKEN for a + // pull_request_target run is not always allowed to write issue comments + // (e.g. Dependabot/darc-authored PRs), so the API can return HTTP 403 + // "Resource not accessible by integration". Release-notes validation has + // already passed in the previous step, so a failed comment must not fail + // the check. Warn and continue for permission errors; rethrow anything else. + if (error.status === 403) { + core.warning(`Skipping release-notes comment: ${error.message}`); + return; + } + throw error; } - - const comment = await github.rest.issues.createComment({ - issue_number: context.issue.number, - owner: context.repo.owner, - repo: context.repo.repo, - body: process.env.COMMENT_BODY - }); - return comment.data.id; From c9940e33f45e0739386b76c9cc779e2051559a49 Mon Sep 17 00:00:00 2001 From: Copilot Date: Tue, 4 Aug 2026 18:15:54 +0200 Subject: [PATCH 6/6] Retrigger CI (Linux test host OOM-killed, exit 137 - infra flake) The Linux job was SIGKILLed (exit 137) while running FSharp.Compiler.ComponentTests with 'Free memory is lower than 5%'; no test assertion failed (failed: 0). This is an environmental OOM, unrelated to the PR content (a darc dependency bump plus a GitHub Actions YAML edit). Retriggering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>