Add management command for finding new version#1910
Conversation
Test results 6 files 1 254 suites 2m 28s ⏱️ Results for commit 084c1df. ♻️ This comment has been updated with latest results. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1910 +/- ##
==========================================
+ Coverage 88.25% 88.32% +0.07%
==========================================
Files 141 142 +1
Lines 6871 6887 +16
==========================================
+ Hits 6064 6083 +19
+ Misses 807 804 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
hmpf
left a comment
There was a problem hiding this comment.
See comment about user agent.
4754cc6 to
04ead9e
Compare
Fixed in #1908 , which is now merged |
johannaengland
left a comment
There was a problem hiding this comment.
I would suggest renaming the command to check_version to follow the pattern we already have established that is verb_noun
084c1df to
19133a2
Compare
|
| This will currently not do anything, but in the future you will be able to get | ||
| a notification in the frontend if there is a new release registered in the database that you haven't seen yet. |
There was a problem hiding this comment.
Make sure to note in #1882 to remove this comment when it is implemented



Scope and purpose
Fixes #1907
Adds a management command that looks for a new Argus release and optionally saves it in the database for future use
Contributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Argus can be found in the
Development docs.