Repository navigation
Use selective Atlas release libraries - #2
Merged
Merged
Conversation
Pin the module closure and lockfile to reproducible GitHub assets, update compatible dependencies, and remove private source imports and runtime Git installation. Bump to 0.10.7.
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.
Switch Atlas imports and installs to the selected 0.4.9 libraries from versioned GitHub assets. Fresh production images install only the modules Stohr uses, without a sibling checkout or Git runtime dependency. Update compatible dependencies and the passkey transport type, and keep S3 signing behind the public Atlas export.
Validation: frozen installs, typecheck, Atlas module guard, production image startup and browser assets, and 489 isolated PostgreSQL tests passed. Biome reports existing warnings without errors. The PR adds the same released-library guard to CI; the existing PostgreSQL suite remains required before rollout.