🚀 v0.13.5 - 10th October 2024

[slate falcon]

Milestone: https://github.com/dagger/dagger/milestone/64

Currently just want to get a hotfix out for this issue ([more context](#1293156465804185610 message))

cc <@&946480760016207902>

TODOs:

• [x] Update Daggerverse/Cloud/Playground
• [x] Go docs have showed up: https://pkg.go.dev/dagger.io/dagger@v0.13.5
• [x] d4gh PR merged and tag published: https://github.com/dagger/dagger-for-github/pull/152
• [x] nix updated
• [x] homebrew updated https://github.com/Homebrew/homebrew-core/pull/193687
• [x] website updated https://docs.dagger.io/install
• [x] improve releasing PR merged https://github.com/dagger/dagger/pull/8680
• [x] incremental automation PR - pushed a separate commit to 8680 that consolidates two steps into one (tiny admittedly, but helps)

[tropic shale]

Can include this pr https://github.com/dagger/dagger/pull/8623 into this release?

[strange gull]

merged

@flint wyvern - where would you expect there to be information on how to install a nightly dagger build? as it turns out, it's already supported from our install.sh script we have, we just don't have it written down anywhere

i've also worked on adding support for it to our github action - https://github.com/dagger/dagger-for-github/pull/151

[strange gull]

@slate falcon i'm headed off now, but everything should be good to run a release whenever you're ready
i added a couple of minor ci changes to the milestone (not super urgent), but should make the releasing process a little bit smoother

https://github.com/dagger/dagger/milestone/64

[slate falcon]

Starting once CI on main finishes!

[slate falcon]

There's a couple jobs on main that are stuck in queued waiting for a runner even after a manual cancel and retry: https://github.com/dagger/dagger/actions/runs/11280772076/job/31375955447

Namely lint and test-publish, which are important enough that I don't want to skip them. Will look in argo to see if there's any hints

[flint wyvern]

I have a commander folder in google drive, so we could have a doc there.

If we are comfortable with the instructions being external, then would it make sense to add the details to our contribution page?

[slate falcon]

Just merged an infra change that might help...

[slate falcon]

Actually, turns out this is what we need if anyone has a sec: https://github.com/dagger/dagger/pull/8678

Looks like AWS just may be out of capacity for some spot instance types right now, that just switches those jobs over to on-demand

[slate falcon]

changelog+version-bump PR here for anyone with a sec: https://github.com/dagger/dagger/pull/8679

(consolidating the steps in creating that PR to a single dagger call seems like a good candidate for incremental automation after release is done)

[slate falcon]

Letting CI run on main, tagging engine after.

Another thing worth addressing as a follow up is the macos 12 GHA runners are deprecated, so worth a try to bump (especially since they seem to rarely work anyways) https://github.com/actions/runner-images/issues/10721 Akihiro says macos 15 is less flaky: https://github.com/actions/runner-images/issues/10721#issuecomment-2405235967

[strange gull]

I trust akihiro, seems worth it 🎉

Bump arbitrary number, thing gets better, of course

[slate falcon]

Engine tag published ✅

Go SDK publish failed, looks like an issue with the automated release notes creation: https://github.com/dagger/dagger/actions/runs/11283014340/job/31381632297#step:3:1077

error: parse selections: parse field "create": init arg "latest" value as dagql.DynamicOptional (GhLatest) using dagql.DynamicOptional: cannot create String from bool

Not a huge deal since I can do it the old fashioned way, but need to fix before next release

[strange gull]

👀 oh rip

Not quite sure how that's happened actually 🤔 that's an issue in the automation I tried to add

The code in here looks right? Maybe somehow we're encoding true/false weirdly in the engine? https://github.com/sagikazarmark/daggerverse/pull/183

Weird, I can dive into that, but somehow looks like we're sending a Boolean value in the query? Something seems super wrong there in the engine, the CI stuff seems right

[slate falcon]

After manually creating the release I left a v0.13.4 in the title somehow, fixed now: https://github.com/dagger/dagger/releases/tag/sdk%2Fgo%2Fv0.13.5

[strange gull]

I'll likely dive in to this tomorrow, already been doing a lot of enum shenanigans

It's a touch late here to dive into anything too big

[slate falcon]

Oh for sure, that seems like a long-standing pre-existing issue, not an emergency

[strange gull]

Fyi the same thing will likely happen with all the SDKs, since they all use the same logic

[slate falcon]

Oh yeah I've been going through them, almost done. Just been rinse+repeating with manually creating the releases

It works out because the release notes are the last step so everything else executes first before it errors out

[strange gull]

😅 love "little" improvement accidentally uncovering hidden engine bugs

[slate falcon]

It works out in the long run since it results in more things getting fixed 🤷‍♂️ 🎉

Okay SDKs+Helm all published and released.

Daggerverse/Cloud can be updated (again) cc @slow kayak @unique sun

d4gh here: https://github.com/dagger/dagger-for-github/pull/152 cc @rose bloom

Okay just in the "async wait for automated/manual processes" phase. I'm trying out putting a checklist in the top-level message of this thread with everything that's outstanding so it's harder to lose track of things

[strange gull]

😱 https://github.com/dagger/dagger/pull/8682

yeah this one just sucks