Snapshots are released frequently, making it hard to keep up when updating the pack. Parts of this process could do with some more/smarter automation.
The general process of creating a variant for a just-released snapshot:
If necessary, update targetVersions in main.ts to ensure the latest snapshot is included.
Perform a test build of the pack: node dist/main.js. Check for JS errors. Check for validation warnings.
Often, a bug from the pack has been fixed in the just-released snapshot. The build tool will produce a warning at step 2. To remedy the issue, add a version constraint to the fix in fixes.ts. This prevents the fix from being emitted for versions that don't suffer from the bug.
Once all the warnings/errors have been dealt with, the new variant can be created and published.
Build the pack with the correct version brand, e.g. node dist/main.js v2.18.
Add the new variant to Modrinth: node dist/publisher/main.js. Check that the changelog is correct for the current version (e.g. v2.18).
Update the version name and download link in the Download section. Check that the link is valid.
Update the table in the Statistics section. Check the stats with node dist/main.js --stats --latest-snapshot, then update the version name in the first column.
Snapshots are released frequently, making it hard to keep up when updating the pack. Parts of this process could do with some more/smarter automation.
The general process of creating a variant for a just-released snapshot:
targetVersionsin main.ts to ensure the latest snapshot is included.node dist/main.js. Check for JS errors. Check for validation warnings.fixes.ts. This prevents the fix from being emitted for versions that don't suffer from the bug.node dist/main.js v2.18.node dist/publisher/main.js. Check that the changelog is correct for the current version (e.g. v2.18).node dist/main.js --stats --latest-snapshot, then update the version name in the first column.