Commit graph

7 commits

Author SHA1 Message Date
46fa824d42
🐛 Remove deprecated CI instruction 2024-02-22 13:46:45 +01:00
cb3d8fd5d6
🐛 Remove deprecated woodpecker ci conditions
Tag condition (when: event: tag) filters are not generalized to `ref`
instead of the old `tag` key. This switches them to the new version.

See
https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution
2024-01-11 11:17:47 +01:00
7b5b3e6e46
🦊 Migrate major woodpecker ci version
Migrated to newer woodpecker version requiring different pipeline
naming scheme, see https://woodpecker-ci.org/docs/migrations.
2024-01-11 09:25:23 +01:00
a8256100f9
🐛 Fix release automation naming scheme
Names for tags in this repo start with a `v` (e.g. `v0.3.1`) but the
release automation did not know about this and would create duplicate
tags without the preceding letter.
2023-08-25 20:47:14 +02:00
6b39e5e05a
🐛 Create dist package contents at root directory 2023-04-12 11:22:00 +02:00
dc68887091
Add automated tagged releases
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
ci/woodpecker/tag/woodpecker Pipeline was successful
Using woodpecker ci most of the release process is now automated.
That means as soon as a new version tag (e.g. `v0.2.3`) is pushed the
release process is started and will (if versions have been bumped
correctly) set up a new release on Gitea and Github simultaneously.

The release process will fail if changelog and program versions
mismatch, or the version has not been bumped in general.

The release contains the executable and some documentation, including
the README as a manpage-formatted gzip file which can be included in the
correct directory to enable a simple manpage for the program.
2022-11-10 14:58:16 +01:00
c925810889
Add woodpecker ci testing 2022-08-06 13:12:34 +02:00