diff --git a/README.md b/README.md index f251439..ff3531e 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ ```yaml - name: Hello - uses: dagger/dagger-for-github@8.0.0 + uses: dagger/dagger-for-github@v8.1.0 with: module: github.com/shykes/daggerverse/hello call: hello --greeting Hola --name Jeremy @@ -28,7 +28,7 @@ ```yaml - name: Integration Test - uses: dagger/dagger-for-github@8.0.0 + uses: dagger/dagger-for-github@v8.1.0 with: workdir: db-service verb: run @@ -55,3 +55,10 @@ By setting the version to `latest`, this action will install the latest version | `args` | Arguments to pass to CLI | false | '' | | `call` | Arguments to pass to CLI (Alias for args with verb:call) | false | '' | | `shell` | Arguments to pass to CLI (Alias for args with verb:shell) | false | '' | + +### All output variables + +| Key | Description | +| ---------- | ----------------------------------------------------------- | +| `stdout` | The standard output of the Dagger command | +| `traceURL` | Dagger Cloud trace URL | diff --git a/RELEASING.md b/RELEASING.md index 1cdbc0b..24e6977 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -22,12 +22,14 @@ separate `v8` tag. Should automatically get `v8`, `v8.0`, `v8.0.0` as well as ```console # Find the latest released patch https://github.com/dagger/dagger-for-github/releases -# or via the `gh` CLI. Use that to figure out the NEXT_PATCH_VERSION. +# or via the `gh` CLI. Use that to figure out the NEXT_VERSION. gh release view --repo dagger/dagger-for-github --json tagName,publishedAt +NEXT_VERSION=vX.Y.Z # e.g. v1.2.3 + # Sign the tag, using the date as the comment, e.g. 2024-07-22 -git tag --sign -m $(date '+%Y-%m-%d') -git push origin #shouldn't need to force since new tag +git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION +git push origin $NEXT_VERSION #shouldn't need to force since new tag ``` - [ ] Create a new release from the patch tag (auto-fill release notes via the