helloadhavan/github_issues huggingface dataset:
Repository: rust-lang/rust
Pull request: unstably mark `NonNull::with_exposed_provenance` as const

Feature: `const_nonnull_with_exposed_provenance`
Tracking issue: https://github.com/rust-lang/rust/issues/154215

This PR constifies `NonNull::with_exposed_provenance`.

r? @tgross35


Changed files:
filename: library/core/src/ptr/non_null.rs
patch: @@ -138,8 +138,9 @@ impl<T: Sized> NonNull<T> {
     ///
     /// This is an [Exposed Provenance][crate::ptr#exposed-provenance] API.
     #[stable(feature = "nonnull_provenance", since = "1.89.0")]
+    #[rustc_const_unstable(feature = "const_nonnull_with_exposed_provenance", issue = "154215")]
     #[inline]
-    pub fn with_exposed_provenance(addr: NonZero<usize>) -> Self {
+    pub const fn with_exposed_provenance(addr: NonZero<usize>) -> Self {
         // SAFETY: we know `addr` is non-zero.
         unsafe {
             let ptr = crate::ptr::with_exposed_provenance_mut(addr.get());
Repository: vercel/next.js
Pull request: Remove leaf segment force-refetch check

Remove the `parallelRoutesKeys.length === 0` condition from `renderComponentsOnThisLevel` in walk-tree-with-flight-router-state.

This check was added to support the behavior where clicking the same link twice forces all page segments to re-render on the server. This should no longer be necessary because the client already adds a refetch marker on those segments, so there's no need to special-case leaf segments on the server side.

Changed files:
filename: packages/next/src/server/app-render/walk-tree-with-flight-router-state.tsx
patch: @@ -99,8 +99,6 @@ export async function walkTreeWithFlightRouterState({
     !flightRouterState ||
     // Segment in router state does not match current segment
     !matchSegment(actualSegment, flightRouterState[0]) ||
-    // Last item in the tree
-    parallelRoutesKeys.length === 0 ||
     // Explicit refresh
     flightRouterState[3] === 'refetch'
Repository: facebook/react
Pull request: Add MIT license header to feature flag utility script

Added the standard Meta Platforms, Inc. MIT license notice to the top of the feature flag comparison script to ensure compliance with repository licensing requirements and for code consistency. 
**No functional or logic changes were made to the code.**

Changed files:
filename: scripts/flags/flags.js
patch: @@ -1,3 +1,9 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
 'use strict';
 
 const babel = require('@babel/register');
Repository: vercel/next.js
Pull request: [otel] set parent span name

Follow up for #90832 

We need to update parent span name when the parent is different from child span

Changed files:
filename: .gitignore
patch: @@ -68,6 +68,7 @@ test-timings.json
 .claude/settings.local.json
 .claude/plans/
 .claude/todos.json
+.claude/worktrees
 CLAUDE.local.md
 
 # Conductor (worktrees created by Conductor app, but keep scripts/)

filename: packages/next/src/build/templates/app-page.ts
patch: @@ -598,6 +598,7 @@ export async function handler(
           // a platform-created HTTP span in adapter deployments).
           if (parentSpan && parentSpan !== span) {
             parentSpan.setAttribute('http.route', route)
+            parentSpan.updateName(name)
           }
         } else {
           span.updateName(`${method} ${srcPage}`)

filename: packages/next/src/build/templates/app-route.ts
patch: @@ -306,6 +306,7 @@ export async function handler(
           // a platform-created HTTP span in adapter deployments).
           if (parentSpan && parentSpan !== span) {
             parentSpan.setAttribute('http.route', route)
+            parentSpan.updateName(name)
           }
         } else {
           span.updateName(`${method} ${srcPage}`)

filename: packages/next/src/build/templates/pages-api.ts
patch: @@ -153,6 +153,7 @@ export async function handler(
             // a platform-created HTTP span in adapter deployments).
             if (parentSpan && parentSpan !== span) {
               parentSpan.setAttribute('http.route', route)
+              parentSpan.updateName(name)
             }
           } else {
             span.updateName(`${method} ${srcPage}`)

filename: packages/next/src/server/route-modules/pages/pages-handler.ts
patch: @@ -429,6 +429,7 @@ export const getHandler = ({
                     // deployments).
                     if (parentSpan && parentSpan !== span) {
                       parentSpan.setAttribute('http.route', route)
+                      parentSpan.updateName(name)
                     }
                   } else {
                     span.updateName(`${method} ${srcPage}`)
Repository: electron/electron
Pull request: ci: update actions/cache to 5.0.3

#### Description of Change
The following message was seen in a release build for 39-x-y:

>Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684, actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Versions greater than 39 already have an updated actions/checkout so this PR just updates actions/cache.  A separate PR will be opened to update actions/checkout for 39-x-y.

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included
- [x] `npm test` passes
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->none


Changed files:
filename: .github/actions/checkout/action.yml
patch: @@ -43,7 +43,7 @@ runs:
       curl --unix-socket /var/run/sas/sas.sock --fail "http://foo/$CACHE_FILE?platform=${{ inputs.target-platform }}&getAccountName=true" > sas-token
   - name: Save SAS Key
     if: ${{ inputs.generate-sas-token == 'true' }}
-    uses: actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+    uses: actions/cache/save@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3
     with:
       path: sas-token
       key: sas-key-${{ inputs.target-platform }}-${{ github.run_number }}-${{ github.run_attempt }}

filename: .github/actions/install-dependencies/action.yml
patch: @@ -7,7 +7,7 @@ runs:
     shell: bash
     id: yarn-cache-dir-path
     run: echo "dir=$(node src/electron/script/yarn.js config get cacheFolder)" >> $GITHUB_OUTPUT
-  - uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+  - uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3
     id: yarn-cache
     with:
       path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
Repository: ollama/ollama
Pull request: fix tensor merge

this fixes a bug with the tensor merge helper. the issue previously is the tensors are sorted in lexical order, not alphanumeric, so the end result is an out of order tensor

Changed files:
filename: convert/tensor.go
patch: @@ -2,10 +2,12 @@ package convert
 
 import (
 	"cmp"
+	"errors"
 	"io"
 	"iter"
 	"path"
 	"slices"
+	"strconv"
 	"strings"
 
 	"github.com/pdevine/tensor"
@@ -94,6 +96,26 @@ func mergeTensors(unmatched []Tensor, merges ...merge) (out []*ggml.Tensor, _ []
 			return matched
 		})
 
+		slices.SortStableFunc(matched, func(a, b Tensor) int {
+			x := strings.Split(a.Name(), ".")
+			y := strings.Split(b.Name(), ".")
+			if len(x) != len(y) {
+				return cmp.Compare(len(x), len(y))
+			}
+
+			vals := make([]int, len(x))
+			for i := range x {
+				vals[i] = strings.Compare(x[i], y[i])
+				m, err := strconv.ParseInt(x[i], 0, 0)
+				n, err2 := strconv.ParseInt(y[i], 0, 0)
+				if errors.Join(err, err2) == nil {
+					vals[i] = cmp.Compare(m, n)
+				}
+			}
+
+			return cmp.Or(vals...)
+		})
+
 		if len(matched) > 0 {
 			out = append(out, &ggml.Tensor{
 				Name:     merges[i].name,

filename: convert/tensor_test.go
patch: @@ -3,8 +3,10 @@ package convert
 import (
 	"bytes"
 	"encoding/binary"
+	"fmt"
 	"io"
 	"iter"
+	"math/rand/v2"
 	"slices"
 	"strings"
 	"testing"
@@ -951,3 +953,45 @@ func TestMerge(t *testing.T) {
 		}
 	})
 }
+
+func TestMergeOrder(t *testing.T) {
+	for range 8 {
+		t.Run("", func(t *testing.T) {
+			tensors := make([]Tensor, 16)
+			for i := range tensors {
+				tensors[i] = &fakeTensor{
+					name:  fmt.Sprintf("layer.%d.weight", i),
+					shape: []uint64{1},
+					data:  []float32{float32(i)},
+				}
+			}
+
+			rand.Shuffle(len(tensors), func(i, j int) {
+				tensors[i], tensors[j] = tensors[j], tensors[i]
+			})
+
+			matched, unmatched := mergeTensors(tensors, merge{"layer.*.weight", "layer.weight"})
+			if len(unmatched) != 0 {
+				t.Error("expected no remaining tensors, got", len(unmatched))
+			}
+
+			if len(matched) != 1 {
+				t.Error("expected 1 merged tensor, got", len(matched))
+			}
+
+			var b bytes.Buffer
+			if _, err := matched[0].WriteTo(&b); err != nil {
+				t.Fatal(err)
+			}
+
+			var f32s [16]float32
+			if err := binary.Read(&b, binary.LittleEndian, &f32s); err != nil {
+				t.Fatal(err)
+			}
+
+			if !slices.IsSorted(f32s[:]) {
+				t.Errorf("merged tensor data is not in order: %+v", f32s)
+			}
+		})
+	}
+}
Repository: rust-lang/rust
Pull request: ui/lto: move and rename two tests from issues/

Move:
- `tests/ui/issues/issue-44056.rs` -> `tests/ui/lto/lto-avx-target-feature.rs`
    - The first test enables both AVX target features and LTO but does not exercise AVX-specific behavior. The test primarily checks that LTO builds successfully with these flags; place it under `ui/lto` for consistency.
- `tests/ui/issues/issue-51947.rs` -> `tests/ui/lto/lto-weak-merge-functions.rs`
    - The second test exercises weak linkage interacting with LTO (merge-functions), so it should belong in `ui/lto`.

I have also added a commented line at the top of each test file indicating the issue it originated from. 

Changed files:
filename: tests/ui/lto/lto-avx-target-feature.rs
patch: @@ -1,3 +1,4 @@
+//! regression test for <https://github.com/rust-lang/rust/issues/44056>
 //@ build-pass (FIXME(55996): should be run on targets supporting avx)
 //@ only-x86_64
 //@ no-prefer-dynamic

filename: tests/ui/lto/lto-weak-merge-functions.rs
patch: @@ -1,3 +1,4 @@
+//! regression test for <https://github.com/rust-lang/rust/issues/51947>
 //@ build-pass
 
 #![crate_type = "lib"]
Repository: rust-lang/rust
Pull request: [stable] Cargo stable backports

1 commits in 292f395c297d4f99171325b0842ac4ea4ff3b386..29ea6fb6a5db279426f4cc4e17aa385f05a0cfbc
2026-03-21 06:42:37 -0500 to 2026-03-24 17:37:48 -0400
- [stable 1.94] Downgrade curl-sys to 0.4.83 (https://github.com/rust-lang/cargo/pull/16787)

Update release notes to mention the Cargo fix and fix broken link.

Changed files:
filename: RELEASES.md
patch: @@ -7,10 +7,11 @@ Version 1.94.1 (2026-03-26)
 * [Remove new methods added to `std::os::windows::fs::OpenOptionsExt`](https://github.com/rust-lang/rust/pull/153491)
   The new methods were unstable, but the trait itself is not sealed and so
   cannot be extended with non-default methods.
-* [[Clippy] Fix ICE in `match_same_arms`](https://github.com/rust-lang/rust-clippy/pull/16685)
-* [[Cargo] Update tar to 0.4.45](https://github.com/rust-lang/cargo/pull/16769)
+* [Clippy: fix ICE in `match_same_arms`](https://github.com/rust-lang/rust-clippy/pull/16685)
+* [Cargo: update tar to 0.4.45](https://github.com/rust-lang/cargo/pull/16769)
   This resolves CVE-2026-33055 and CVE-2026-33056. Users of crates.io are not affected.
   See [blog](https://blog.rust-lang.org/2026/03/21/cve-2026-33056/) for more details.
+* [Cargo: fix certificate validation errors on FreeBSD](https://github.com/rust-lang/cargo/pull/16787)
 
 Version 1.94.0 (2026-03-05)
 ==========================

filename: src/tools/cargo
patch: @@ -1 +1 @@
-Subproject commit 292f395c297d4f99171325b0842ac4ea4ff3b386
+Subproject commit 29ea6fb6a5db279426f4cc4e17aa385f05a0cfbc
Repository: huggingface/transformers
Pull request: Integrate the Neuron device to TrainingArguments

# What does this PR do?

Integrate the neuron device to TrainingArguments. It enables using the neuron device with the `Trainer` class.

Changed files:
filename: src/transformers/training_args.py
patch: @@ -44,6 +44,7 @@
     is_torch_mlu_available,
     is_torch_mps_available,
     is_torch_musa_available,
+    is_torch_neuron_available,
     is_torch_neuroncore_available,
     is_torch_npu_available,
     is_torch_tf32_available,
@@ -1812,6 +1813,7 @@ def _setup_devices(self) -> "torch.device":
                 "torch.distributed process group is initialized, but parallel_mode != ParallelMode.DISTRIBUTED. "
                 "In order to use Torch DDP, launch your script with `python -m torch.distributed.launch"
             )
+
         if is_torch_xla_available():
             device = self.distributed_state.device
             self._n_gpu = 0
@@ -1837,6 +1839,9 @@ def _setup_devices(self) -> "torch.device":
             elif is_torch_hpu_available():
                 device = torch.device("hpu:0")
                 torch.hpu.set_device(device)
+            elif is_torch_neuron_available():
+                device = torch.device("neuron:0")
+                torch.neuron.set_device(device)
             else:
                 # Default to cuda:0 (respects CUDA_VISIBLE_DEVICES); nn.DataParallel handles n_gpu > 1
                 device = torch.device(

filename: src/transformers/utils/__init__.py
patch: @@ -222,6 +222,7 @@
     is_torch_mlu_available,
     is_torch_mps_available,
     is_torch_musa_available,
+    is_torch_neuron_available,
     is_torch_neuroncore_available,
     is_torch_npu_available,
     is_torch_optimi_available,

filename: src/transformers/utils/import_utils.py
patch: @@ -464,6 +464,26 @@ def hpu_backend_compile(*args, **kwargs):
     return True
 
 
+@lru_cache
+def is_torch_neuron_available(check_device: bool = False) -> bool:
+    import torch
+
+    if importlib.util.find_spec("torch_neuronx") is None:
+        return False
+
+    if check_device:
+        try:
+            import torch_neuronx  # noqa: F401
+
+            # Will raise a RuntimeError if no Neuron is found
+            _ = torch.neuron.device_count()
+            return torch.neuron.is_available()
+        except RuntimeError:
+            return False
+
+    return hasattr(torch, "neuron") and torch.neuron.is_available()
+
+
 @lru_cache
 def is_torch_bf16_gpu_available() -> bool:
     if not is_torch_available():
@@ -484,6 +504,8 @@ def is_torch_bf16_gpu_available() -> bool:
         return torch.backends.mps.is_macos_or_newer(14, 0)
     if is_torch_musa_available():
         return torch.musa.is_bf16_supported() if hasattr(torch, "musa") else False
+    if is_torch_neuron_available():
+        return torch.neuron.is_bf16_supported()
     return False
Repository: nodejs/node
Pull request: tools: fix parsing of commit trailers in `lint-release-proposal` GHA

It's failing in https://github.com/nodejs/node/pull/62073 because of f3d3968dcd3d8334ae7778f6bb5ac1f23c563d3a, which sets `PR-URL` in the last line of its message.

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: .github/workflows/lint-release-proposal.yml
patch: @@ -88,7 +88,7 @@ jobs:
           gh api \
             -H "Accept: application/vnd.github+json" \
             -H "X-GitHub-Api-Version: 2022-11-28" \
-            --jq '.commits.[] | { smallSha: .sha[0:10] } + (.commit.message|capture("^(?<title>.+)\n\n(.*\n)*PR-URL: (?<prURL>.+)\n"))' \
+            --jq '.commits.[] | { smallSha: .sha[0:10] } + (.commit.message|capture("^(?<title>.+)\n\n(.*\n)*PR-URL: (?<prURL>.+)(\n|$)"))' \
             "/repos/${GITHUB_REPOSITORY}/compare/v${MAJOR}.x...$GITHUB_SHA" --paginate \
           | node tools/actions/lint-release-proposal-commit-list.mjs "$CHANGELOG_PATH" "$GITHUB_SHA" \
           | while IFS= read -r PR_URL; do
Repository: electron/electron
Pull request: ci: update actions/cache to 5.0.3

Backport of #50222

See that PR for details.


Notes: <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->none


Changed files:
filename: .github/actions/checkout/action.yml
patch: @@ -43,7 +43,7 @@ runs:
       curl --unix-socket /var/run/sas/sas.sock --fail "http://foo/$CACHE_FILE?platform=${{ inputs.target-platform }}&getAccountName=true" > sas-token
   - name: Save SAS Key
     if: ${{ inputs.generate-sas-token == 'true' }}
-    uses: actions/cache/save@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+    uses: actions/cache/save@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3
     with:
       path: sas-token
       key: sas-key-${{ inputs.target-platform }}-${{ github.run_number }}-${{ github.run_attempt }}

filename: .github/actions/install-dependencies/action.yml
patch: @@ -7,7 +7,7 @@ runs:
     shell: bash
     id: yarn-cache-dir-path
     run: echo "dir=$(node src/electron/script/yarn.js config get cacheFolder)" >> $GITHUB_OUTPUT
-  - uses: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684 # v4.2.3
+  - uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3
     id: yarn-cache
     with:
       path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
Repository: facebook/react
Pull request: Fix changelog link

Closes https://github.com/reactjs/react.dev/issues/8081

Changed files:
filename: CHANGELOG.md
patch: @@ -9,7 +9,7 @@ Read the [React 19.2 release post](https://react.dev/blog/2025/10/01/react-19-2)
 - [`<Activity>`](https://react.dev/reference/react/Activity): A new API to hide and restore the UI and internal state of its children.
 - [`useEffectEvent`](https://react.dev/reference/react/useEffectEvent) is a React Hook that lets you extract non-reactive logic into an [Effect Event](https://react.dev/learn/separating-events-from-effects#declaring-an-effect-event).
 - [`cacheSignal`](https://react.dev/reference/react/cacheSignal) (for RSCs) lets your know when the `cache()` lifetime is over.
-- [React Performance tracks](https://react.dev/reference/developer-tooling/react-performance-tracks) appear on the Performance panel’s timeline in your browser developer tools
+- [React Performance tracks](https://react.dev/reference/dev-tools/react-performance-tracks) appear on the Performance panel’s timeline in your browser developer tools
 
 ### New React DOM Features
Repository: huggingface/transformers
Pull request: [remote code/vllm] Fix incorrect tied weights

# What does this PR do?

For remote code that behave correctly with tied weights, we need to keep the same behavior as for the main lib, i.e. not remove them from tied weights (as tied weights are marked as missing to avoid inits!!)

Changed files:
filename: src/transformers/modeling_utils.py
patch: @@ -4609,11 +4609,13 @@ def mark_tied_weights_as_initialized(self, loading_info):
         # Note: this is never an issue in main Transformers, as we never do module-tying, only parameter-tying, and we know
         # which params are supposed to be tied to which other params
         if self.is_remote_code():
-            # Remove those that are already initialized, but appear as missing due to module tying
+            # Remove those that are already initialized, but appear as missing due to module tying (only if they are not known
+            # tied weights, i.e. we did not explicitly mark them as initialized just above)
             loading_info.missing_keys = {
                 key
                 for key in loading_info.missing_keys
-                if not getattr(self.get_parameter_or_buffer(key), "_is_hf_initialized", False)
+                if key in self.all_tied_weights_keys
+                or not getattr(self.get_parameter_or_buffer(key), "_is_hf_initialized", False)
             }
 
     def get_parameter_or_buffer(self, target: str):
Repository: rust-lang/rust
Pull request: triagebot: remove myself from some mention groups

I haven't worked in these areas for a little while, but happy to still be pinged if someone wanted.


Changed files:
filename: triagebot.toml
patch: @@ -1177,7 +1177,7 @@ cc = ["@oli-obk", "@RalfJung", "@JakobDegen", "@vakaras"]
 
 [mentions."compiler/rustc_error_messages"]
 message = "`rustc_error_messages` was changed"
-cc = ["@davidtwco", "@TaKO8Ki"]
+cc = ["@TaKO8Ki"]
 
 [mentions."compiler/rustc_errors/src/annotate_snippet_emitter_writer.rs"]
 message = "`rustc_errors::annotate_snippet_emitter_writer` was changed"
@@ -1189,11 +1189,11 @@ cc = ["@Muscraft"]
 
 [mentions."compiler/rustc_errors/src/formatting.rs"]
 message = "`rustc_errors::formatting` was changed"
-cc = ["@davidtwco", "@TaKO8Ki", "@JonathanBrouwer"]
+cc = ["@TaKO8Ki", "@JonathanBrouwer"]
 
 [mentions."compiler/rustc_macros/src/diagnostics"]
 message = "`rustc_macros::diagnostics` was changed"
-cc = ["@davidtwco", "@TaKO8Ki", "@JonathanBrouwer"]
+cc = ["@TaKO8Ki", "@JonathanBrouwer"]
 
 [mentions."compiler/rustc_public"]
 message = "This PR changes rustc_public"