Automate deploy with GHA

[clairemcginty]

• standardizes on Sonatype for both stable releases + snapshots
• automates release via a dispatch workflow (automatically triggering a release on a tag/release doesn't work well with maven release plugin; it will automatically bump project version, commit that to GitHub, then push a tag. See more here)

Tested with dry-run and snapshot builds locally. I set the -DdryRun=true flag in the workflow build for now, so that we can run a test on GHA. Then we can remove the flag

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.65%. Comparing base (5f56efb) to head (ec26133).

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #946   +/-   ##
=========================================
  Coverage     91.65%   91.65%           
  Complexity      252      252           
=========================================
  Files            26       26           
  Lines           947      947           
  Branches         71       71           
=========================================
  Hits            868      868           
  Misses           52       52           
  Partials         27       27           

[RustedBones]

That's a nice process.
I suppose we have to select the branch when running the workflow. It's more convenient to run on master/main but that will probably mean we can't enable the branch protection rule.

If we want this extra security, we should create a release/vX.Y.Z branch, run the action from this one and then create a pull-request and a merge commit in the main branch

[RustedBones]

is this required ?

[clairemcginty]

it was for me, at least locally

[RustedBones]

why do we have an environment ?

[clairemcginty]

...Good question, the environment had already been created in GHA settings and is used in maven.yml so I just continued that pattern

[clairemcginty]

If we want this extra security, we should create a release/vX.Y.Z branch, run the action from this one and then create a pull-request and a merge commit in the main branch

oh, interesting idea! the only problem is that I don't know if the maven-release-plugin is sophisticated enough for this, but I can look into it