Issues with check_dependency_updates

[andrewtavis]

Terms

• I have searched all open bug reports
• I agree to follow activist's Code of Conduct

Behavior

In #724 we developed check_dependency_updates, but this workflow has proven to not work particularly well as seen in #1089 and #1011. Issues are:

• The data for the issue title isn't formatted
• The updates that would happen aren't added to the issue text
  • We'd like the full error text
• The frontend errors seem to not be being included

Ideally we'd have this workflow running every two months and we'd then get a report that would tell us which dependencies would cause new errors so that we can react to these changes.

From the original issue #724:

• We'll keep the current Dependabot warnings and react to them as needed
• We'll run a workflow every two months
• This workflow will update all dependencies to the next available minor release
• The backend and frontend checks will be ran such that new errors will be detected
• Results will be logged and new issues will be made to work on them
• This two month process will coincide with Code Night 🌙 such that we can work together to squash 'em all 🐞

Would be great if someone wanted to look into this! 😊