Most of the logic is in the action repository, and it'll get tested after I
merge this and attempt to release 2.0.0.4 by pushing the tag.
It uses an API Key I created for the FreckleEngineering user, which we'll
add as maintainer to all our packages, and stored as an Organization secret in
Freckle.
This does regress a little bit on the checks I'd typically do as part of
releasing (e.g. does it build on stackage-nightly), but I hope to bring those
into the normal CI workflow(s).
Additionally, if we can get a merge to main that signals a release to create
an appropriate tag, that would close the loop and automate everything
end-to-end.
Most of the logic is in the action repository, and it'll get tested after I merge this and attempt to release 2.0.0.4 by pushing the tag.
It uses an API Key I created for the FreckleEngineering user, which we'll add as maintainer to all our packages, and stored as an Organization secret in Freckle.
This does regress a little bit on the checks I'd typically do as part of releasing (e.g. does it build on stackage-nightly), but I hope to bring those into the normal CI workflow(s).
Additionally, if we can get a merge to
mainthat signals a release to create an appropriate tag, that would close the loop and automate everything end-to-end.