regression: malformed should_panic attribute input (accepted breakage; might need more downstream patches)

[BoxyUwU]

• https://crater-reports.s3.amazonaws.com/beta-1.91-2/beta-2025-09-21/gh/cre-chan.MCIR/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.91-2/beta-2025-09-21/gh/KijitoraFinch.Fuchu/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.91-3/beta-2025-09-21/reg/text_art_cn-0.3.1/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.91-3/beta-2025-09-21/reg/dinero-rs-0.33.3-dev/log.txt

[INFO] [stdout] error[E0539]: malformed `should_panic` attribute input
[INFO] [stdout]   --> src/frontend/parser/tiger_parser/token.rs:87:5
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[should_panic("Expecting char. Identifier found")]
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^----------------------------------^^
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    expected this to be of the form `expected = "..."`

[fmease]

Accepted breakage. Lang-FCP in #143808. Some patches were sent to downstream projects (#143808 (comment)) but it seems like not all projects linked in the issue description were included.

There's no obligation to create downstream patches, right? So should we just close this issue immediately without further action or prepare some out of kindness?

[BoxyUwU]

If the breakage was accepted with the understanding that all crates had been PR'd then it could make sense to send PRs to other crates that were affected. It might be worth grepping the beta crater runs for this error though because im not 100% confident this is all the crates, there might be a couple more.

[fmease]

@jdonszelmann @JonathanBrouwer Do you have the time and inclination to double-check if all regressed crates (in the list above and in the full report in #146902 (since they might contain more as Boxy suggested above)) have corresponding patches or issues?