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.
Also added a changelog note to #2592.
Pre-release
Project.toml
CHANGELOG.md
, following the existing style (in particular, make sure that the change log for this version has the correct version number and date).make changelog
, to make sure that all the issue references inCHANGELOG.md
are up to date.[ci skip]
workflow_dispatch
trigger to check for any changes that broke extensions: https://github.com/JuliaDocs/Documenter.jl/actions/runs/11719039348The release
After merging the pull request, tag the release. There are two options for this:
[at]JuliaRegistrator register
on the GitHub commit.Either of those should automatically publish a new version to the Julia registry.
Once registered, the
TagBot.yml
workflow 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.