chore: Release v0.54.3 by MeltyBot · Pull Request #3651 · meltano/sdk

MeltyBot · 2026-05-27T21:33:06Z

Prepare MeltanoSDK v0.54.3 for release.

Checklist:

Check that the right version is set in all the files.
Groom the changelog for wording or missing entries.
Merge this PR once everything looks good.

Release Draft

Summary by Sourcery

Prepare the 0.54.3 release of the Meltano SDK.

Bug Fixes:

Document a fix ensuring stream names are included in log messages when ACTIVATE_VERSION forces _sdc metadata columns.

Enhancements:

Bump SDK version references from 0.54.2 to 0.54.3 across project configuration, templates, and documentation metadata.

sourcery-ai · 2026-05-27T21:33:12Z

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares the Meltano SDK for the v0.54.3 release by updating version references across project metadata, templates, documentation, and issue templates, and by adding a new changelog entry describing the main bug fix.

Flow diagram for version bump to v0.54.3 across project files

flowchart LR
    A[Update version to v0.54.3] --> B[pyproject.toml tool.commitizen.version]
    A --> C[docs conf.py release]
    A --> D[cookiecutter tap-template pyproject.toml]
    A --> E[cookiecutter target-template pyproject.toml]
    A --> F[cookiecutter mapper-template pyproject.toml]
    A --> G[.github bug issue template placeholder]
    A --> H[CHANGELOG.md new v0.54.3 entry]

File-Level Changes

Change	Details	Files
Add v0.54.3 release notes to the changelog documenting the key bug fix.	Add new v0.54.3 section with release date. Document bug fix ensuring stream name is included in log messages when ACTIVATE_VERSION forces _sdc metadata columns.	`CHANGELOG.md`
Update cookiecutter templates to depend on singer-sdk v0.54.3 instead of v0.54.2.	Bump mapper template dependency pin from 0.54.2 to 0.54.3, including faker extra variant. Bump tap template dependency pin from 0.54.2 to 0.54.3, including extras variant. Bump target template dependency pin from 0.54.2 to 0.54.3, including faker extra variant.	`cookiecutter/mapper-template/{{cookiecutter.mapper_id}}/pyproject.toml` `cookiecutter/tap-template/{{cookiecutter.tap_id}}/pyproject.toml` `cookiecutter/target-template/{{cookiecutter.target_id}}/pyproject.toml`
Align project and docs metadata with the new 0.54.3 version.	Update bug issue template placeholder SDK version to 0.54.3. Update Sphinx docs configuration `release` string to 0.54.3. Update Commitizen configuration version to 0.54.3.	`.github/ISSUE_TEMPLATE/bug.yml` `docs/conf.py` `pyproject.toml`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

sourcery-ai

Hey - I've found 1 issue, and left some high level feedback:

In the new changelog entry for v0.54.3, the sentence 'Ensure stream name is include in log message...' should be corrected to 'included' for clarity.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the new changelog entry for v0.54.3, the sentence 'Ensure stream name is include in log message...' should be corrected to 'included' for clarity.

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="12" />
<code_context>
+
+### 🐛 Fixes
+
+- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is include in log message when ACTIVATE_VERSION forces _sdc metadata columns
+
 ## v0.54.2 (2026-05-18)
</code_context>
<issue_to_address>
**issue (typo):** Fix grammar in "Ensure stream name is include"

This should read: "Ensure stream name is included in log message when ACTIVATE_VERSION forces _sdc metadata columns."

```suggestion
- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is included in log message when ACTIVATE_VERSION forces _sdc metadata columns.
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

sourcery-ai · 2026-05-27T21:33:54Z

+
+### 🐛 Fixes
+
+- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is include in log message when ACTIVATE_VERSION forces _sdc metadata columns


issue (typo): Fix grammar in "Ensure stream name is include"

This should read: "Ensure stream name is included in log message when ACTIVATE_VERSION forces _sdc metadata columns."

Suggested change

- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is include in log message when ACTIVATE_VERSION forces _sdc metadata columns

- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is included in log message when ACTIVATE_VERSION forces _sdc metadata columns.

codspeed-hq · 2026-05-27T21:36:34Z

Merging this PR will not alter performance

✅ 8 untouched benchmarks

_{Comparing release/v0.54.3 (8fa5789) with v0.54 (748f194)}

codecov · 2026-05-27T21:36:40Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.81%. Comparing base (748f194) to head (8fa5789).

Additional details and impacted files

@@           Coverage Diff           @@
##            v0.54    #3651   +/-   ##
=======================================
  Coverage   93.81%   93.81%           
=======================================
  Files          73       73           
  Lines        5948     5948           
  Branches      729      729           
=======================================
  Hits         5580     5580           
  Misses        273      273           
  Partials       95       95

Flag	Coverage Δ
core	`82.33% <ø> (ø)`
end-to-end	`75.21% <ø> (ø)`
optional-components	`42.75% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

read-the-docs-community · 2026-05-27T21:42:35Z

Documentation build overview

📚 Meltano SDK | 🛠️ Build #32876683 | 📁 Comparing 8fa5789 against latest (ea0f833)

🔍 Preview build

8 files changed · ± 8 modified

± Modified

@classmethods

- **fix: Ensure stream name is include in log message when ACTIVATE_VERSION forces _sdc metadata columns (meltano#3650)** - **chore: Release v0.54.3 (meltano#3651)** - **fix: Emitted `ACTIVATE_VERSION` now honor the stream aliases configured with stream maps (meltano#3654)** - **chore: Release v0.54.4 (meltano#3655)** - **chore: Lock file maintenance** - **fix: Convert class-scoped fixtures in built-in integration tests into `@classmethod`s (meltano#3676) (meltano#3677)** - **chore: Release v0.54.5 (meltano#3678)** ## Summary by Sourcery Release version v0.54.5 and align templates, docs, and tooling with the new version. Bug Fixes: - Document the fix converting class-scoped fixtures in built-in integration tests to use @classmethods in the changelog. Enhancements: - Update cookiecutter tap/target/mapper templates to depend on singer-sdk v0.54.5. Build: - Update project version metadata to 0.54.5 in pyproject and related tooling configuration. Documentation: - Bump documented release version to 0.54.5 in the Sphinx configuration and GitHub bug report template. --------- Signed-off-by: Edgar Ramírez Mondragón <[email protected]> Co-authored-by: MeltyBot <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

chore: Bump package version

3c2a18a

MeltyBot requested a review from a team as a code owner May 27, 2026 21:33

MeltyBot added the release label May 27, 2026

MeltyBot requested a review from edgarrmondragon as a code owner May 27, 2026 21:33

MeltyBot assigned edgarrmondragon May 27, 2026

style: pre-commit fixes

8fa5789

sourcery-ai Bot reviewed May 27, 2026

View reviewed changes

edgarrmondragon merged commit 7a0a2e5 into v0.54 May 27, 2026
42 checks passed

edgarrmondragon deleted the release/v0.54.3 branch May 27, 2026 21:50

edgarrmondragon mentioned this pull request Jun 16, 2026

chore: Merge branch 'v0.54' #3679

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: Release v0.54.3#3651

chore: Release v0.54.3#3651
edgarrmondragon merged 2 commits into
v0.54from
release/v0.54.3

MeltyBot commented May 27, 2026 •

edited by edgarrmondragon

Loading

Uh oh!

sourcery-ai Bot commented May 27, 2026 •

edited

Loading

Reviewer's Guide

Flow diagram for version bump to v0.54.3 across project files

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai Bot left a comment

Uh oh!

sourcery-ai Bot May 27, 2026

Uh oh!

codspeed-hq Bot commented May 27, 2026

Uh oh!

codecov Bot commented May 27, 2026 •

edited

Loading

Uh oh!

read-the-docs-community Bot commented May 27, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		### 🐛 Fixes

		- [#3650](https://github.com/meltano/sdk/issues/3650) Ensure stream name is include in log message when ACTIVATE_VERSION forces _sdc metadata columns

Uh oh!

Conversation

MeltyBot commented May 27, 2026 • edited by edgarrmondragon Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by Sourcery

Uh oh!

sourcery-ai Bot commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

Flow diagram for version bump to v0.54.3 across project files

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sourcery-ai Bot May 27, 2026

Choose a reason for hiding this comment

Uh oh!

codspeed-hq Bot commented May 27, 2026

Merging this PR will not alter performance

Uh oh!

codecov Bot commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

read-the-docs-community Bot commented May 27, 2026

Documentation build overview

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

MeltyBot commented May 27, 2026 •

edited by edgarrmondragon

Loading

sourcery-ai Bot commented May 27, 2026 •

edited

Loading

codecov Bot commented May 27, 2026 •

edited

Loading