fix(release): copy README/LICENSE into Docker build; drop PyPI attestations

[Liohtml]

The v0.2.1 release run (27365603005) failed in both publish jobs. build succeeded and produced valid wheels; the two failures are independent:

1. Docker ❌ — real Dockerfile bug

OSError: Readme file does not exist: README.md
ERROR: process "uv sync --no-dev --no-cache ..." did not complete (exit 1)

uv sync builds the medcheck package itself, and hatchling needs README.md (pyproject readme = "README.md") — but the Dockerfile only copied pyproject.toml, uv.lock*, src/, workflows/, never the README. Fix: copy README.md + LICENSE into the build context.

✅ Verified locally: uv build succeeds using exactly the file set the Dockerfile now copies (produces medcheck-0.2.1.tar.gz + wheel). (The Docker daemon isn't available in this environment, so I validated the failing step — the package build — directly.)

2. PyPI ❌ — transient Sigstore outage (not our bug)

502 Server Error: Bad Gateway for url: https://rekor.sigstore.dev/api/v1/log/entries
RekorClientError: Rekor returned an unknown error with HTTP 502

The build and OIDC Trusted Publishing auth both worked; the upload failed at the PEP 740 attestation step on a Sigstore Rekor 502 — a third-party outage. Fix: set attestations: false so a Sigstore outage can't block release. OIDC Trusted Publishing still authenticates the upload (no token, same security posture for auth).

After merge — retry the release

Re-tag to retrigger: delete + recreate v0.2.1 on main, or cut v0.2.2. I'll guide whichever you prefer.

Validation

• ruff ✅ · release.yml parses as valid YAML ✅ · package build ✅ with the new Docker file set.

https://claude.ai/code/session_01KYcUxCGAHaTPrRHTzJCWQz

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@Liohtml, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ccdf642-1e20-4759-a120-9347b5bd2f69

📥 Commits

Reviewing files that changed from the base of the PR and between 10fcde8 and 33cbb2d.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• Dockerfile

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/repo-issues-features-3ZLdb

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!