Backport to 1.10: bump Documenter to 1.15.0 (include several PRs) #60129
+269
−45
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fingolfin
commented
Nov 13, 2025
fingolfin
force-pushed
the
mh/backport-documenter-update-1.10
branch
from
38b3544 to
8bc8c88
Compare
A couple small fixes and cosmetic improvements to the Unicode table in the docs: * Most importantly, makes sure that the resulting object from the at-eval block is `Markdown.MD`, which which will be necessary for Documenter 1.0 (#47105). It also fixes the `Markdown.Table` structure -- each of the cells should be an array, not just a string, so it adds one more layer of nesting. * Cosmetically, center-aligns the characters, and wraps the latex commands in `<code>`
Currently mainly to test a few things on CI here, but will update this to an actual PR once 0.28.0 is out. --------- Co-authored-by: Lilith Orion Hafner <[email protected]>
fingolfin
force-pushed
the
mh/backport-documenter-update-1.10
branch
from
8bc8c88 to
b67c572
Compare
fingolfin
commented
Nov 13, 2025
The documentation builds can fail if the Julia source code is not properly in a Git repo (tarballs, Buildkite). This should ensure that Documenter knows which remote repository corresponds to the Julia source tree. Hopefully will fix JuliaCI/julia-buildkite#336
fingolfin
force-pushed
the
mh/backport-documenter-update-1.10
branch
from
1f1f77e to
44cdb79
Compare
fingolfin
changed the title
Member
|
I'll merge this into the backports branch. Worst case we can revert it. |
Member
|
I see the "don't squash" label here. @KristofferC Is it okay for me to regular-merge this into the backports branch? Or do we want to avoid having merge commits on the backports branch? |
Member
Author
|
I put the "no squash" on this because it technically backports four PRs, each in one commit. That said, for me personally it doesn't matter, but perhaps it does for some tooling? |
Member
Author
|
Oh and of course I also could now update it to go to Documenter 1.16, see #60132 ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Manual backport of several PRs to get Documenter to 1.15.0:
Actually I cheated: I built this using Julia 1.10.10 because I was unable to build from the release-1.10 branch. See #60128