#Typescript yarn deps issue
1 messages · Page 1 of 1 (latest)
I don't think it's a good idea to force users to use a specific package manager, most already got their habit and dagger should not change that, instead it should just keep their expererience as smooth as possible
fyi @bleak acorn @solar wind
also @cloud hearth since he helped manage when we hit this before
Yarn is great but sometime super unstable, also the workspace manager isn't as great at go.work
right agreed - but it looks like we're in a position of needing to run a hotfix release today
I remember having issues with yarn while everything was fine with npm
Oh I see, until v0.12, I missread
My bad
yeah yeah
Yeah that's perfectly fine to do that
i don't wanna estimate the time to v0.12 too much, but it's "imminent"
let's do this for now - if we get the 2 field package.json pr together, then once we've reviewed+merged, we can determine whether we would want to branch and release v0.11.10 with that pr to fix this issue
i don't think we can ship the downgrade pr in v0.11
in the meantime, could you create a tracking issue in github with the suggestion to use yarn in the meantime that we can point users to?
yes, but, we're not going to release v0.11 off of main again
Oh I see
the next release off of main will be v0.12.0
if we do v0.11.10 it'll be branched off of v0.11.9
Ok I'm creating the issue
Issue opened, I'm starting to work on this right now,
First: pinning a runtime version
Second: changing the package manager, I'm going to open 2 different PR for that
@sharp peak https://github.com/dagger/dagger/pull/7852
To pin a runtime version
I tested locally with integration test, works fine, I'm waiting for the CI to be green, writing a changelog note and we're good
nice nice ❤️ 🎉
@sharp peak I updated based on your comment, feel free to approve if you think that's good enough
Brb just gone for lunch 🙂