Repository navigation
fix(lastcode): keep local update builds reproducible - #183
Merged
lastobelus merged 4 commits intoSep 3, 2026
Merged
Conversation
Loading
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.
Retained local-update worktrees could reuse stale local package snapshots, while isolated validation could inherit a source thread from a different T3 home. macOS path aliases and replay-renumbered migration fixtures also made full validation fail despite equivalent behavior.
Force-refresh frozen local dependencies, scope CLI source-thread context to the matching home, normalize Cursor skill paths, and align migration fixtures with their current numbers. This restores deterministic full update builds without changing normal app behavior.
Built with GPT-5.6 Sol in the Codex harness.