Addon custom update at studios

General
1

Hey! Given that there are naming rules enforced for uploading and updating addons, I’m trying to figure out the best approach for custom studio-specific addons.

Currently, new custom addons are named like:
core 1.4.0+dev

If I upload an addon with the same name but different code, it replaces the existing one on all client machines? I think “No”

Is there a way to:

  • Use a secondary prefix or suffix (e.g., studio-specific tag) when creating a tag?
  • Version custom addons in a way that avoids conflict with official ones?

Looking for a clean strategy for studio-specific addon management

2

The addons should adhere to Semantic Versioning.

Typically, it can be

  • 1.4.0+lbsvfx.1
  • OR 1.4.0-lbsvfx.1
2 Likes
3

About the - vs + .
The thing is that according to semver, versions with - are considered older than versions without -.

Additionally, values after + in the name are considred metadata, and it doesn’t represent if the version is older or newer. but I think AYON should consider them when sorting the available addons in versions drop down menu in bundle settings.

1 Like
4

It has been fixed a few months ago.

Now we have this order :
1.0.8-custom.1 < 1.0.8 < 1.0.8+custom.1

1 Like