This release is a pre-release and may not be stable for production use.
Meltano Singer SDK
The Tap and Target SDKs are the fastest way to build custom data extractors and loaders! Taps and targets built on the SDK are automatically compliant with the Singer Spec, the de-facto open source standard for extract and load pipelines.
Future-proof extractors and loaders, with less code
On average, developers tell us that they write about 70% less code by using the SDK, which makes learning the SDK a great investment. Furthermore, as new features and capabilities are added to the SDK, your taps and targets can always take advantage of the latest capabilities and bug fixes, simply by updating your SDK dependency to the latest version.
Meltano
Not familiar with Meltano? Meltano is your CLI for ELT+ that:
- Starts simple: Meltano is pip-installable and comes in a prepackaged docker container, you can have your first ELT pipeline running within minutes.
- Has DataOps out-of-the-box: Meltano provides tools that make DataOps best practices easy to use in every project.
- Integrates with everything: 300+ natively supported data sources & targets, as well as additional plugins like great expectations or dbt are natively available.
- Is easily customizable: Meltano isn't just extensible, it's built to be extended! The Singer SDK (for Connectors) & EDK (for Meltano Components) are easy to use. Meltano Hub helps you find all of the connectors and components created across the data community.
- Is a mature system: Developed since 2018, runs in production at large companies like GitLab, and currently powers over a million pipeline runs monthly.
- Has first class ELT tooling built-in: Extract data from any data source, load into any target, use inline maps to transform on data on the fly, and test the incoming data, all in one package.
If you want to get started with Meltano, we suggest you:
- head over to the Installation
- or if you have it installed, go through the Meltano Tutorial.
Documentation
- See our online documentation for instructions on how to get started with the SDK.
Contributing back to the SDK
- For more information on how to contribute, see our Contributors Guide.
Making a new release of the SDK
-
Trigger a version bump using the GitHub web UI or the cli:
$ gh workflow run
The
increment: autooption will figure out the most appropriate bump based on commit history. -
Follow the checklist in the PR description.
-
Publish a new release using the GitHub web UI.
1 maintainer
Release files for singer-sdk 0.55.0a9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| singer_sdk-0.55.0a9.tar.gz | 1.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| singer_sdk-0.55.0a9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / singer_sdk-0.55.0a9.tar.gz
| Download URL | singer_sdk-0.55.0a9.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2dae22c7248cb0e9f839cf183cc1b60372b8674f242af0c74b6b7d6a499cea2
|
|
BLAKE2b-256 checksum How to use checksums |
7786a4c88760dee11ef897b8a8d957c383f254881043516283446b6f96199afe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / singer_sdk-0.55.0a9-py3-none-any.whl
| Download URL | singer_sdk-0.55.0a9-py3-none-any.whl |
|---|---|
| Size | 223.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3780bced70df002af0c608ffe11f552642fa4948fba9837140a291f6a18f2ac8
|
|
BLAKE2b-256 checksum How to use checksums |
4d99217fe194d59078664407157acf81c4b406d169b48f7e389db13cdd10a8a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log
