8682f63aaa
Last time this ran, GoReleaser built an artefact with the wrong version - it didn't bump it correctly. It was meant to build 0.1.0-alpha.33, but it built 0.1.0-alpha.32 instead: https://github.com/dagger/dagger/runs/4860126130?check_suite_focus=true#step:7:94 This new approach is a simpler and more explicit tag bump by leveraging the semver-tool directly. A link to this utility is included in the comments. We version it in this repository so that it is all self-contained. We also use the gh CLI tool directly, instead of a GitHub Action that hides the implementation detail behind Typescript. We now have two very simple gh CLI invocations that do all that. While we still use the https://github.com/lewagon/wait-on-check-action GitHub Action to wait on running checks, and abort if any check failed, I didn't want to bundle that improvement into this PR - it's already big enough. As a meaningful improvement, we should have a Dagger package that bumps versions. It would have been so much easier to use that Dagger package. That implies us switching our GitHub Actions to Dagger, which we should totally do. Small steps ftw! Next step: run 0.1.0 release manually Step 2: run 0.2.0-alpha.1 release manually Step 3: wait for 0.2.0-alpha.2 to be produced automatically, tomorrow. Pair: @aluzzardi Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk> |
||
|---|---|---|
| .dagger/env | ||
| .github | ||
| client | ||
| cmd | ||
| compiler | ||
| cue.mod/pkg | ||
| docs | ||
| environment | ||
| keychain | ||
| mod | ||
| pkg | ||
| plan | ||
| plancontext | ||
| solver | ||
| state | ||
| telemetry | ||
| tests | ||
| util | ||
| version | ||
| website | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser.yml | ||
| .markdownlint.yaml | ||
| doc.go | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| install.ps1 | ||
| install.sh | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| semver | ||
| tracing.compose.yaml | ||
| universe | ||
Dagger
Dagger is a portable devkit for CICD.
Using Dagger, software teams can develop powerful CICD pipelines with minimal effort, then run them anywhere. Benefits include:
- Unify dev and CI environments. Write your pipeline once, Dagger will run it the same everywhere.
- Reduce CI lock-in. No more re-writing everything from scratch every 6 months.
How does it work?
- Automate actions with your favorite programming language. No proprietary SDK: just regular shell, Go, Javascript, Python...
- Reuse actions from a large and growing catalog.
- Tie it all together in CUE - a revolutionary declarative language invented at Google. No more YAML hell!
- Test and debug instantly on your local machine. No more waiting 10min to catch a typo.
- Run your pipelines on any Docker-compatible runtime, for maximum portability. This means most modern CI runners can run Dagger out of the box.