-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Historical spec artifacts starting with v1.11 have broken CSS #1964
Comments
As I said in the Matrix Spec & Docs Authoring room, this should be fixed once we handle #1957. |
I just realized that the issue was in the spec-historical artifact, but not the spec artifact. That is due to the fact that we do not use the same version of Hugo for both. It is due to a big breaking change in Hugo 0.123.0. The last time that it was updated, only the version for the historical artifact was changed, which was probably not the intended goal. In any case we should probably use a CI variable to make sure that they stay in sync. |
This brought even more issues, as reported in the matrix-spec room:
And this is probably not the only broken link, I noticed others when working on #1984. An easy way to find them is to let htmltest do its job. They should all be fragments, so removing the We could have noticed that sooner if the historical build was also tested with htmltest. |
And the v1.12 spec-historical artifact has the same issues, since it was built in the same conditions. Edit: An easy way to fix the v1.11 and v1.12 spec-historical artifacts with no manual work required is to regenerate them with Hugo 0.117.0, like the non-historical artifacts. |
FWIW I regenerated them locally with hugo 0.117.0, and I checked that the only difference they have with the non-historical spec is the historical info box: |
as expected, this broke v1.13's release when shipping v1.12 too. |
Link to problem area: spec-historical of https://github.com/matrix-org/matrix-spec/releases/tag/v1.11
Issue
compared to:
Expected behaviour
Implied above.
The text was updated successfully, but these errors were encountered: