Skip to content

Clarify sequential_trace autorouter deprecation guidance - #844

Merged
imrishabh18 merged 2 commits into
mainfrom
fix/remove-sequential-trace-842
Sep 11, 2026
Merged

Clarify sequential_trace autorouter deprecation guidance#844
imrishabh18 merged 2 commits into
mainfrom
fix/remove-sequential-trace-842

Conversation

@imrishabh18

@imrishabh18 imrishabh18 commented Sep 11, 2026

Copy link
Copy Markdown
Member

The deprecated sequential-trace guidance recommends sequential_trace, but core disables both spellings by default. Document both as deprecated and direct users to the default autorouter with <autoroutingphase /> or <fanout /> elements as needed. Explain that temporary legacy support requires platformConfig.allowLegacyAutorouters: true.

Preserves both spellings in the public types and runtime schemas. Updates platform configuration guidance and regenerates the references.

Validation: all 511 tests pass; TypeScript and formatting checks pass. Ran all four required documentation generators.

Fixes #842.

@imrishabh18 imrishabh18 changed the title Remove sequential_trace autorouter presets Clarify sequential_trace autorouter deprecation guidance Sep 11, 2026
@imrishabh18
imrishabh18 merged commit 6bb594d into main Sep 11, 2026
4 checks passed
@imrishabh18
imrishabh18 deleted the fix/remove-sequential-trace-842 branch September 11, 2026 16:51
@tscircuitbot

Copy link
Copy Markdown
Contributor

Thank you for your contribution! 🎉

PR Rating:
Impact: Tiny

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecated sequential-trace guidance recommends sequential_trace, but core disables both

2 participants