Skip to content

chore: Release v0.54.5#3678

Merged
edgarrmondragon merged 1 commit into
v0.54from
release/v0.54.5
Jun 16, 2026
Merged

chore: Release v0.54.5#3678
edgarrmondragon merged 1 commit into
v0.54from
release/v0.54.5

Conversation

@MeltyBot

@MeltyBot MeltyBot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Prepare MeltanoSDK v0.54.5 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 project for the v0.54.5 release.

Bug Fixes:

  • Document the conversion of class-scoped fixtures in built-in integration tests to class methods in the changelog.

Documentation:

  • Add v0.54.5 entry to the changelog and update documentation config to the new release version.

Chores:

  • Bump singer-sdk version references from 0.54.4 to 0.54.5 across templates, project metadata, and GitHub issue templates.

@MeltyBot
MeltyBot requested a review from a team as a code owner June 16, 2026 02:37
@sourcery-ai

sourcery-ai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares the Meltano SDK project for the v0.54.5 release by adding the new changelog entry and updating all hard-coded version references from 0.54.4 to 0.54.5 across templates, docs, and tooling configuration.

File-Level Changes

Change Details Files
Add v0.54.5 entry to the changelog documenting the primary fix in this release. CHANGELOG.md
Update cookiecutter templates to depend on singer-sdk version 0.54.5 for newly generated projects.
  • Bump singer-sdk dependency constraint from ~=0.54.4 to ~=0.54.5 in the mapper cookiecutter template, including the faker extra variant.
  • Bump singer-sdk dependency constraint from ~=0.54.4 to ~=0.54.5 in the tap cookiecutter template, for both with- and without-extras cases.
  • Bump singer-sdk dependency constraint from ~=0.54.4 to ~=0.54.5 in the target cookiecutter template, including the 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 library version metadata and documentation with the new 0.54.5 release.
  • Update the Singer SDK version placeholder in the bug report issue template to 0.54.5.
  • Set the Sphinx docs 'release' string to 0.54.5.
  • Update the Commitizen configuration version to 0.54.5 so future automated bumps start from this release.
.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

@sourcery-ai sourcery-ai Bot left a comment

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.

Hey - I've reviewed your changes and they look great!


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.

@codecov

codecov Bot commented Jun 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.81%. Comparing base (9dd5563) to head (5a74ae4).

Additional details and impacted files
@@           Coverage Diff           @@
##            v0.54    #3678   +/-   ##
=======================================
  Coverage   93.81%   93.81%           
=======================================
  Files          73       73           
  Lines        5952     5952           
  Branches      731      731           
=======================================
  Hits         5584     5584           
  Misses        273      273           
  Partials       95       95           
Flag Coverage Δ
core 82.40% <ø> (ø)
end-to-end 75.20% <ø> (ø)
optional-components 42.72% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 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.

@codspeed-hq

codspeed-hq Bot commented Jun 16, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 8 untouched benchmarks


Comparing release/v0.54.5 (5a74ae4) with v0.54 (9dd5563)

Open in CodSpeed

@edgarrmondragon
edgarrmondragon merged commit 38880fc into v0.54 Jun 16, 2026
42 checks passed
@edgarrmondragon
edgarrmondragon deleted the release/v0.54.5 branch June 16, 2026 02:41
daria-hrabar pushed a commit to daria-hrabar/sdk that referenced this pull request Jun 16, 2026
- **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>
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