Pin dagger CLI to v0.2 (#81)

Browse source

Since we published https://github.com/dagger/dagger/releases/tag/v0.3.6
(Nov. 30, 2022), this action started downloading that version (i.e.
`latest`), which resulted in breakage, as described in the issue that
this fixes.

As soon as all tests pass and this gets the OK + merge, we should:
1. Cut a new release for this action (I am thinking v3.2.0)
2. Update the v3 tag to point to this new version

That should fix this for all existing GitHub Actions users without any
intervention on their part.

Fixes https://github.com/dagger/dagger-for-github/issues/80

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

...

This commit is contained in:

Gerhard Lazu 2022-12-06 19:39:50 +00:00 • committed by GitHub

parent 23fd2f48d1

commit 75549c92b9

No known key found for this signature in database

GPG key ID: 4AEE18F83AFDEB23

6 changed files with 13 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

dist/index.js generated vendored

View file

File diff suppressed because one or more lines are too long