> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/sharing-mods/updating-published-mods.md).

# Updating Published Mods

It's possible to make changes to mods so that your team can access those updated features as well. 

### Incrementing the Version Number

When updating a published mod, it’s best practice to increment the version number to indicate the kind of change made:

For example:

* Increment Patch version (for bug fixes): 1.2.3 → 1.2.4
* Increment Minor version (for new features): 1.2.3 → 1.3.0
* Increment Major version (for backward incompatible changes): 1.2.3 → 2.0.0

Incrementing the version number conveys two primary benefits:

* PixieBrix and users know it’s a new version
* You can track changes made across versions, and/or revert to a previous version

### Staging Mod Updates

When making major changes to a mod, it can be helpful to make a separate mod so you don’t break anything on the copy users currently have.

You can then copy changes from the updated mod to the live mod in the Workshop. Just make sure to change the version number and mod id!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pixiebrix.com/developing-mods/sharing-mods/updating-published-mods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.