The latest version is currently obtained from the info branch. This works fine but adds a lot of complexity to the Azure build pipeline.
The same information can be obtained directly from the GitHub Releases API, either from the release title or from the tag associated to it.
In summary:
GET https://api.github.com/repos/fernandreu/office-ribbonx-editor/releases/latest
Accept: application/vnd.github.v3+json (optional)
Users will keep using the info branch until they update the tool manually, so the build pipeline behaviour should not be changed for a while (e.g. a few major releases after this gets implemented, or a full year).
The latest version is currently obtained from the
infobranch. This works fine but adds a lot of complexity to the Azure build pipeline.The same information can be obtained directly from the GitHub Releases API, either from the release title or from the tag associated to it.
In summary:
Users will keep using the
infobranch until they update the tool manually, so the build pipeline behaviour should not be changed for a while (e.g. a few major releases after this gets implemented, or a full year).