#dagger update, upgrade, etc
kindred radish
Mentioning here since dependencies and core install/update commands are involved.
I'm still trying to understand the constellation of issues here.
#daggernauts message related from @light tulip
I have the same issue. I would like to automatically update my Module dependencies with renovate or dependabot.
I tried to update to the "latest" version. E.g. dagger update github.com/sagikazarmark/daggerverse/helm@latest
This did not work.
To run renovate properly I'd need to get the latest version of a module on Daggerverse.
This, because I have to know about the new version before I run dagger update
Is there an API or URL providing this information? (Getting the target of the link "Go to latest version" is no very useful)
Thanks!
proper gust
yeah honestly we just need a proposal for what the new behavior should be
i had an idea that we should add --patch/--minor/--major flags to update that would allow all the tags to bump to those
the behavior right now is that we just bump the pins
but also maybe we need full on version selectors? dunno
I'm happy to write some options down when I'm back from PTO?
fossil owl
Is it realistic to have the behavior be different between branches and tags?
If the requested version was a tag -> update defaults to updating to the latest available tag
If the requested version was a branch -> keep the current behavior of updating to tip of the branch
proper gust
If the requested version was a tag -> `update` defaults to updating to the lates...
mm agree that that's better than today - but I wonder if it's not enough? e.g. what if I really want to not upgrade it? do we need a version specifier to say, only this version, or this range of versions, etc.
fossil owl
mm agree that that's better than today - but I wonder if it's not enough? e.g. w...
We could add those as opt-in flags
But if we agree on the default behavior, then we could make that change first, then add more options over time
Mostly I was wondering if there was any adverse reaction to treating branches & tags differently
proper gust
Mostly I was wondering if there was any adverse reaction to treating branches & ...
mmm yeah I think we probably should
I think the main change we'll need is a bit of a format change to dagger.json, where as well as the pin, we track whether we installed as a branch or tag (shouuuuld be pretty easy, we can just track the fully resolved ref)
once we've done that, we can change cli behavior as we like