Skip to content

fix(sbom): unparseable -> unparsable in the marker failure message - #5

Merged
livingstaccato merged 1 commit into
mainfrom
fix/sbom-message-spelling
Aug 27, 2026
Merged

fix(sbom): unparseable -> unparsable in the marker failure message#5
livingstaccato merged 1 commit into
mainfrom
fix/sbom-message-spelling

Conversation

@livingstaccato

Copy link
Copy Markdown
Member

Converges one word across the fleet.

pyvider's codespell rejects the variant spelling unparseable, so the eleven repositories that took the SBOM marker fix in the sweep carry unparsable. This repository merged the fix first and kept the original, leaving the same file differing across the workspace by one word in one error string.

No behaviour change — the string is only reached when a wheel's Requires-Dist cannot be parsed at all. bash -n clean.

With this, scripts/sbom_from_wheel.sh is byte-identical across every repository that has it, except for provide-foundation's comment describing the v0.4.3 incident in the first person, which is correct there and nowhere else.

pyvider's codespell rejects the variant spelling, and the eleven repositories
that took this fix in the sweep therefore carry `unparsable`. This repository
merged first and kept the original, so the same file now differs across the
fleet by one word in one error string.

Converging on the spelling that passes every gate in the workspace. No
behaviour change: the string is only reached when a wheel's Requires-Dist
cannot be parsed at all.
@livingstaccato
livingstaccato merged commit 0120256 into main Aug 27, 2026
11 checks passed
@livingstaccato
livingstaccato deleted the fix/sbom-message-spelling branch August 27, 2026 16:42
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.

1 participant