Update stale dependencies

[github-actions]

Updating dependencies to the latest stable versions

[dotemacs]

Almost...

Looking into it.

[dotemacs]

1. outdated.md needs to be removed before the PR step is made.
2. after running lein ancient upgrade, lein test is kicked off

Because the test run is kicked off automatically, no diff is made. PR coming up

[rm-hull]

Shouldn’t it also bump the versions in project.clj too?

[dotemacs]

Shouldn’t it also bump the versions in project.clj too?

There are couple of reasons behind this:

• deps.edn doesn't have a version number so I didn't look into it
• some steps are better done manually, for example I could look for a way to bump the version, but what number will the next release be in: x.y.z or x.y.z-SNAPSHOT or something else?

If I were to do this, maybe we can have a workflow that does this: when you create a branch for releasing, say release and you push any commit into it (even an empty commit) with a commit message release: x.y.z (anything after release: , is the next release version):

• it takes this x.y.z as the release number and checks out master
• bumps the version number in project.clj with x.y.z
• tags master with x.y.z & builds the jar and pushes it to Clojars
• if all the above steps go well, it cleans up by deleting the branch release

The above steps allow you to have flexibility to add any release number

Thoughts?

[dotemacs]

Also, please close this PR as the new one for dependency update won't be created if this one is present.

Thanks @rm-hull

[dotemacs]

Ah nice, the GitHub Action force pushed to this branch with all the updates

[dotemacs]

It looks like this is going to run every day, until merged