Repository navigation
Sync rocicorp/mono main (9aca1b0) - #28
Merged
Merged
Conversation
Mono-Internal-Commit: 16db23d0bc36943539d4573b1d85c4e497150a69
Mono-Internal-Commit: 3fe85f2d6943f81cfa2e6e81fa09876e36b97e53
Closes rocicorp#6730 Co-authored-by: joshuasun <sunjue123@outlook.com> Mono-Internal-Commit: aa98917c5d5a37e9b2d3662baadc7e65d96eb823
Closes rocicorp#6728 Co-authored-by: joshuasun <sunjue123@outlook.com> Mono-Internal-Commit: d461b05f94088d043ab60edcd870daaf949df242
…s overlap Closes rocicorp#6729 Co-authored-by: joshuasun <sunjue123@outlook.com> Mono-Internal-Commit: 678acb51506b32c30d1c21bf356e05ac5c1e4981
…tart Mono-Internal-Commit: 1215b6d4787a9768a83fee28e2c479b719018999
Mono-Internal-Commit: ae6de4792084dab468bd9269d271b494354a7b8d
…s vitest ^5.0.5 Upstream's lockfile dropped vitest 5.0.0, which both still resolved to; they now resolve to upstream's 5.0.5 entry. Only their two importers change in the lockfile. Amp-Thread-ID: https://ampcode.com/threads/T-c513a037-a257-45e0-b9a9-15c15edfe859 Co-authored-by: tmm <tmm@tmm.dev>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Merges rocicorp/mono
mainup to 9aca1b0: 7 commits, with no conflicts.ast.tsswapsArray.prototype.toSortedfor a helper (Hermes lacks it); behaviour is the same, and the regenerated conformance vectors are byte-identical.close()dropping a shared SQLite connection; a throwingclose()blocking a reopen) have no Swift counterpart:ReplicaDatabase.release()runs once per client, guarded byrepClosed, synchronously on the engine loop, and opening never waits on a close.zero-conformanceandzero-swift-clistill resolved to. They now take^5.0.5and upstream's existing 5.0.5 entry; only their two importers change in the lockfile (8 lines).pnpm install --frozen-lockfileleaves it unchanged, andsyncpack lintis clean.zero-conformance28/28 (vectors regenerated, unchanged),zero-swiftCLI 26/26, Swift 215 tests in 41 suites.No changeset: nothing in the Swift package changes.
Landing: like #3, this should land with its merge commit so upstream stays an ancestor of main; a squash would make the next sync conflict.