Skip to main content

Versioning

Extensions allows versioning of each Extension so that the developer can test the Extension in Auravant during the development process and publish updates available to all users.

For this, it is only necessary to understand the following concepts:

  • Each Extension has a succession of Versions
    • The Version has an associated Status
  • Each Version has a succession of Commits

The Version is an instance of the Extension whose Status can be:

  • Development: The Version is in the development process, visible and accessible only by the developer from the marketplace.
  • Revision: The Version has been sent for revision so that the Auravant team can check it and publish it, request corrections, or reject it.
  • Production: The Version passed the revision and it was published. It is accessible by any user from the Auravant Marketplace.
  • Denied: The Version was rejected by the revision.
  • Down: The Version was shut down.

Commits are, as in Git, advances in the Extension's code. When changes are made to the code and you want to test them in Auravant, a new Commit is created with those changes.

Life cycle of an Extension​

When an Extension is declared, instantly Version 1.0 is created in Development status. The "1" corresponds to the Version number and the "0" to the Commit number. The first Commit contains the boilerplate, i.e., the minimum code that the Extension needs to initialize. From there, the developer will be able to upload a new code, creating a new Commit each time, obtaining Versions 1.1, 1.2, etc.

Moreover, the developer will be able to select and change, from all the Commits made, which one he/she wants to be assigned to the Version in Development status and access it from the Marketplace. That is to say that the code that will be executed when opening an Extension from the Marketplace will be the one from the selected Commit.

There can only be one Version in Development status.

Once the developer has sufficiently tested the Version and it is ready to be published, he must select "publish" from the Version options. There, the status will change to Revision and he/she will not be able to make any changes to the Version or its Commits. In turn, a new Development Version will be generated whose first commit will be the one selected in the previous Version.

  • If the Version in Revision status is not accepted, it will be set to Denied status and the developer will not be able to make any changes to it. The corresponding corrections must be made on the Development Version and it must be sent for revision again.

  • If the Version is approved, it will be assigned the Production status and will be accessible by all Auravant users from the Marketplace. In case a Production Version already exists, when the new Version is approved, the current Version will be removed and the new Version will go to Production status.

There can only be one Version in Production status.

In this way, a Development Version and a Production Version of the same Extension can coexist. All users will see the Production Version and the developer will see both Production and Development listed as two different Extension.