Add instructions for publishing new releases #52
Merged
Conversation
This file contains 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
|
Looks great, thanks @willGraham01. I made a couple of tiny changes to match the formatting of the rest of the website (and stop sphinx complaining). Not sure why the action is failling. |
|
The tool used to generate the custom 404 page doesn't work on sphinx 7.2.0: Pinned the sphinx version to 7.1.0 and raised #53 to track. |
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.
Description
What is this PR
Why is this PR needed?
Standardise the methods we use to create new package releases.
What does this PR do?
Adds instructions for publishing a new release to the developer documentation.
Does this PR require an update to the documentation?
Meta-question.
Checklist: