Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/joshuaKnauber/serpens_addon_market/llms.txt

Use this file to discover all available pages before exploring further.

The Serpens Addon Market tracks two distinct but related versioning concerns: the current released version of Serpens itself (recorded in version.json) and the per-entry Serpens compatibility tags that indicate which major version of Serpens a given addon, snippet, or package was built for. Understanding both is important both for consumers browsing the marketplace and for submitters preparing their listings.

​
version.json

The version.json file lives at the root of the repository and records the current stable release of the Serpens visual scripting addon, along with a summary of what changed in that release. This file is read by the marketplace frontend to display the latest Serpens version and changelog to users.
​
version
array of integers
The current Serpens release version expressed as a three-element array [major, minor, patch]. For example, [3, 1, 2] represents Serpens version 3.1.2.
​
content
array of strings
A list of changelog items for the current release. Each string is a short bullet describing a new feature, improvement, or fix included in this version.

​
Current version.json

{
  "version": [3, 1, 2],
  "content": [
    "Outputs for interface nodes",
    "Context Overrides",
    "Bugfixes",
    "See the documentation for a full changelog"
  ]
}

​
serpens_version Field on Entries

The serpens_version field appears on addon and snippet entries in addons.json and snippets.json. It is an integer — either 2 or 3 — indicating which major release of Serpens the entry targets:
  • 2 — The entry was created with Serpens 2.x and uses that version’s node API.
  • 3 — The entry requires Serpens 3.x. It may depend on nodes, features, or APIs that do not exist in Serpens 2.
Older entries may omit serpens_version entirely. These entries predate the field’s introduction and should be treated as implicitly compatible with Serpens 2.x. No Serpens 3-specific functionality should be assumed for entries that lack this field.
The version field on package entries in packages.json follows the same integer convention — 2 for Serpens 2.x packages and 3 for Serpens 3.x packages. The bot automatically sets version: 3 for all newly submitted packages. Some older package entries may omit this field if they were submitted before it was introduced.

​
Guidance for Submitters

When preparing your addon or snippet for submission, include the serpens_version field in the JSON payload you copy from Serpens if your work relies on Serpens 3.x features.
If your addon or snippet requires Serpens 3.x features — such as the Serpens 3 node graph API, context overrides, or interface node outputs — set "serpens_version": 3 in your addon JSON before submitting to the marketplace. This helps users quickly identify whether a listing is compatible with the version of Serpens they have installed.

Build docs developers (and LLMs) love

Get started for freeTalk to us