Skip to content

cache: propagate github instance slug - #27

Closed
max-blacksmith wants to merge 1 commit into
useFetchAsHTTPClientfrom
cache-instance-slug
Closed

max-blacksmith wants to merge 1 commit into
useFetchAsHTTPClientfrom
cache-instance-slug

Conversation

@max-blacksmith

@max-blacksmith max-blacksmith commented Sep 24, 2026 •

Copy link
Copy Markdown

Cache requests need the GitHub instance identity so matching owner/repo names on different instances cannot share entries.

Read BLACKSMITH_INSTANCE_SLUG from the runner environment and send X-Blacksmith-Instance-Slug on restore, reserve, and commit requests. Missing values default to github for existing dotcom runners.

flowchart LR
  job[Job instance_slug] --> agent[Agent guest environment]
  agent --> toolkit[Cache HTTP client]
  toolkit --> header[X-Blacksmith-Instance-Slug]
  header --> backend[Instance-scoped backend]
Loading

Targets useFetchAsHTTPClient, the branch with the cache package used by the actions. Two header propagation tests passed on Testbox; Prettier passed.

Deploy the backend and agents first. After merging, publish the cache package, update pinned dependencies in the cache/setup actions, and rebuild their bundles before enabling non-dotcom caching.

Companion PRs: backend, agent.

@max-blacksmith

Copy link
Copy Markdown
Author

This information shouldn't be passed like this.

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