Closed RhysLees closed 2 years ago
@marcusmoore Is there anything else you think should be added?
@marcusmoore I can also close #63 with the same type of tag instead of saying Potentially Abandoned
Would it be worth adding to this PR or as a separate PR?
@RhysLees thanks for the updates and also peeking at additional issues that might be solved in a similar manner. A separate PR would be appreciated.
I'll review (and hopefully merge) this PR later this week.
Thanks again! 😄
@RhysLees thanks for the updates and also peeking at additional issues that might be solved in a similar manner. A separate PR would be appreciated.
I'll review (and hopefully merge) this PR later this week.
Thanks again! 😄
Awesome, thanks for Reviewing, I'll wait until this is merged then I'll make a PR for the other issue as it mainly uses the same code from this PR 😊
@RhysLees hey look at that!
This has been deployed. Thank you for your work on this 😄
@RhysLees hey look at that!
This has been deployed. Thank you for your work on this 😄
AYYYYYYY let's go! Thanks for your help in making it possible!
This PR adds the following:
nova_version to packages DB Table
Nova version to PackageDetailFrame if their latest stable release requires a Nova version
Current Nova Version Supported Label to Package cards if their latest stable release requires a Nova version that matches the major version specified in env
Adds Nova's current filter to tags and filters their latest stable release if it requires a Nova version that matches the major version specified in env
When a new major version of Nova is released all that is needed is to increase the version in .env from
NOVA_LATEST_MAJOR_VERSION=4
toNOVA_LATEST_MAJOR_VERSION=5
Closes #196