[FEAT] release / docker ci pipeline

[dni]

the goal of this PR is to run these action on a new tag:

• create a github release and autogenerate release notes on tagging
• release a dockerimage on dockerhub for that tag and latest
• can manually run docker publish on custom tag

BREAKING

in the future we will use docker pull lnbits/lnbits instead of lnbitsdocker/lnbits-legend

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b711137) 59.23% compared to head (03e704f) 59.24%.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1907      +/-   ##
==========================================
+ Coverage   59.23%   59.24%   +0.01%     
==========================================
  Files          60       60              
  Lines        8951     8951              
==========================================
+ Hits         5302     5303       +1     
+ Misses       3649     3648       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[motorina0]

are we still planning to support tags of the form v0.11.rc0?

[dni]

we could consider switching to v as it is the default on github

v0.0.0
or 0.0.0

[motorina0]

I meant the rc0 at the end. The regex only supports digits.

[dni]

currently we don't have it in on-tag. we could add it. but i think rc could be an expection where we do it manually in the GUI

[motorina0]

The image on https://hub.docker.com/u/lnbits was Updated 4 moths ago.

Can we get the flow to run for this branch?

• rebase dev
• relax tag regex
• create trial tag on this branch. Ex: dec-20-2023?
• revert tag relax regex

[dni]

The image on https://hub.docker.com/u/lnbits was Updated 4 moths ago.

Can we get the flow to run for this branch?

* rebase dev

* relax tag regex

* create trial tag on this branch. Ex: `dec-20-2023`?

* revert tag relax regex

i dont really think that adds much, i would just switch the docker with the 0.12.0 release

if we want we could manually run older tags via github actions GUI and push them like that.

[motorina0]

i dont really think that adds much, i would just switch the docker with the 0.12.0 release

if we want we could manually run older tags via github actions GUI and push them like that.

Its good to test before we merge.