#@Helder Correia @kjuulh just wanted to
charred gulch
For the automated release part:
It is honestly way overdue. It would go along way to make the project more stable, because I honestly forget to do it when the version is bumped.
We can do 0.12.2 or whatever the newest version is. I haven't run the engine upgrade in a while for the sdk, which is why it is a bit behind.
quartz crystal
I think it's just the crate publishing that we'd need to do to automate it in - I think all we'd need is a CARGO_REGISTRY_TOKEN for it
charred gulch
It isn't too bad. We also need a way of setting the cargo workspace version if we don't want to do it manually. And fit that to the regular release flow. And as you mention get a token installed. Gerhard also has access to the cargo project so it should be easy to just setup a github secret for it
Crates.io project*
I remember I did create a publish step but I don't think we ever ended up using it. Because it didn't fit in the release process as it was then. I.e. with the workspace version having to change and all that
quartz crystal
if you're happy to take a look at the workspace bumping step, i can sync with @kind geode at some point on getting the cargo stuff setup
and then i'll factor it into the RELEASING doc
charred gulch
Yes. I am guessing checkie or whatever is also part of the release process as well as docs. I'll give it a whirl next time I am at the PC to see what I am missing
kind geode
👋
@quartz crystal dagger-ci is in the RelEng Vault. If you login into GitHub as that user, you can then login into https://crates.io with GitHub, and then: https://crates.io/crates/dagger-sdk
quartz crystal
nice nice 🎉 thanks!
kind geode
quartz crystal
@charred gulch from my understanding - the dagger-codegen and dagger-bootstrap crates are just internal to the operation of working on the SDK
I can't see any dependency from dagger-sdk on them
those first two published crates only seem to be relevant for the yanked dagger-rs?
charred gulch
<@211225862912081920> from my understanding - the `dagger-codegen` and `dagger-b...
They're there only for the codegen.
quartz crystal
am i misunderstanding something? or would we want to yank those from crates.io as well?
(for context - i've started seriously on this piece in https://github.com/dagger/dagger/pull/9197)
charred gulch
Nope we can yank them
quartz crystal
(for context - i've started seriously on this piece in https://github.com/dagger...
logic being, i've fallen deep into the rust rabbit hole for fun, and want to do rust dagger things now 😄
quartz crystal
Nope we can yank them
same for dagger-core as well?
charred gulch
Sounds great! I am just starting my Christmas vacation so let me know if you find something of interest got plenty of time on my hands
Yes dagger core as well
It was separate from the SDK in the past but it is unwieldy to handle crates in lock step
quartz crystal
just glancing, i don't think anyone at dagger has permissions for those crates - so i think you would have to yank them?
charred gulch
Yes I can do that
quartz crystal
when i get something working, i'll probably try and manually publish crates for v0.15.0+? and then i'll integrate it into the rest of the process
just wanted to check that that sounds okay to ya
charred gulch
Go nuts! I'll give the release a go on all my projects as well once you've got it out
Should all be yanked now
quartz crystal
🎉