chore: register 5.0 as the current version - #35
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Registers API Platform 5.0 in the documentation site and makes it the version served at
/docs/.Changes, in the order the release skill in this repository lists them:
docs-versions.txt: add5.0as the first line.current-version.txt:4.3becomes5.0.hugo.toml:defaultVersionanddefaultVersionPathbecome5.0andv5.0, and a new[[params.versions]]block goes above4.4.config/_default/menus.tomlis not edited by hand. The deploy workflow inapi-platform/docsrunstools/get-docs.shandnode tools/menu.mjson every build, so the menu is regenerated there.Do not merge before
api-platform/corehas a5.0branch.tools/get-core-docs.shrunsgit fetch --depth=1 origin $versionagainstapi-platform/corefor every entry ofdocs-versions.txt. Core hasmainand4.4today, so merging this first makes the deploy fail on the5.0entry. Theapi-platform/docsside is ready: its5.0branch exists and matchesmain.The matching Caddy change is in api-platform/website#706.