Skip to content

Conversation

@ugrc-release-bot
Copy link
Contributor

@ugrc-release-bot ugrc-release-bot bot commented Jan 5, 2026


6.0.0 (2026-01-09)

⚠ BREAKING CHANGES

  • The API for the SFTP loaders changed; there's no longer the option to pass in a known_hosts file.

Features

  • replace pysftp with fabric, paramiko. (933c355)

Bug Fixes

  • use folder.add instead of content.add to upload gdb (3f1d84a)

Dependencies

  • update paramiko requirement from <4.0.0 to <5.0.0 (3820c70)

This PR was generated with Release Please. See documentation.

@codecov
Copy link

codecov bot commented Jan 5, 2026

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.69%. Comparing base (f87f4c5) to head (f9d4241).
⚠️ Report is 126 commits behind head on main.

Files with missing lines Patch % Lines
src/palletjack/version.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #178      +/-   ##
==========================================
+ Coverage   94.52%   95.69%   +1.16%     
==========================================
  Files           7        7              
  Lines        1133     1254     +121     
  Branches      148      147       -1     
==========================================
+ Hits         1071     1200     +129     
+ Misses         52       44       -8     
  Partials       10       10              

☔ 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.

@jacobdadams
Copy link
Member

@stdavis This should be a major version bump (there's a commit with feat! in it), but it's still doing a patch. Is that because the first commits pushed triggered a release candidate that was only a patch, so it's trying to keep with that instead of re-analyzing the version number?

@ugrc-release-bot ugrc-release-bot bot force-pushed the release-please--branches--main branch from d2dcea0 to 66159ba Compare January 5, 2026 20:48
@steveoh
Copy link
Member

steveoh commented Jan 6, 2026

I'm guessing because it was squashed? Maybe you can duplicate the message with an empty commit for the changelog and automation. In the future you may need to edit the squash commit message to play nice with conventional commits.

image

@stdavis
Copy link
Member

stdavis commented Jan 8, 2026

I agree with Steve's assessment, although, I frequently have issues getting major bumps to work correctly. You can force this PR to be a specific version by following these steps.

@ugrc-release-bot ugrc-release-bot bot force-pushed the release-please--branches--main branch from 66159ba to 56921f8 Compare January 9, 2026 16:50
@stdavis stdavis changed the title chore: release v5.2.13 chore: release v6.0.0 Jan 9, 2026
@stdavis stdavis force-pushed the release-please--branches--main branch from 56921f8 to f9d4241 Compare January 9, 2026 16:56
@jacobdadams jacobdadams merged commit f45e4ee into main Jan 9, 2026
5 checks passed
@jacobdadams jacobdadams deleted the release-please--branches--main branch January 9, 2026 16:58
@ugrc-release-bot
Copy link
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants