Quick steps
- 01Read the changelog on the pack's detail page before updating.
- 02Check for breaking changes — they are called out in a prominent banner.
- 03If a breaking change affects your graph, read the migration notes.
- 04Update from the app's 'Installed packs' panel, not from the store.
- 05Pin to an older version in the app's pack settings if you need stability.
Immutable releases
Once a pack version is published, it never changes. The author cannot edit the code, the README, or the changelog of an already-published version. This is a hard constraint, not a convention.
Why? Because your graphs declare a dependency on a specific version. If that version could change silently, you'd have no way to know whether a graph you built last month still works today.
Changelog anatomy
Every pack detail page shows the changelog for the selected version. It is split into three parts:
| Section | Colour | Meaning |
|---|---|---|
| Added | green + | New nodes, options, or behaviours you can use |
| Changed | amber ~ | Existing behaviour that shifted — may require graph adjustments |
| Fixed | grey · | Bug corrections — should be safe to update |
Breaking changes are flagged with a warning banner above the changelog. A breaking change is any change that makes a graph built against an earlier version fail or behave differently without modification.
Compatibility range
The scorecard on every pack page shows Requires app. A pack specifies the minimum app version it needs — if your app is older, the pack won't install. Updates can raise this minimum, which is itself a breaking change and always appears in the breaking-changes section.
Version history
The View all versions link on every pack page takes you to the full version history. Each row shows:
- The version number and release date.
- The compatibility range for that version.
- A direct install link (for pinning to an older version).
Updating a pack
Updates are managed in the [fix]net app's "Installed packs" panel, not from the store. The store is for discovery; the app is for lifecycle management.
When an update is available, the app shows a badge. Before you tap Update:
- Read the changelog for the new version on the store page.
- Check whether any breaking changes affect nodes you're actively using.
- If you need the change — update. If you're mid-project and can't afford disruption — pin.
Related reading
- Build your first graph →
- [How versioning works in the [fix]store](/blog/how-versioning-works.html) (blog)