Skip to content

fix(ci): drop uv cache + clarify entry skill action/conversation split - #13

Merged
dean-harel merged 1 commit into
mainfrom
fix/publish-uv-cache
Apr 25, 2026
Merged

fix(ci): drop uv cache + clarify entry skill action/conversation split#13
dean-harel merged 1 commit into
mainfrom
fix/publish-uv-cache

Conversation

@dean-harel

Copy link
Copy Markdown
Owner

Summary

  • CI: Remove `enable-cache: true` from the `astral-sh/setup-uv` step in `entry-publish.yml`. The cache step required a `uv.lock` that doesn't exist (scripts use PEP 723 inline metadata, not a project lockfile), and bombed with `No matches found for glob **/uv.lock` before any publish work ran. Surfaced on PR entry: don't conversate, navigate #12, the first end-to-end run of the publish pipeline introduced in PR feat: X Articles syndication pipeline #10.
  • Entry skill: Clarify that artifacts are only written when the user picks a listed action — free-form follow-ups are conversation, not revise instructions. Add a research.yaml rule that later sections should build on earlier ones.

Test plan

The Entry Publish workflow enabled astral-sh/setup-uv caching, which
required a uv.lock that doesn't exist (scripts use PEP 723 inline
metadata, not a project lockfile). The cache step errored with
"No matches found for glob **/uv.lock" before any publish work ran.
Removed enable-cache so the action installs uv without a cache key.

Entry skill: clarified that artifacts are only written when the user
picks a listed action — free-form follow-ups are conversation, not
revise instructions. Added a research.yaml rule that later sections
should build on earlier ones.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

✅ All review checks passed. When you're ready, apply the ready label to publish.

@dean-harel
dean-harel merged commit e887dff into main Apr 25, 2026
2 of 3 checks passed
@dean-harel
dean-harel deleted the fix/publish-uv-cache branch April 25, 2026 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant