Complete data-operation safeguards and reproducible v2.1.2 release - #54
Merged
Merged
Conversation
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.
Native writes acknowledged by MongoDB could be missing from a branch created immediately through REST, and the console could apply an Undo scope different from the one just previewed. This change drains parent capture before REST forks, preserves an immutable bounded Undo review, and recovers expired or reset demo sessions with regression coverage.
The 2.1.2 release also makes the bundled console reproducible from public
web/source, fixes Go v2 module publication, and defines a safe stopped-source import workflow. Failed/cancelled imports remain hidden and clean up their partial state; explicit cleanup supports crash recovery. Concurrent service startup no longer drops the current WAL index, and stopping capture during collection setup no longer reports a permanent capture failure.Compatibility changes:
github.com/argon-lab/argon/v2andgithub.com/argon-lab/argon/api/v2; root and nested API tags must identify the same commit.--source-quiescedafter stopping source writers and DDL; dry runs remain available without acknowledgment.Release publication now depends on the complete engine/API/CLI/driver/vulnerability/browser checks on the tagged commit. Public UI assets are checked against the locked source, and release manifests record engine/UI/binary provenance. All platform binaries build in one job and upload directly to the release, avoiding temporary Actions artifact storage as a publication dependency.
Validation: real MongoDB 7.0.43 REST branch and degraded-capture regressions; API/CLI suites; import interruption/cleanup/retry; concurrent index migration; PyMongo/Mongoose convergence and undo; external Go consumer build; vet and reachable vulnerability checks; release metadata/installer tests; public UI rebuild comparison, full npm audit (0 advisories), and production-embedded browser regression covering reviewed Undo, delayed responses, recovery, isolation and mobile rendering. Full root/S3 tests and all other gates run in PR CI before merge.