Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ShipEngine/shipengine-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.0.2
Choose a base ref
...
head repository: ShipEngine/shipengine-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.0.0
Choose a head ref
  • 10 commits
  • 4 files changed
  • 3 contributors

Commits on Dec 16, 2025

  1. feat!: drop Python 3.7-3.9 support, add Python 3.10-3.13 support 

    BREAKING CHANGE: Python 3.7, 3.8, and 3.9 are no longer supported. Minimum required Python version is now 3.10.

- Update python dependency from ^3.7 to ^3.10
- Update classifiers to list Python 3.10, 3.11, 3.12, 3.13
- Update aiohttp to ^3.9.0 for Python 3.10+ compatibility
- Update dev dependencies: pytest ^7.0.0, black ^22.0.0, flake8 ^6.0.0
- Fix black target-version typo and update to py310

This change aligns with the CI configuration that tests against Python 3.10-3.13 and uses updated package versions compatible with these Python versions.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
    @semarj @claude
    semarj and claude committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    7559751 View commit details
    Browse the repository at this point in the history

  2. Merge pull request #40 from ShipEngine/update-python-version-support 

    feat!: drop Python 3.7-3.9 support, add Python 3.10-3.13 support
    @semarj
    semarj authored Dec 16, 2025
    Configuration menu
    Copy the full SHA
    bc0d843 View commit details
    Browse the repository at this point in the history

  3. fix: add release-please v4 configuration files 

    Add required configuration for release-please v4:
- .release-please-manifest.json: Tracks current version (1.0.0)
- release-please-config.json: Configures release strategy for Python package

Without these files, release-please v4 cannot properly detect and bump
versions for breaking changes. This will allow the breaking change in
commit 7559751 to properly trigger a major version bump to 2.0.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
    @semarj @claude
    semarj and claude committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    b927df2 View commit details
    Browse the repository at this point in the history

  4. Merge pull request #42 from ShipEngine/fix-release-please-config 

    fix: add release-please v4 configuration files
    @semarj
    semarj authored Dec 16, 2025
    Configuration menu
    Copy the full SHA
    1fcb54c View commit details
    Browse the repository at this point in the history

  5. fix: update release-please manifest to current version 1.0.2 

    The manifest was set to 1.0.0 but the actual codebase is at 1.0.2
(per pyproject.toml and CHANGELOG.md). This caused release-please to
look at all commits since 1.0.0 and bump to 1.0.1 instead of properly
detecting the breaking change (commit 7559751) that should bump to 2.0.0.

By setting the manifest to 1.0.2, release-please will only consider
commits after that version, properly detecting the breaking change
and bumping to 2.0.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
    @semarj @claude
    semarj and claude committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    6d27544 View commit details
    Browse the repository at this point in the history

  6. Merge pull request #44 from ShipEngine/fix-manifest-version 

    fix: update release-please manifest to current version 1.0.2
    @semarj
    semarj authored Dec 16, 2025
    Configuration menu
    Copy the full SHA
    6da380f View commit details
    Browse the repository at this point in the history

  7. chore: trigger release-please to regenerate with v1.0.2 baseline

    @semarj
    semarj committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    9fc7feb View commit details
    Browse the repository at this point in the history

  8. chore: trigger release-please to regenerate PR

    @semarj
    semarj committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    155e3f3 View commit details
    Browse the repository at this point in the history

  9. chore: release 2.0.0

    @semarj
    semarj committed Dec 16, 2025
    Configuration menu
    Copy the full SHA
    97081ed View commit details
    Browse the repository at this point in the history

  10. Merge pull request #48 from ShipEngine/release-2.0.0 

    chore: release 2.0.0
    @semarj
    semarj authored Dec 16, 2025
    Configuration menu
    Copy the full SHA
    c433d71 View commit details
    Browse the repository at this point in the history
Loading