Chore: Add dev options to pixi version config generator #57
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
Base automatically changed from
hotfix-versioned-code-content-handling
to
chore-website-v7-snapshot
January 15, 2024 13:06
Base automatically changed from
chore-website-v7-snapshot
to
chore-website-versioning
January 15, 2024 13:08
Base automatically changed from
chore-website-versioning
to
website-restructuring
January 15, 2024 13:09
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.
devand 'next-v8` branch, utilising GithHub rest API to fetch the latest commit's SHA for whichever dev branch selected during the script run.8.0.0-rcto bedevto match our newdevworking docs version.5b66fdf1SHA (https://pkg.csb.dev/pixijs/pixijs/commit/5b66fdf1/pixi.js) and do the same for the dev versions that we want to have on the docs, at least during this development period.