Andrew Poelstra 6b9d76db7a Merge rust-bitcoin/rust-bitcoin#2050: CI: add an automated github releases on new tags ... c34c709681 CI: add an automated github releases on new tags (Einherjar) Pull request description: Creates a `gh-release.yml` that runs on every new tag using the [`ncipollo/release-action`](https://github.com/ncipollo/release-action), which is one of the recommended actions after [GitHub's official `actions/create-release`](https://github.com/actions/create-release) was archived. The idea is to just have a release with the source code, no binary (although if wanted I can add that as well). A little bit of context: tcharding told me yesterday at TABConf that he copied manually all commits titles to the release notes somewhere (I think in crates.io?). This is an easy way to do it, just copy from the GitHub release. Finally, it is also positive to generate Releases from Tags since this increases the exposure of the repo (GitHub is highly social) while also signaling maturity. Here's an [example](https://github.com/oven-sh/bun/releases/tag/bun-v0.8.1) that I've found in a non-related repo that has the same `generateReleaseNotes: true` as this PR proposes <img width="857" alt="image" src="https://github.com/realeinherjar/rust-bitcoin/assets/136860407/41789514-8abf-4f58-b7ca-d2c352346923"> ACKs for top commit: apoelstra: ACK c34c709681 tcharding: ACK c34c709681 Tree-SHA512: 06bc0276b5aca95e19965eadb79d0a4cf8606b222dce37f095247196fcac023458c34e35cf34fa2344bc274063e642b93b05dc796a27179567052c58ac4bc27a		2023-09-27 13:55:46 +00:00
..
fuzz.yml	Bump actions/upload-artifact from 2 to 3	2023-09-11 10:17:32 +00:00
gh-release.yml	CI: add an automated github releases on new tags	2023-09-10 19:21:22 -03:00
kani.yml	Bump model-checking/kani-github-action from 0.36 to 0.37	2023-09-25 10:34:39 +00:00
release.yml	Bump actions/checkout from 2 to 4	2023-09-09 15:26:36 +00:00
rust.yml	Merge rust-bitcoin/rust-bitcoin#2060: fix(CI): `rust-toolchain` stable	2023-09-10 21:10:17 +00:00