chore(ci): releases

[kristof-mattei]

• Docker container is built on every PR, not published.
• Upon accepting PR, changelog is generated + new tag.
• New release is published with ^ changelog + tag
• New tag kicks off Docker container build + publish for v{x}, v{x.y}, v{x.y.z} and latest

[github-actions]

Test results for Rust

305 tests  ±0   305 ✅ ±0   5s ⏱️ ±0s
  4 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 7f885ae. ± Comparison against base commit 73b3442.

♻️ This comment has been updated with latest results.

[esatterwhite]

The binary and container should be built and released from what is on main after it has merged. We don't release from prs or branches

We don't need merge commits

[esatterwhite]

This is very much outside the way the company has managed releases.
We need to figure why there is such a disconnect with this repository, figure out how we can bring this closer to our current standards, and determine what from this and actually neccesary.

[gjanco]

This is very much outside the way the company has managed releases. We need to figure why there is such a disconnect with this repository, figure out how we can bring this closer to our current standards, and determine what from this and actually neccesary.

We discussed this in the Innovation Meeting Thursday. There was concern that malicious code could be run in Jenkins when we accept a PR. GH Actions was brought up as a good alternative (Phil will probably be moving vector/edge there as well).

[Shearerbeard]

Closed - stale