Routes containing colons generate incorrect type-import paths
For a path such as /stuff:action, the generated type filename used a Unicode ratio character while the import retained a literal colon, leaving the handler argument typed as any.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1619
- Reporter
- dissemond-bitside
- Reported
- April 2, 2026
- Reported version
- 2.4.0
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2026
- Classification confidence
- High
- Chronology confidence
- High
- Accepted correction
- PR #1620
- First fixed release
- 2.5.0
- Report to release
- 1.64 elapsed daysReport: 2026-04-02T02:36:22Z; corrected publication: 2026-04-03T17:57:55.215Z.
Historical test demonstration and reproducible commands
Finding
This was a genuine regression, but it occurred in September 2025 rather than 2026.
Evidence trail
Origin
Exact origin: 8f0d2d20, committed September 3, 2025; first affected release 1.4.5. A Windows-path compatibility change sanitized the generated filename but did not apply the same transformation to the route file’s type import.
Source history and behavioral evidence
The introducing change and the later fix are symmetrical: one transformed the output filename; the other made the generated import use the same safe-path function. The fix includes the colon-route reproduction.
Release chronology
The mismatch first shipped in 1.4.5. It was corrected in 2.5.0 one day after the report.