🤖✅ dagger/go 34 Remove buildinfo package

[outer hornet]

🟢9 🔴1
0f1460cec44d - Remove buildinfo package
https://dagger.cloud/dagger-dogfood/checks/github.com/dagger/go@0f1460cec44d613ea7479a72fb8e1af68b2d12cf

🟢 dang-sdk:generate-all
🔴 dang-skill:generate
🟢 e-2-e

@potent portal
🔴1 red · dagger/go 34 Remove buildinfo package · commit 0f1460cec44d

🔴 dang-skill:generate on 0f1460cec44d
Cloud status: FAILURE

dagger --x-release=v1.0.0-beta.3 -W github.com/dagger/go@0f1460cec44d613ea7479a72fb8e1af68b2d12cf check 'dang-skill:generate'

Link: https://dagger.cloud/dagger-dogfood/checks/github.com/dagger/go@0f1460cec44d613ea7479a72fb8e1af68b2d12cf?check=dang-skill%3Agenerate

[potent portal]

@outer hornet what does CI fail here?

[outer hornet]

Investigating failed dang-skill:generate for commit 0f1460cec44d.
-# I’ll inspect the failed dang-skill:generate check and pull the relevant failure output.
-# 💻 curl -fsS -X POST "$AGENT_RELAY_URL/append-status-message" -H 'content-type: application/json' -d '{"message_id":"1528095099085394154","content":"I’ll inspect the failed dang-skill:generate check and pull the releva...
-# 💻 ls -la ~/src/github.com/dagger && ls -la ~/src/github.com/dagger/dagger 2>/dev/null || true && ls -la ~/src/github.com/dagger/dagger.io 2>/dev/null || true
🔎 relay lookup
-# 💻 command -v dagger && dagger version
-# 💻 git -C ~/src/github.com/dagger/dagger status --short --branch && git -C ~/src/github.com/dagger/dagger rev-parse HEAD && git -C ~/src/github.com/dagger/dagger remote -v
-# 💻 dagger --x-release=v1.0.0-beta.3 -W github.com/dagger/go@0f1460cec44d613ea7479a72fb8e1af68b2d12cf check 'dang-skill:ge...
Status feed truncated; full status feed will be linked when this turn completes.
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate is-empty
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate modified-paths
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate added-paths
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate removed-paths
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate diff-stats
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate as-patch | sed -n '1,260p'
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate as-patch --help | sed -n '1,220p'
-# 💻 dagger --x-release=v1.0.0-beta.3 -W ~/src/github.com/dagger/go call dang-skill generate as-patch contents | sed -n '1,260p'
📣 done

🤖⚙️ dagger/go 34 Remove buildinfo package

🤖🔎 dagger/go 34 Remove buildinfo package

[outer hornet]

@potent portal dang-skill:generate fails because the generator produced changes. It pulls skills/dang-language from https://github.com/vito/dang@main and the checked-in skill docs are stale.

Dagger reports these modified paths: skills/dang-language/SKILL.md, reference/control-flow.md, reference/graphql.md, reference/objects.md, reference/stdlib.md, reference/syntax.md, and reference/types.md. The error is: generate function dang-skill:generate produced changes; run dagger generate dang-skill:generate to apply.

So this is generated-docs drift, not a Go compile/test failure. One notable cause is the generator depending on upstream vito/dang@main, so it can go red when that upstream skill changes.

🤖✅ dagger/go 34 Remove buildinfo package