Updating a Package

Instructions for how to update your mod on Thunderstore

Packages can be updated with new versions (you cannot modify existing versions) through the same page that you uploaded the original package.

  • Unzip your original package.

  • Add or modify your README.md, CHANGELOG.md, code, and other assets.

  • Modify the manifest.json file's version_number field to a higher version number. Do not modify the name field or it will be uploaded as a new package instead of updating the old one.

  • Upload it again under the same Team (otherwise it will be uploaded as a new package instead of updating the old one).

Example of modifying the manifest.json:

{
    "name": "ExamplePackage",
    "version_number": "1.0.0",
    "website_url": "",
    "description": "This is an example",
    "dependencies": []
}
{
    "name": "ExamplePackage",
    "version_number": "1.0.1",
    "website_url": "",
    "description": "This is an updated example!",
    "dependencies": []
}

Package versions are immutable! Once a version is successfully uploaded, it can no longer be edited. Any further changes (including README.md edits) will require uploading a new version. Immutability is required for the ecosystem to offer conflict-freeness guarantees and efficient caching.

Changelog

Thunderstore supports CHANGELOG.md files which use the same markdown as your README.md file.

Example:

## v3.0.0
- Added X feature
- Added Y feature
- Fixed Z bug

## v2.0.0
- Added X feature
- Fixed Y bug
- Fixed Z bug

## v1.0.1
- Fixed text formatting in `README.md`

## v1.0.0
- Full release
- Fixed X bug
- Fixed Y bug

##
<details><summary>Show pre-release updates</summary>

## v0.5.1
- Fix X bug

## v0.5.0
- Beta release
- Add X feature
- Fix Y bug

## v0.1.1
- Fix X bug

## v0.1.0
- Alpha release

</details>

Last updated

Was this helpful?