Record Workshop versions in Drone changelogs and retire local sending
This commit is contained in:
@@ -38,3 +38,22 @@ dialog. Select it before publishing.
|
||||
|
||||
This directory holds publishing artwork separately from game resources, so the
|
||||
PNG does not need Enfusion texture metadata or inclusion in the runtime PAK.
|
||||
|
||||
## Recording the published version
|
||||
|
||||
The project `.gproj` does not store the Workshop release version. Workbench stores
|
||||
it as `asset.version` in its local publishing `manifest.json`; the top-level
|
||||
`version` is the manifest schema. The latest recorded published version is in
|
||||
the preamble of [CHANGELOG.md](../CHANGELOG.md).
|
||||
|
||||
After a successful Workshop upload, run
|
||||
`python3 tools/workshop_changelog.py --published` to copy the version into
|
||||
`CHANGELOG.md`. The default manifest path
|
||||
targets this Linux/Proton Workbench installation; `--manifest PATH` overrides it.
|
||||
Running without `--published` only shows the bundled version. The helper does not
|
||||
publish or verify the online Workshop revision, so compilation alone is not enough
|
||||
to record a release as published.
|
||||
|
||||
Add the player-facing changes to the newest changelog entry, commit all intended
|
||||
source and changelog changes, then push. Drone includes the recorded version in
|
||||
the Discord changelog. See [the notification workflow](../docs/discord-changelog-ci.md).
|
||||
|
||||
Reference in New Issue
Block a user