New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Check the target pro version #2

Open

steveoh opened this issue Mar 29, 2018 · 1 comment

Owner

steveoh commented Mar 29, 2018

Currently, the update only looks at the addin version when knowing to update. Check the pro version

Pro release numbering is meaningful 2.1 vs 2.0 means that 2.1 adds new functionality in a non-breaking way. 3.0 would be a breaking change compared to 2.x. So, don't update if 1) it's a major version change or 2) probably not if it's a minor version change either as that could use new APIs that don't exist on that machine

Contributor

green3g commented Apr 3, 2018

I think having a file, like proversion-2.1.0 uploaded next to the .addinx release is reasonable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment