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

✨ Support latest as the default option for the version input #114

Closed
purpleclay opened this issue Apr 4, 2024 · 0 comments · Fixed by #115
Closed

✨ Support latest as the default option for the version input #114

purpleclay opened this issue Apr 4, 2024 · 0 comments · Fixed by #115

Comments

@purpleclay
Copy link
Contributor

What are you trying to do?

I want to stay in sync with the latest version of Dagger while using the GitHub action. However, I have to explicitly set the version to '', which isn't a great developer experience. The version input should default to latest and reflect this in the script and documentation.

Many other GitHub actions use this approach.

Why is this important to you?

Keeping in sync requires manual updates of my GitHub workflows or setting the version to ''. If I am to be explicit, I would prefer to put the version as latest within my workflows.

How are you currently working around this?

I have to manually update my workflows with the version of Dagger that I want.

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 a pull request may close this issue.

1 participant