[STORY] Release pages with install, upgrade and verify steps; signed OCI chart; Scorecard; pinned kind
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with .github/workflows/release-please.yml and the e2e workflows test-e2e.yml and test-e2e-rbac.yml; inspect how release bodies and chart pushes are handled. Add the Scorecard workflow and pin kind as described in the scope. Run actionlint .github/workflows/*.yml and verify the chart with the documented cosign verify command; done when release jobs reject missing footers or unsigned chart pushes.
Written by the indexing model from the issue text.
Description
Goal
Make each release page tell a user how to install, upgrade and verify that release, and close the remaining supply-chain gaps that a reviewer checks first.
Definition of done
- Observable: every release body ends with an install and upgrade block (
helm install ... --version <v>,brew upgrade), thegh attestation verifycommand, and the image digests; the OCI Helm chart is cosign-signed; an OpenSSF Scorecard workflow runs on main;kindis pinned in the e2e workflows. - Negative: a release body without the footer, or an unsigned chart push, fails the release job.
Scope
.github/workflows/release-please.yml(release body footer, chart signing), a Scorecard workflow,test-e2e.ymlandtest-e2e-rbac.yml(pin kind).
Out of scope
- The tool pinning and verification-identity changes in #2398.
Consumers and surfaces touched
- GitHub release bodies, the OCI chart in
ghcr.io/defilantech/charts/llmkube, CI workflows.
Verification
actionlint .github/workflows/*.yml
cosign verify ghcr.io/defilantech/charts/llmkube:<v> --certificate-identity <main release workflow> --certificate-oidc-issuer https://token.actions.githubusercontent.com
Falsification
- Edit: drop the chart signing step.
- Expected failure: the documented
cosign verifyfor the chart fails on the next release.
Risks
- Scorecard findings will need triage; start it as informational.
- Dominant language
- Go
- Stars
- 232
- Forks
- 37
- Avg merge
- 21h 42m
- Merged PRs (30d)
- 244
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from defilantech/LLMKube
-
component/metal-agent documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
defilantech/LLMKube#2581 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
defilantech/LLMKube#2578 ·
Maintainers usually reply within 1 day
-
documentation helm priority/low size/small
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
defilantech/LLMKube#2420 ·
Maintainers usually reply within 1 day
-
component/metal-agent enhancement priority/low size/medium
Difficulty 4/5 3-5 days Newbie friendliness 48/100
defilantech/LLMKube#2597 ·
Maintainers usually reply within 1 day
-
[BUG] Docs and comments describe InsufficientMemory only as a start refusal, but a serving engine can now carry itPossibly taken @defilan-agent claimed this today. Openbug component/metal-agent documentation priority/low size/small
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
defilantech/LLMKube#2596 ·
Maintainers usually reply within 1 day
All issues in defilantech/LLMKube
Similar issues
-
☢️ Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/import-export area/projects concern/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
go-vikunja/vikunja#4455 · 1 comment ·
Maintainers usually reply within 2 days
-
Dependabot PRs no longer merge automaticallyPossibly taken @dwisiswant0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectdiscovery/urlfinder#160 ·
Maintainers usually reply within 1 day
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chnm/legal-modernism#450 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day