[x] Update CHANGELOG.md, following the existing style (in particular, make sure that the change log for this version has the correct version number and date).
[x] Run make changelog, to make sure that all the issue references in CHANGELOG.md are up to date.
[x] Check that the commit messages in this PR do not contain [ci skip]
mortenpi
commented
5 months ago
I was hoping that we'd get #2378 in, but it looks like there's a regression there. So let's not block the release anymore.
Pre-release
[x] Change the version number in
Project.toml[x] Update
CHANGELOG.md, following the existing style (in particular, make sure that the change log for this version has the correct version number and date).[x] Run
make changelog, to make sure that all the issue references inCHANGELOG.mdare up to date.[x] Check that the commit messages in this PR do not contain
[ci skip][x] Run regression-tests workflow using a
workflow_dispatchtrigger to check for any changes that broke extensions: https://github.com/JuliaDocs/Documenter.jl/actions/runs/8677920503The release
[x] After merging the pull request, tag the release. There are two options for this:
[at]JuliaRegistrator registeron the GitHub commit.Either of those should automatically publish a new version to the Julia registry.
Once registered, the
TagBot.ymlworkflow should create a tag, and rebuild the documentation for this tag.These steps can take quite a bit of time (1 hour or more), so don't be surprised if the new documentation takes a while to appear.