You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintainers prioritize PRs with a clear reviewer test plan — without it, review may be delayed.
2
+
Help reviewers verify this PR quickly.
3
3
4
-
Don't hard-wrap paragraphs: GitHub renders single newlines as <br>, so wrapped text shows as a narrow column. Write each paragraph or list item as one long line.
4
+
Maintainers prioritize PRs that include clear proof of work.
5
+
If a PR does not include enough validation detail to reproduce and verify the change efficiently, review may be delayed.
5
6
-->
6
7
7
-
## What this PR does
8
+
## Summary
8
9
9
-
<!-- What this PR does. Describe the change in prose, not by file or function names. -->
10
+
- What changed:
11
+
- Why it changed:
12
+
- Reviewer focus:
10
13
11
-
## Why it's needed
12
-
13
-
<!-- Why it's needed: the motivation, the problem being solved, or the user-facing benefit. -->
14
-
15
-
## Reviewer Test Plan
14
+
## Validation
16
15
17
16
<!--
18
-
How a reviewer can confirm this PR: reproduction steps, expected vs observed behavior, and evidence. CI runs on macOS, Windows, and Linux — Tested on is what you verified locally.
19
-
20
-
User-visible / TUI: Before/After with tmux-real-user-testing skill, screenshots, or a short recording.
21
-
Non–user-visible (refactor, types, docs): commands and output below; write N/A under Before/After.
22
-
-->
23
-
24
-
### How to verify
25
-
26
-
<!-- How you reproduced it and what a reviewer should confirm — steps if needed, expected vs observed behavior. Focus on outcomes; paste logs or test output when helpful. -->
27
-
28
-
### Evidence (Before & After)
29
-
30
-
<!-- User-visible / TUI changes: paste before-and-after screenshots, tmux logs, or video side by side. Non-UI changes (docs, refactor, types): N/A -->
17
+
Be concrete. Do not write only "tested locally".
18
+
Include the exact commands, prompts, outputs, logs, screenshots, or videos that prove the change was actually run and observed.
31
19
32
-
### Tested on
20
+
For user-visible changes, bug fixes, CLI / TUI behavior changes, or interaction changes, include key screenshots or a short video.
21
+
When possible, show before/after behavior.
33
22
34
-
| OS | Status |
35
-
| :--------: | :----: |
36
-
| 🍏 macOS ||
37
-
| 🪟 Windows ||
38
-
| 🐧 Linux ||
39
-
40
-
<!-- ✅ tested · ⚠️ not tested · N/A -->
41
-
42
-
### Environment (optional)
23
+
If helpful, use the `e2e-testing` skill to gather stronger end-to-end validation evidence.
24
+
-->
43
25
44
-
<!-- Local runtime: e.g. npm run dev, Docker/Podman sandbox, seatbelt. N/A if only unit tests. -->
if [[ -z "${ALIYUN_OSS_ACCESS_KEY_ID}" || -z "${ALIYUN_OSS_ACCESS_KEY_SECRET}" ]]; then
435
+
echo "::error::Missing Aliyun OSS credentials. Set ALIYUN_OSS_ACCESS_KEY_ID and ALIYUN_OSS_ACCESS_KEY_SECRET in the production-release environment secrets."
436
+
exit 1
437
+
fi
438
+
439
+
ossutil config \
440
+
-e "${ALIYUN_OSS_ENDPOINT}" \
441
+
-i "${ALIYUN_OSS_ACCESS_KEY_ID}" \
442
+
-k "${ALIYUN_OSS_ACCESS_KEY_SECRET}" \
443
+
-L EN \
444
+
-c "${RUNNER_TEMP}/.ossutilconfig"
445
+
389
446
- name: 'Publish @qwen-code/qwen-code'
390
447
working-directory: 'dist'
391
448
run: |-
@@ -400,37 +457,150 @@ jobs:
400
457
env:
401
458
NODE_AUTH_TOKEN: '${{ secrets.NPM_TOKEN }}'
402
459
403
-
- name: 'Verify Standalone Archives'
404
-
run: |-
405
-
npm run verify:installation-release -- --dir dist/standalone
for asset in install-qwen-standalone.sh install-qwen-standalone.ps1 install-qwen-standalone.bat uninstall-qwen-standalone.sh uninstall-qwen-standalone.ps1 SHA256SUMS; do
0 commit comments