Skip to content

Pin moonlink 0.3.0 (37b040f9) - #206

Merged
zhousun merged 1 commit into
v0.3-devfrom
v0.3/17-final-pin
Nov 17, 2026
Merged

zhousun merged 1 commit into
v0.3-devfrom
v0.3/17-final-pin

Conversation

@zhousun

@zhousun zhousun commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Moves the moonlink submodule to its 0.3.0 release commit 37b040f9. Since the previous pin 0e38b435:

  • moonlink PR 2376: when a mirror is dropped, its source is removed from the publication by the table's identity (its OID), not its name, and a new connection to the same database waits for the previous one to finish shutting down. Before, dropping a mirror and creating it again at once, the documented way to resnapshot, could leave the new mirror errored ("no longer in publication moonlink_pub"); CI hit it intermittently in make test.
  • moonlink PR 2378: dependency upgrades for the open RustSec advisories (tokio, h2, hyper, rustls, openssl, bytes, zstd, lru 0.18.2 and others), with explicit, reasoned ignores where no fix exists; moonlink's cargo deny check is green.
  • Test-only changes to moonlink's chaos tests.

The CHANGELOG gets one line for the resnapshot fix, and the pins in docs/ARCHITECTURE.md and tests/mirror_diff/expected.txt follow.

Tests

CI on this PR (make test on PostgreSQL 14-18), plus a dispatched run for the e2e gate on PostgreSQL 17 and 18 and the Docker image build and run.

This pull request and its description were written by Isaac.

Moves the moonlink submodule to its release commit: the publication cleanup of a dropped mirror acts on the source
table's identity and waits for the previous connection, so dropping and re-creating a mirror keeps the new one
(moonlink PR 2376); dependency upgrades for the open RustSec advisories (moonlink PR 2378); and test-only fixes.

Co-authored-by: Isaac <no-reply@databricks.com>
@zhousun
zhousun merged commit 1719f31 into v0.3-dev Nov 17, 2026
21 checks passed
@zhousun
zhousun deleted the v0.3/17-final-pin branch November 17, 2026 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant