docs/PUBLISHING.md
Publishing a version of Amethyst requires incrementing all modified sub-crates and then publishing the sub-crates in the following order. You must comment out dev-dependencies when publishing.
Steps:
is:pr is:merged base:master merged:>=YYYY-MM-DDrender_sprite() so it uses the correct index into the rgba vector".vX.Y.Z, and push. For example: git tag v0.15.1 && git push origin HEAD --tags
[dev-dependencies] section from all Cargo.toml files and then commit. Here is an example of commenting out dev-dependencies.script/publish.sh from the workspace root.git revert HEAD.Draft a new release.
Amethyst X.Y.Z (fill in the version number).script/publish-docs.sh.†bors r+amethyst-starter-2d repo to use the new version*Could use more detail!
†Let's automate this!
Here is a snapshot of which crates depend on which others. This is no longer needed for publishing, since the order of publishing is implicit in publish.sh
amethyst_configamethyst_deriveamethyst_erroramethyst_core
dependencies:
amethyst_assets
dependencies:
amethyst_network
dependencies:
amethyst_window
dependencies:
amethyst_audio
dependencies:
amethyst_locale
dependencies:
amethyst_input
dependencies:
amethyst_controls
dependencies:
amethyst_rendy
dependencies:
amethyst_tiles
dependencies:
amethyst_ui
dependencies:
amethyst_utils
dependencies:
amethyst_animation
dependencies:
amethyst_gltf
dependencies:
Aka, amethyst
Dependencies:
amethyst_test
dependencies: