Updating Dagger Dependencies

[chrome ocean]

Hi all, sorry if this is a duplicate, but I couldn't really find anything on this, although I've only been messing around with Dagger (in terms of actually trying to use it) for a few hours so maybe it'd be self explanitory over time.
Let's say I have a repository and I start using Dagger to run tests locally and in a CI/CD pipeline.
Based on the examples for NodeJS/TypeScript, in the dagger folder there will be package.json, yarn.lock, etc.

Now let's say a few months pass by. I would assume at this point there will be updates to dependencies, and perhaps updates to Dagger which would require updated dependencies.
Are these handled automatically if you run some arbitrary Dagger command, or is there a specific command to update the dependencies?

[forest hedge]

dagger develop should be your friend to bring your whole module, including its dependencies, up to date most effectively for once you've updated your dagger CLI version.

That being said, @wheat wagon, @mild stone it seems there should be regular updates to any vendored packages like yarn that go along with Dagger releases, right?

There is also a lot of discussion here that is relevant. https://github.com/dagger/dagger/issues/8688

[chrome ocean]

Thanks for the information. I'll take a look.