Skip to content

chore: Release v0.54.3#3651

Merged
edgarrmondragon merged 2 commits into
v0.54from
release/v0.54.3
May 27, 2026
Merged

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

Conversation

@MeltyBot
Copy link
Copy Markdown
Contributor

@MeltyBot MeltyBot commented May 27, 2026

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.

@MeltyBot MeltyBot requested a review from a team as a code owner May 27, 2026 21:33
@MeltyBot MeltyBot requested a review from edgarrmondragon as a code owner May 27, 2026 21:33
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 27, 2026

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]
Loading

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

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread CHANGELOG.md Outdated

### 🐛 Fixes

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown

codspeed-hq Bot commented May 27, 2026

Merging this PR will not alter performance

✅ 8 untouched benchmarks


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

Open in CodSpeed

@codecov
Copy link
Copy Markdown

codecov Bot commented May 27, 2026

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.

@edgarrmondragon edgarrmondragon merged commit 7a0a2e5 into v0.54 May 27, 2026
42 checks passed
@edgarrmondragon edgarrmondragon deleted the release/v0.54.3 branch May 27, 2026 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants