Skip to content

fork-release: do not restore target/ from cache - #8

Merged
JSBtechnologies merged 1 commit into
mainfrom
fork-release-no-target-cache
Oct 21, 2026
Merged

JSBtechnologies merged 1 commit into
mainfrom
fork-release-no-target-cache

Conversation

@JSBtechnologies

Copy link
Copy Markdown
Owner

Summary

The first fork-v0.1.0 tag run failed in "Build Codex package" with could not find native static library rusty_v8. The run restored the target/ cache saved by the earlier build-only dispatch, in which the v8 crate's build script was fresh but its downloaded static library was not part of the cache. Stop caching target/ (cache-targets: "false"); keep the cargo registry cache. A release build is a full LTO build regardless, so the target cache bought almost nothing.

Test plan

  • YAML parses; prettier clean
  • re-tag fork-v0.1.0 on the merged commit and confirm the tag run publishes the release

The first tag run restored a target/ cache in which the v8 build script was
fresh but its downloaded static library was absent, and the build failed with
"could not find native static library rusty_v8". A release build is a full
LTO build regardless, so cache only the cargo registry.
@JSBtechnologies
JSBtechnologies merged commit e9ff0fa into main Oct 21, 2026
9 checks passed
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