Repository navigation
Harden shared vault portability, lockfile reproducibility and CI triggers - #5
Merged
Merged
Conversation
…T and O_EXCL symlink rejection
…bootstrap locked dependencies
…al vault parity gate
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
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.
Responds to November 9 review findings. Removes the architecture-specific numeric O_NOFOLLOW bit while retaining O_CREAT|O_EXCL symlink refusal, adds a CI SHA256 parity check against MLT Player's matching branch or main, pins Flutter CI and removes already merged feature branches from push triggers. Will regenerate and commit pubspec.lock with flutter pub get and enforce it in CI. This PR is intentionally a draft and does not change runtime login behavior.