helloadhavan/github_issues huggingface dataset:
Repository: huggingface/transformers
Pull request: [XPU] Fix fp8 UT patch func

# What does this PR do?

When testing `tests/quantization/finegrained_fp8/test_fp8.py` on XPU, it reported the following error:
```
FAILED tests/quantization/finegrained_fp8/test_fp8.py::FP8QuantizerTest::test_dequantization_no_accelerator - AssertionError: False is not true
FAILED tests/quantization/finegrained_fp8/test_fp8.py::FP8QuantizerTest::test_dequantize_when_no_accelerator - ValueError: Expected a xpu device, but got: cpu
FAILED tests/quantization/finegrained_fp8/test_fp8.py::FP8QuantizerTest::test_quantizer_validation_no_accelerator - AssertionError: RuntimeError not raised
```
The root cause is that the `_patch_no_accelerator` method does not fully take effect on XPU.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- text models: @ArthurZucker @Cyrilvallez
- vision models: @yonigozlan @molbap
- audio models: @eustlb @ebezzam @vasqu
- multimodal models: @zucchini-nlp
- graph models: @clefourrier

Library:

- generate: @zucchini-nlp (visual-language models) or @gante (all others)
- continuous batching: @remi-or @ArthurZucker @McPatate
- pipelines: @Rocketknight1
- tokenizers: @ArthurZucker and @itazap
- trainer: @SunMarc
- attention: @vasqu @ArthurZucker @CyrilVallez
- model loading (from pretrained, etc): @CyrilVallez
- distributed: @3outeille @ArthurZucker
- CIs: @ydshieh

Integrations:

- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization: @SunMarc @MekkCyber
- kernels: @MekkCyber @drbh
- peft: @BenjaminBossan @githubnemo

Devices/Backends:

- AMD ROCm: @ivarflakstad
- Intel XPU: @IlyasMoutawwakil
- Ascend NPU: @ivarflakstad 

Documentation: @stevhliu

Research projects are not maintained and should be taken as is.

 -->


Changed files:
filename: tests/quantization/finegrained_fp8/test_fp8.py
patch: @@ -46,6 +46,9 @@ def _patch_no_accelerator():
         stack.enter_context(patch("torch.cuda.is_available", return_value=False))
         if hasattr(torch, "xpu"):
             stack.enter_context(patch("torch.xpu.is_available", return_value=False))
+            stack.enter_context(
+                patch("transformers.quantizers.quantizer_finegrained_fp8.is_torch_xpu_available", return_value=False)
+            )
         yield
Repository: vuejs/vue
Pull request: fix a typo on type definition name

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- ISSUE TEMPLATE -->
**Please check if the PR fulfills these requirements**
- [x] Do not submit PRs against the master branch.
- [x] Checkout a topic branch from the relevant branch, e.g. dev, and merge back against that branch.
- [x] The tests are running: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup

If adding new feature:
- [ ] Added accompanying test case.
- [ ] In the commit message, provide convincing reason to add this feature.
      Ideally you should open a suggestion issue first and have it greenlighted before working on it.

If fixing a bug:
- [ ] If you are resolving a special issue, add (fix #xxxx[,#xxx]) (#xxxx is the issue id) in your PR title
- [ ] Provide detailed description of the bug in the PR. Live demo preferred.
- [ ] Add appropriate test coverage if applicable.

**What kind of change does this PR introduce?** (check at least one with "x")
```
[ ] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactoring
[ ] Build related changes
[ ] Other... Please describe:
```

**Does this PR introduce a breaking change?** (check one with "x")
```
[ ] Yes
[x] No
```

If this PR contains a breaking change, please describe the impact and migration path for existing applications:

**Other information**:
I am not very sure this is a breaking change or not on type definition.


Changed files:
filename: src/compiler/codegen/index.js
patch: @@ -7,7 +7,7 @@ import { camelize, no } from 'shared/util'
 
 type TransformFunction = (el: ASTElement, code: string) => string;
 type DataGenFunction = (el: ASTElement) => string;
-type DirctiveFunction = (el: ASTElement, dir: ASTDirective, warn: Function) => boolean;
+type DirectiveFunction = (el: ASTElement, dir: ASTDirective, warn: Function) => boolean;
 
 // configurable state
 let warn
@@ -246,7 +246,7 @@ function genDirectives (el: ASTElement): string | void {
   for (i = 0, l = dirs.length; i < l; i++) {
     dir = dirs[i]
     needRuntime = true
-    const gen: DirctiveFunction = platformDirectives[dir.name] || baseDirectives[dir.name]
+    const gen: DirectiveFunction = platformDirectives[dir.name] || baseDirectives[dir.name]
     if (gen) {
       // compile-time directive that manipulates AST.
       // returns true if it also needs a runtime counterpart.
Repository: ggml-org/llama.cpp
Pull request: test: fix IMROPE perf test case

Ref: https://github.com/ggml-org/llama.cpp/issues/19464


Changed files:
filename: tests/test-backend-ops.cpp
patch: @@ -8523,7 +8523,7 @@ static std::vector<std::unique_ptr<test_case>> make_test_cases_perf() {
                     test_cases.emplace_back(new test_rope(type, { 80,  32, 512, 1},  20, GGML_ROPE_TYPE_NEOX, 512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // neox (stablelm)
                     test_cases.emplace_back(new test_rope(type, { 64,   8, 512, 1},  64, GGML_ROPE_TYPE_NEOX, 512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // neox (falcon 40B)
                     test_cases.emplace_back(new test_rope(type, {128,  12, 512, 1}, 128, GGML_ROPE_TYPE_MROPE,  512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // rope_multi,m-rope (qwen2vl 2B)
-                    test_cases.emplace_back(new test_rope(type, {128,  12, 2, 1}, 128, GGML_ROPE_TYPE_IMROPE,  512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // rope_multi,imrope (qwen3vl 2B)
+                    test_cases.emplace_back(new test_rope(type, {128,  12, 512, 1}, 128, GGML_ROPE_TYPE_IMROPE,  512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // rope_multi,imrope (qwen3vl 2B)
                     test_cases.emplace_back(new test_rope(type, { 80,  16, 2, 1},  80, GGML_ROPE_TYPE_VISION, 512, 1.0f, 0.0f, 1.0f, ff, v, fw)); // rope_multi,m-rope (qwen2vl ViT)
                 }
             }
Repository: ollama/ollama
Pull request: Update README.md

Added Ollama Mixture of Experts repository to terminal apps.

Changed files:
filename: README.md
patch: @@ -337,6 +337,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [podman-ollama](https://github.com/ericcurtin/podman-ollama)
 - [gollama](https://github.com/sammcj/gollama)
 - [Ollama eBook Summary](https://github.com/cognitivetech/ollama-ebook-summary/)
+- [Ollama Mixture of Experts (MOE) in 50 lines of code](https://github.com/rapidarchitect/ollama_moe)
 
 ### Apple Vision Pro
 - [Enchanted](https://github.com/AugustDev/enchanted)
Repository: huggingface/transformers
Pull request: [Quantization] Remove dequant fp8 config

# What does this PR do?

Remove quantization config when dequantizing on the fly

Changed files:
filename: src/transformers/quantizers/quantizer_finegrained_fp8.py
patch: @@ -178,6 +178,10 @@ def _process_model_before_weight_loading(
 
         model.config.quantization_config = self.quantization_config
 
+    def _process_model_after_weight_loading(self, model: "PreTrainedModel", **kwargs):
+        if self.pre_quantized and self.quantization_config.dequantize:
+            self.remove_quantization_config(model)
+
     def update_missing_keys(self, model, missing_keys: list[str], prefix: str) -> list[str]:
         from ..integrations import FP8Linear
Repository: vercel/next.js
Pull request: [bundle-analyzer] Disable revalidateOnFocus and revalidateOnReconnect

For the `experimental-analyze`, the page resets its selected state `onSuccess`.

https://github.com/vercel/next.js/blob/2307d46f511d02f48d4b8f93713c4bc087c0e5ff/apps/bundle-analyzer/app/page.tsx#L64-L68

However, since SWR revalidates on focus, if you click outside the tab and come back, e.g., write to docs or messengers, it revalidates and resets the state. Since the current view can be inside multiple depths, losing that state for focus can be painful. Therefore, set `revalidateOnFocus` to false. For similar reasons, set `revalidateOnReconnect` to false as well.

### Before

https://github.com/user-attachments/assets/ed04b4c2-f414-4fd9-9a6e-4c910031af9f

### After

https://github.com/user-attachments/assets/4130e3ca-9f3a-4f8b-8a5b-a8eb8d7d23dc

Changed files:
filename: apps/bundle-analyzer/app/page.tsx
patch: @@ -61,6 +61,8 @@ export default function Home() {
     isLoading: isAnalyzeLoading,
     error: analyzeError,
   } = useSWR<AnalyzeData>(analyzeDataPath, fetchAnalyzeData, {
+    revalidateOnFocus: false,
+    revalidateOnReconnect: false,
     onSuccess: (newData) => {
       const newRootSourceIndex = getRootSourceIndex(newData)
       setSelectedSourceIndex(newRootSourceIndex)
Repository: facebook/react
Pull request: Add a shorthand for building the view-transition fixture

I end up rebuilding for testing the view-transition fixture a lot. It doesn't need everything that flight needs so this just adds a short hand that's a little faster to rebuild.

Changed files:
filename: package.json
patch: @@ -117,6 +117,7 @@
     "build-for-devtools-dev": "yarn build-for-devtools --type=NODE_DEV",
     "build-for-devtools-prod": "yarn build-for-devtools --type=NODE_PROD",
     "build-for-flight-dev": "cross-env RELEASE_CHANNEL=experimental node ./scripts/rollup/build.js react/index,react/jsx,react.react-server,react-dom/index,react-dom/client,react-dom/server,react-dom.react-server,react-dom-server.node,react-dom-server-legacy.node,scheduler,react-server-dom-webpack/ --type=NODE_DEV,ESM_PROD,NODE_ES2015 && mv ./build/node_modules ./build/oss-experimental",
+    "build-for-vt-dev": "cross-env RELEASE_CHANNEL=experimental node ./scripts/rollup/build.js react/index,react/jsx,react-dom/index,react-dom/client,react-dom/server,react-dom-server.node,react-dom-server-legacy.node,scheduler --type=NODE_DEV && mv ./build/node_modules ./build/oss-experimental",
     "linc": "node ./scripts/tasks/linc.js",
     "lint": "node ./scripts/tasks/eslint.js",
     "lint-build": "node ./scripts/rollup/validate/index.js",
Repository: vercel/next.js
Pull request: Match behavior of baseline-browser-mapping with caniuse-lite

## What?

Similar to `caniuse-lite` there's a new package in `browserslist` that also has "data is outdated" message. In order to handle it in the same way as `caniuse-lite` I've marked it external and added it as a dependency of Next.js when installing.

I'm still not happy about this. This log is not super helpful and would preferably be disabled. Alternatively we can switch to loading browserslist using the rust-side browserslist implementation.

Warning message:

```
[baseline-browser-mapping] The data in this module is over two months old.  To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
```

Changed files:
filename: packages/next/package.json
patch: @@ -101,6 +101,7 @@
     "@next/env": "16.1.0-canary.9",
     "@swc/helpers": "0.5.15",
     "caniuse-lite": "^1.0.30001579",
+    "baseline-browser-mapping": "^2.8.3",
     "postcss": "8.4.31",
     "styled-jsx": "5.1.6"
   },

filename: packages/next/taskfile.js
patch: @@ -50,10 +50,12 @@ export async function copy_styled_jsx_assets(task, opts) {
 }
 
 const externals = {
-  // don't bundle caniuse-lite data so users can
+  // don't bundle caniuse-lite and baseline-browser-mapping data so users can
   // update it manually
   'caniuse-lite': 'caniuse-lite',
   '/caniuse-lite(/.*)/': 'caniuse-lite$1',
+  'baseline-browser-mapping': 'baseline-browser-mapping',
+  '/baseline-browser-mapping(/.*)/': 'baseline-browser-mapping$1',
 
   postcss: 'postcss',
   // Ensure latest version is used

filename: pnpm-lock.yaml
patch: @@ -1081,6 +1081,9 @@ importers:
       '@swc/helpers':
         specifier: 0.5.15
         version: 0.5.15
+      baseline-browser-mapping:
+        specifier: ^2.8.3
+        version: 2.8.32
       caniuse-lite:
         specifier: 1.0.30001746
         version: 1.0.30001746
Repository: ggml-org/llama.cpp
Pull request: server: do not log certain endpoints (avoid log spam)

Avoid spamming the log with requests on `/health` or `/models` API


Changed files:
filename: tools/server/server-http.cpp
patch: @@ -28,14 +28,20 @@ server_http_context::server_http_context()
 server_http_context::~server_http_context() = default;
 
 static void log_server_request(const httplib::Request & req, const httplib::Response & res) {
-    // skip GH copilot requests when using default port
-    if (req.path == "/v1/health") {
+    // skip logging requests that are regularly sent, to avoid log spam
+    if (req.path == "/health"
+        || req.path == "/v1/health"
+        || req.path == "/models"
+        || req.path == "/v1/models"
+        || req.path == "/props"
+        || req.path == "/metrics"
+    ) {
         return;
     }
 
     // reminder: this function is not covered by httplib's exception handler; if someone does more complicated stuff, think about wrapping it in try-catch
 
-    SRV_INF("request: %s %s %s %d\n", req.method.c_str(), req.path.c_str(), req.remote_addr.c_str(), res.status);
+    SRV_INF("done request: %s %s %s %d\n", req.method.c_str(), req.path.c_str(), req.remote_addr.c_str(), res.status);
 
     SRV_DBG("request:  %s\n", req.body.c_str());
     SRV_DBG("response: %s\n", res.body.c_str());
Repository: vuejs/vue
Pull request: imporve:check the delete oparator in event expression

Fix: https://github.com/vuejs/vue/issues/4966



Changed files:
filename: src/compiler/error-detector.js
patch: @@ -8,6 +8,10 @@ const prohibitedKeywordRE = new RegExp('\\b' + (
   'super,throw,while,yield,delete,export,import,return,switch,default,' +
   'extends,finally,continue,debugger,function,arguments'
 ).split(',').join('\\b|\\b') + '\\b')
+const unaryOperatorsRE = new RegExp('\\b' + (
+  'delete,typeof,void'
+).split(',').join('\\s*\\([^\\)]*\\)|\\b') + '\\s*\\([^\\)]*\\)')
+const eventAttrRE = /^@|^v-on:/
 // check valid identifier for v-for
 const identRE = /[A-Za-z_$][\w$]*/
 // strip strings in expressions
@@ -30,6 +34,8 @@ function checkNode (node: ASTNode, errors: Array<string>) {
         if (value) {
           if (name === 'v-for') {
             checkFor(node, `v-for="${value}"`, errors)
+          } else if (eventAttrRE.test(name)) {
+            checkEvent(value, `${name}="${value}"`, errors)
           } else {
             checkExpression(value, `${name}="${value}"`, errors)
           }
@@ -46,6 +52,17 @@ function checkNode (node: ASTNode, errors: Array<string>) {
   }
 }
 
+function checkEvent (exp: string, text: string, errors: Array<string>) {
+  const keywordMatch = exp.replace(stripStringRE, '').match(unaryOperatorsRE)
+  if (keywordMatch) {
+    errors.push(
+      `avoid using JavaScript unary operator as property name: ` +
+      `"${keywordMatch[0]}" in expression ${text.trim()}`
+    )
+  }
+  checkExpression(exp, text, errors)
+}
+
 function checkFor (node: ASTElement, text: string, errors: Array<string>) {
   checkExpression(node.for || '', text, errors)
   checkIdentifier(node.alias, 'v-for alias', text, errors)

filename: test/unit/features/options/template.spec.js
patch: @@ -70,4 +70,15 @@ describe('Options template', () => {
     expect('invalid v-for iterator "2"').toHaveBeenWarned()
     expect('invalid expression: v-for="(1, 2) in a----"').toHaveBeenWarned()
   })
+
+  it('warn error in generated function (v-on)', () => {
+    new Vue({
+      template: `<div @click="delete('Delete')"></div>`,
+      methods: { delete: function () {} }
+    }).$mount()
+    expect('Error compiling template').toHaveBeenWarned()
+    expect(
+      `avoid using JavaScript unary operator as property name: "delete()" in expression @click="delete('Delete')"`
+    ).toHaveBeenWarned()
+  })
 })
Repository: nodejs/node
Pull request: test: fix test-buffer-zero-fill-cli to be effective

The test was useless for testing `--zero-fill-buffers` flag, which is what it was supposed to test.

1. `Buffer.allocUnsafeSlow(20)` is zero-filled regardless of the flag because it's from heap (<=64), not an alloc

2. 50 first calls to `Buffer.allocUnsafe(20)` were zero-filled regardless of the flag because they all come from the pool which was in the snapshot, and no real runtime alloc was made.

This PR fixes the test, so it now fails without the flag (as expected).

Changed files:
filename: test/parallel/test-buffer-zero-fill-cli.js
patch: @@ -14,6 +14,13 @@ function isZeroFilled(buf) {
   return true;
 }
 
+// We have to consume the data from the pool as otherwise
+// we would be testing what's in snapshot, which is zero-filled
+// regardless of the flag presence, and we want to test the flag
+for (let i = 0; i < 8; i++) {
+  assert(isZeroFilled(Buffer.allocUnsafe(1024)));
+}
+
 // This can be somewhat unreliable because the
 // allocated memory might just already happen to
 // contain all zeroes. The test is run multiple
@@ -22,7 +29,8 @@ for (let i = 0; i < 50; i++) {
   const bufs = [
     Buffer.alloc(20),
     Buffer.allocUnsafe(20),
-    Buffer.allocUnsafeSlow(20),
+    Buffer.allocUnsafeSlow(20), // Heap
+    Buffer.allocUnsafeSlow(128), // Alloc
     Buffer(20),
   ];
   for (const buf of bufs) {
Repository: ollama/ollama
Pull request: Added QodeAssist link to README.md

QodeAssist is using ollama to provide an AI-powered coding assistant plugin for Qt Creator

Changed files:
filename: README.md
patch: @@ -429,6 +429,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Headless Ollama](https://github.com/nischalj10/headless-ollama) (Scripts to automatically install ollama client & models on any OS for apps that depends on ollama server)
 - [vnc-lm](https://github.com/jk011ru/vnc-lm) (A containerized Discord bot with support for attachments and web links)
 - [LSP-AI](https://github.com/SilasMarvin/lsp-ai) (Open-source language server for AI-powered functionality)
+- [QodeAssist](https://github.com/Palm1r/QodeAssist) (AI-powered coding assistant plugin for Qt Creator)
 
 ### Supported backends
Repository: ggml-org/llama.cpp
Pull request: ggml: use noexcept overload for is_regular_file in backend registration

using noexcept std::filesystem::directory_entry::is_regular_file overload prevents abnormal termination upon throwing an error (as caused by symlinks to non-existant folders on linux)

fixes issue #18560

- Searched for existing PRs for this issue
- `GG_BUILD_LOW_PERF=1 bash ./ci/run.sh ./tmp/results ./tmp/mnt` passed successfully executing ci locally
- `bash ./ci/run.sh ./tmp/results ./tmp/mnt` fails `26/41 Test #26: test-jinja-py` with `ModuleNotFoundError: No module named 'jinja2'`, but succeeds after installing the missing python dependency jinja2 in the virtual environment. I assume this to be unrelated to this PR as the same behavior is observed without the commit.
- test-backend-ops results: `10872/10872 tests passed
  Backend ROCm0: OK
Backend 2/2: CPU
  Skipping CPU backend
2/2 backends passed
OK`

Changed files:
filename: ggml/src/ggml-backend-reg.cpp
patch: @@ -471,9 +471,10 @@ static ggml_backend_reg_t ggml_backend_load_best(const char * name, bool silent,
 
     int best_score = 0;
     fs::path best_path;
+    std::error_code ec;
 
     for (const auto & search_path : search_paths) {
-        if (std::error_code ec; !fs::exists(search_path, ec)) {
+        if (!fs::exists(search_path, ec)) {
             if (ec) {
                 GGML_LOG_DEBUG("%s: posix_stat(%s) failure, error-message: %s\n", __func__, path_str(search_path).c_str(), ec.message().c_str());
             } else {
@@ -483,7 +484,7 @@ static ggml_backend_reg_t ggml_backend_load_best(const char * name, bool silent,
         }
         fs::directory_iterator dir_it(search_path, fs::directory_options::skip_permission_denied);
         for (const auto & entry : dir_it) {
-            if (entry.is_regular_file()) {
+            if (entry.is_regular_file(ec)) {
                 auto filename = entry.path().filename();
                 auto ext = entry.path().extension();
                 if (filename.native().find(file_prefix) == 0 && ext == file_extension) {
Repository: vuejs/vue
Pull request: NonParsingTags should not be case-insensitive

In vue 2.0, the template is parsed by a Virtual DOM. The paring process is case-sensitive. For example, the VDOM can distinguish between `<Button>` and `<button>`. However, the function is `isNonParsingTag` is case-insensitive which shouldn't be.


Changed files:
filename: src/platforms/web/compiler/util.js
patch: @@ -4,15 +4,13 @@ import { makeMap } from 'shared/util'
 
 export const isUnaryTag = makeMap(
   'area,base,br,col,embed,frame,hr,img,input,isindex,keygen,' +
-  'link,meta,param,source,track,wbr',
-  true
+  'link,meta,param,source,track,wbr'
 )
 
 // Elements that you can, intentionally, leave open
 // (and which close themselves)
 export const canBeLeftOpenTag = makeMap(
-  'colgroup,dd,dt,li,options,p,td,tfoot,th,thead,tr,source',
-  true
+  'colgroup,dd,dt,li,options,p,td,tfoot,th,thead,tr,source'
 )
 
 // HTML5 tags https://html.spec.whatwg.org/multipage/indices.html#elements-3
@@ -22,6 +20,5 @@ export const isNonPhrasingTag = makeMap(
   'details,dialog,div,dl,dt,fieldset,figcaption,figure,footer,form,' +
   'h1,h2,h3,h4,h5,h6,head,header,hgroup,hr,html,legend,li,menuitem,meta,' +
   'optgroup,option,param,rp,rt,source,style,summary,tbody,td,tfoot,th,thead,' +
-  'title,tr,track',
-  true
+  'title,tr,track'
 )
Repository: facebook/react
Pull request: feat(eslint-plugin-react-hooks): update `engines` declaration

In preparation for the merging of the compiler plugin into this one (#32416), this change proactively updates the plugin's `engines` declaration to require Node versions greater than or equal to 18

BREAKING CHANGE

Changed files:
filename: packages/eslint-plugin-react-hooks/package.json
patch: @@ -31,7 +31,7 @@
   "main": "./index.js",
   "types": "./index.d.ts",
   "engines": {
-    "node": ">=10"
+    "node": ">=18"
   },
   "homepage": "https://react.dev/",
   "peerDependencies": {
Repository: facebook/react
Pull request: [ci] Upload release for easier debugging


Uploads the releases that were published in case to help with debugging or verifying a dry run.
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32492).
* __->__ #32492
* #32491

Changed files:
filename: .github/workflows/runtime_releases_from_npm_manual.yml
patch: @@ -117,3 +117,9 @@ jobs:
             --publishVersion=${{ inputs.version_to_publish }} \
             --skipPackages=${{ inputs.skip_packages }} ${{ (inputs.dry && '') || '\'}}
             ${{ inputs.dry && '--dry'}}
+      - name: Archive released package for debugging
+        uses: actions/upload-artifact@v4
+        with:
+          name: build
+          path: |
+            ./build/node_modules
Repository: facebook/react
Pull request: [ci] Fix discord notification title


fun times
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32491).
* #32492
* __->__ #32491

Changed files:
filename: .github/workflows/runtime_releases_from_npm_manual.yml
patch: @@ -50,7 +50,7 @@ jobs:
           embed-author-name: ${{ github.event.sender.login }}
           embed-author-url: ${{ github.event.sender.html_url }}
           embed-author-icon-url: ${{ github.event.sender.avatar_url }}
-          embed-title: "⚠️ Publishing release from NPM${{ inputs.dry && ' (dry run)' }}"
+          embed-title: "⚠️ Publishing release from NPM${{ (inputs.dry && ' (dry run)') || '' }}"
           embed-description: |
             ```json
             ${{ toJson(inputs) }}