[rush reporter][R11] Remove legacy reporter bridges in a later major
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reviewing parent issue #5858 and blockers #5982 and #5983; no files or tests are named in this issue. Define measurable adoption and canary criteria, then verify the full-major, telemetry, migration-documentation, and compatibility requirements before treating the deferred cleanup as done.
Written by the indexing model from the issue text.
Description
Parent: #5858
Blocked by: #5982, #5983, plus at least one full major of default use with no blocking canary regressions
Goal
Track the intentionally deferred cleanup after the reporter system has proven ecosystem adoption.
Scope
- Define measurable ecosystem/canary criteria for removing the legacy renderer.
- Remove the
AlreadyReportedErrorbridge only after migration criteria are met. - Remove obsolete primary-path
StreamCollatorplumbing while retaining the standalone package if other consumers still need it. - Remove temporary compatibility adapters and update protocol support policy as appropriate.
Acceptance criteria
- At least one full major has shipped with the new reporter defaults.
- Canary and compatibility telemetry show no blocking regressions.
- Migration documentation and release notes provide replacement guidance.
- Cleanup does not remove permanent verbosity aliases or required emergency/recovery behavior without a separate approved design.
DAG
Terminal node; later-major cleanup only.
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