VersionCheck enhancements #4964
Labels
difficulty-01-duckling
Issue where no particularly involved knowledge of the internal API is needed.
enhancement
Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope.
feature-settings
feature-version-check
good first issue
Want to contribute? That's a good place to start!
up-for-grabs
Use this label in conjunction with a difficulty level label, e.g. difficulty-02-ducky
user-interface
This issue explicitly relates to the visible interface of Rubberduck.
wpf
Issue is easier to resolve with knowledge of WPF/XAML
Justification
The
VersionCheck
feature is currently sending an asynchronous HTTP request to http://www.rubberduckvba.com/build/version/stable, which responds with the version number for the latest "green release".With the website's recent update, that version number is now coming straight from releases, through the GitHub API - rather than returning the assembly version of the Rubberduck.dll assembly depoyed to the website, it's now returning a version number parsed (using a simple regex) from the latest "green release" tag name - which must contain the version number in the format
v0.0.0
(orv0.0.0.0
).The website's
BuildController
has been updated to also provide a response to http://rubberduckvba.com/build/version/prerelease, which yields a version number parsed (using a simple regex) from the latest tag against the [next] branch - the tag name must contain the version number in the formatv0.0.0.0
(orv0.0.0
).Description
Let's enhance the
VersionCheck
settings to offer 3 settings:For back-compat, let's treat the existing "Check if a new version is available" setting as "Check if a new release build is available". This enhanced setting would probably look best with a combobox selection (currently a simple checkbox).
The text was updated successfully, but these errors were encountered: