Meltano is a Python based ELT orchestrator where pipelines are declared as reusable blocks of extractors, loaders and transforms. The last week on the main branch brought 11 commits, 33 files changed, 716 insertions and 148 deletions. Two of those commits matter to operators: Python warnings are now emitted as structured log events, and meltano run no longer leaks database sessions when blocks never actually run.
Python warnings become structured events ¶
The most operator visible change is the logging commit from October 26. Python warnings, the ones surfaced through the warnings module, used to hit stderr as raw text. They bypassed the structured logging pipeline entirely, so anything shipping logs to Loki, Elasticsearch or a JSON parser had to regex match them.
The change lands in src/meltano/core/logging/utils.py and src/meltano/core/logging/__init__.py, with tests added under tests/meltano/core/logging/test_logging_utils.py. Warnings are now routed through the logging machinery and emitted as structured events, in the same shape as the rest of Meltano’s console output. If you grep orchestrator logs for level=error or parse JSON lines, warnings from SDK deprecations or dependency mismatches now show up in the same stream as everything else. That closes a real observability gap: warnings were previously the one class of output you could not alert on reliably.
meltano run leaks sessions when blocks never run ¶
A narrower but worth knowing fix landed on October 25 in the block execution path. When you invoke meltano run with --dry-run or --only-install, the per block systemdb sessions were opened during validation but never closed, because the blocks themselves never reached the run phase that owns cleanup. The fix touches src/meltano/core/block/block_parser.py and src/meltano/core/block/extract_load.py, the same two files touched twice in this window, which suggests the block lifecycle is under active attention.
The blast radius was small. Sessions held open on the system database for a validation only invocation, typically a local SQLite file. In CI, where dry runs run frequently against short lived containers, that meant lingering connections until process exit. It is a footgun fix, not a data correctness fix.
Dependency pinning and audit hygiene ¶
Three commits handle the dependency surface. One pins pytest from >=9 to ~=9.1.1 across the dev, testing and typing dependency groups in pyproject.toml and uv.lock. That is a deliberate tradeoff: reproducible test environments at the cost of a manual bump each time a pytest minor lands. Projects bitten by patch releases changing plugin behavior tend to converge on this shape.
Another adds uv audit ignores to the config, which is worth reading when the project pushes its next lock file bump, since it changes which advisories actually fail the build. Renovate handled routine housekeeping in parallel: GitHub Actions minor and patch updates, webpack bumped to ~5.112.0 for the docs site, and lock file maintenance.
Cloud changelog and tap-mongodb Arrow docs ¶
Two documentation commits describe features rather than change them. One documents Arrow BATCH format support for tap-mongodb, including a new arrow-support page wired into sidebars.js and the ConnectorSearch component. If you run MongoDB ingestion targets that accept Arrow batches instead of JSON lines, the serialization path and schema fidelity differ and it is worth reading the tap-mongodb docs before enabling it. The other adds a dated Meltano Cloud changelog entry, which indicates Cloud changes are being surfaced in the public repo with a regular cadence.
A CLAUDE.md update rounds this out, describing expectations for AI assisted contributions to the codebase. Expect more repos to carry such files.
What to watch ¶
- The structured warning logging is the first place to look if your log ingestion regexes silently stop matching warning lines after your next upgrade.
- The
pytest~=9.1.1pin means CI reproducibility now depends on a maintainer bumping the pin; track it if you vendor Meltano’s dev environment. - Both commits touching the block parser and extract load path in one week hint at further
meltano runlifecycle work. Watchsrc/meltano/core/block/for follow ups.