The scripting API doesn't follow a versioning spec like semver. Instead, functions and constants are added/modified/deleted as needed and pushed to the live updates repo.
One possible way to track versions is to add a permalink to the commit where an entry is added/deleted/modified. Functions and constants currently have an unused since property in their status property which could be used to store the link (this was the original plan but was not implemented for now). The link would not need to be updated every time there is a change in the source code, only when the entry's status changes (stable, deprecated, deleted, unstable).
The scripting API doesn't follow a versioning spec like semver. Instead, functions and constants are added/modified/deleted as needed and pushed to the live updates repo.
One possible way to track versions is to add a permalink to the commit where an entry is added/deleted/modified. Functions and constants currently have an unused
sinceproperty in theirstatusproperty which could be used to store the link (this was the original plan but was not implemented for now). The link would not need to be updated every time there is a change in the source code, only when the entry's status changes (stable, deprecated, deleted, unstable).