[rush reporter][R9] Complete Rush 6 reporter and plugin migration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nodejs, typescript
- Domain
- build-system, devtools
Research direction
Start with parent issue #5858 and the blocked issues #5977, #5979, #5980, and #5981, then review the Rush reporter and rushd cutover described here. Done means the acceptance criteria pass: compatibility is tested before plugin execution, both Rush 5 and Rush 6 behavior are covered, the legacy fallback remains documented and tested, and the default flip is reversible.
Written by the indexing model from the issue text.
Description
Parent: #5858
Blocked by: #5977, #5979, #5980, #5981; coordinated with #5900
Goal
Execute the daemon-aligned Rush 6 reporter cutover after the opt-in path and compatibility gates are proven.
Scope
- Deprecate and remove
ILogger.terminalandRushSession.terminalProviderin the major release. - Gate incompatible plugins before
apply()with the structured migration diagnostic. - Retain the legacy renderer,
AlreadyReportedErrorbridge, verbosity aliases, andRUSH_REPORTER=legacyemergency fallback for at least one major. - Enable default reporter selection and environment-based agent selection in coordination with the rushd client/default flip.
- Validate daemon and in-process clients consume the same presentation-free event stream and derive the same exit behavior.
Acceptance criteria
- Plugin incompatibility is detected before plugin code executes.
- Rush 5 compatibility behavior and Rush 6 breaking behavior are explicitly tested.
- Reporter and rushd cutovers ship in the same major and pass #5900 transparency gates.
- The legacy emergency path remains documented, tested, and independent of the daemon fallback.
- Default flip is reversible to the opt-in behavior without protocol rollback.
DAG
Unblocks R11.
Part of #5858.
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 48
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/rushstack
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100