GitHub
10/19/2026, 2:34 PMstart_date setting. The SDK applies start_date to every incremental stream, but no capability names it, so each tap defines the setting by hand and --about does not list it as a capability.
The new TapCapabilities.START_DATE (start-date) is a default tap capability. It adds the start_date setting to the config schema of every tap, as batch does for batch_config.
• Add TapCapabilities.START_DATE and START_DATE_CONFIG, and add the capability to Tap.capabilities.
• Add start_date in Tap.append_builtin_config when the tap has the capability. A start_date that the tap defines itself stays as it is.
• List the capability with the built-in tap capabilities in the docs.
• Remove the hand-written start_date property from the tap template. The template meltano.yml does not list start-date yet, because the published Meltano schema does not accept it.
• Test that a tap that rejects unknown settings accepts start_date only with the capability.
The --about output of every tap now lists start-date and a start_date setting, unless the tap overrides capabilities without it. This includes full-table taps, and is why the --about snapshots change.
---
🤖 Generated with Claude Code
Summary by Sourcery
Add built-in support for declaring and configuring the start_date capability across SDK taps.
New Features:
• Add the start-date tap capability and built-in start_date configuration setting.
Enhancements:
• Make the SDK automatically expose start_date for taps with the capability while preserving tap-defined overrides.
• Remove the template’s manually defined start_date configuration and document the SDK-provided setting.
Documentation:
• Document start-date alongside the built-in tap capabilities and update the tap template guidance.
Tests:
• Verify that start_date is accepted only when the tap advertises the capability and update tap --about snapshots.
meltano/sdkGitHub
10/19/2026, 5:19 PM