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

🐞 default version is too old #168

Closed
levlaz opened this issue Dec 27, 2024 · 4 comments
Closed

🐞 default version is too old #168

levlaz opened this issue Dec 27, 2024 · 4 comments

Comments

@levlaz
Copy link

levlaz commented Dec 27, 2024

What is the issue?

If I don't explicitly set the version number, it seems to want to use 0.13.7 for some reason, can we make this latest somehow?

https://github.com/levlaz/snippetbox/actions/runs/12521681484/job/34929042207

Dagger version

dagger v0.15.1 (registry.dagger.io/engine:v0.15.1) darwin/arm64

Steps to reproduce

No response

Log output

No response

@jedevc
Copy link
Member

jedevc commented Jan 6, 2025

The default version to pull is based on the version of the action - if you pin the action to v6.15.1, you always get the same version of dagger: v0.13.7.

You can specify to always get the latest version, by using the version arg documented in the README.

@sw360cab
Copy link

@jedevc in case of a local module call, is there a way to tell an action to use the same version of the module itself?
It happened to me different failures of actions because of a simple mismatch between Dagger version in local module (likely updated), and the Dagger version in the github action (forgot to update/sync version).

IMHO, It should be possible to instruct the actions to "use the same version of what is in dagger.json"
What do you think/suggest?

@jedevc
Copy link
Member

jedevc commented Mar 27, 2025

@sw360cab, yup that sgtm - I'd like that feature. See #138, where it was also proposed.

@jedevc
Copy link
Member

jedevc commented Mar 27, 2025

Also gonna close this, from 8.0.0 the version is now not tied to the dagger version - it's not required as an explicit parameter.

@jedevc jedevc closed this as completed Mar 27, 2025
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

No branches or pull requests

3 participants