Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin dagger CLI to v0.2 #81

Merged
merged 1 commit into from
Dec 6, 2022
Merged

Conversation

gerhard
Copy link
Member

@gerhard gerhard commented Dec 6, 2022

Fixes #80

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.

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

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:
- dagger#80

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
@gerhard gerhard marked this pull request as ready for review December 6, 2022 19:38
@gerhard gerhard merged commit 75549c9 into dagger:main Dec 6, 2022
@gerhard gerhard deleted the pin-to-dagger-cli-v2 branch December 6, 2022 19:39
jpadams pushed a commit that referenced this pull request Nov 13, 2023
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 #80

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rollback breakage caused by Dagger CLI 0.3 release
2 participants