Reset Bootsnap RBS cache on lockfile changes & remove cache priming for CI - #2669
Open
KaanOzkan wants to merge 2 commits into
Open
Reset Bootsnap RBS cache on lockfile changes & remove cache priming for CI#2669KaanOzkan wants to merge 2 commits into
KaanOzkan wants to merge 2 commits into
Conversation
KaanOzkan
force-pushed
the
ko-reset-bootsnap-cache-on-lockfile
branch
4 times, most recently
from
July 30, 2026 20:20
d62a2e9 to
0ec2da2
Compare
KaanOzkan
changed the title
Stores the current `Gemfile.lock` digest in Tapioca's dedicated Bootsnap cache and resets the Bootsnap payload when the digest changes. Skips stale read-only caches so consumers do not use rewritten iseqs built for a different lockfile.
The `--only-bootsnap-rbs-cache` flag and read-only cache path supported sharing a primed cache between CI jobs. That workflow is no longer used. Keep the cache local and writable. Normal `tapioca dsl` runs populate it, and lockfile changes reset the cached iseq payload.
KaanOzkan
force-pushed
the
ko-reset-bootsnap-cache-on-lockfile
branch
from
July 30, 2026 20:58
0ec2da2 to
8095cb1
Compare
KaanOzkan
marked this pull request as ready for review
July 30, 2026 20:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
tapiocaor one of its dependencies changed because Bootsnap does not include those dependencies in its cache key.--only-bootsnap-rbs-cachewas added to prime the cache in CI, but sharing Bootsnap caches across CI builds is unreliable and the read-only path complicates cache setup for little benefit.Implementation
Gemfile.lockdigest in Tapioca’s dedicated Bootsnap cache. When the digest changes, delete the Bootsnap payload so the current run rebuilds it.--only-bootsnap-rbs-cache, read-only cache handling, and their documentation. Keep the cache focused on writable local runs.Tests
Added coverage that changing
Gemfile.lockresets the existing Bootsnap payload.