Add CI pipeline to check for outdated dependencies

[julian-bcw]

This action will run once per month, and check for outdated project dependencies. This won't affect pull requests, and instead the results can be found in the Actions tab.

Results are displayed in a chart that shows the outdated version being used, and the new version. Indirect dependencies are not included (since we have no control over them).

[codecov[bot]]

Codecov Report

Merging #787 (247f858) into main (87cdb45) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #787   +/-   ##
=======================================
  Coverage   62.56%   62.56%           
=======================================
  Files          87       87           
  Lines        6465     6465           
=======================================
  Hits         4045     4045           
  Misses       2224     2224           
  Partials      196      196           

Flag	Coverage Δ
unittests	62.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[julian-bcw]

Is there any way to notify us if there are any outdated dependencies, as going into the actions tab to check this will be easily forgotten. If there isn't we can just setup internally some kind of reminder to check the status of the job

The only thing I can think of would be to set up an email account for this and use this action to email the results: https://github.com/marketplace/actions/send-email

We would also need to setup GitHub Secrets for this, which I don't think I can do for this repo. Do you think it's worth doing @rokn? Setting up a reminder would probably be easier.

[rokn]

Is there any way to notify us if there are any outdated dependencies, as going into the actions tab to check this will be easily forgotten. If there isn't we can just setup internally some kind of reminder to check the status of the job

The only thing I can think of would be to set up an email account for this and use this action to email the results: https://github.com/marketplace/actions/send-email

We would also need to setup GitHub Secrets for this, which I don't think I can do for this repo. Do you think it's worth doing @rokn? Setting up a reminder would probably be easier.

Yeah I also saw this but it seems to be unnecessary hard to setup. Okay we'll just setup some remainders to check the job every month. Thanks!

[julian-bcw]

Could you please verify the comment and rebase with the main?

@svetlio8 Both are fixed now. Looks like my commit signing was setup for julian@bcw.com instead of julian@bcw.group.