This patch bundles the fixes and tweaks from issue #20 to shore up stability and performance, making the codebase more reliable and integrations smoother. It’s strictly a bug-fix release, so users should see fewer errors and a more consistent experience.

justanotherbyte pushed a patch update to the main branch, bumping autumn’s version from 3.1.5 to 3.1.6.

Adding the hosted_invoice_url field to the CustomerInvoice model ensures invoice links are included in customers.get responses, aligning with the autumn-js interface. This small change enhances functionality by providing direct access to hosted invoice URLs without breaking existing integrations. However, documentation still needs updating and client code should be reviewed to handle the new field appropriately.

justanotherbyte pushed to main a commit by jeremylevasseur fixing the CustomerInvoice model by adding a missing hosted_invoice_url field, ensuring invoice URLs are included in the data.

justanotherbyte pushed an update to the main branch, tweaking the GitHub Actions publish workflow to include ASGI dependencies during installation. This ensures the CI step now installs tests, aio, and asgi extras before running pytest.

This patch addresses the two issues tracked in #18 and #19, squashing minor bugs and tightening up stability. It’s a bug-fix release, so users and integrators should upgrade to enjoy smoother, more reliable behavior.

justanotherbyte pushed a patch bump on the main branch, updating the autumn package version in __init__.py from 3.1.4 to 3.1.5. This routine chore keeps the release version up to date.

justanotherbyte pushed jeremylevasseur’s fix to the main branch, updating the Customer model to include missing payment_method and referrals fields and introducing new ReferredCustomer and CustomerReferral classes to better support referral data.

This change adds payment_method and referrals fields to the Customer model and introduces new CustomerReferral and ReferredCustomer types so that expanded query responses include payment method and referral data. By aligning the Python client with the autumn-js interface, it ensures those fields are no longer dropped and improves data completeness. However, documentation wasn’t updated, the payment_method field remains loosely typed as Any, and test coverage for the new referral models may be insufficient.

This change adds a missing force_checkout parameter to the checkout method and its stub, enabling callers to force a checkout URL in the Autumn client. It enhances the client’s flexibility without altering existing default behavior. However, documentation remains outdated and additional tests or examples may be needed to validate and illustrate the new parameter.

justanotherbyte pushed jeremylevasseur’s fix to main, adding the missing force_checkout boolean parameter (defaulting to False) to both the async stubs and the Client.checkout method. This small patch closes an oversight in the checkout API so callers can now explicitly force a checkout session.

This patch release is a bug fix that resolves a major compatibility issue with the JavaScript SDK, restoring smooth integration for web projects. Upgrading to v3.1.4 ensures users and integrators won’t run into errors when using the JS SDK.

justanotherbyte pushed a chore commit on main, bumping the autumn package version in autumn/init.py from 3.1.1 to 3.1.4. This version bump prepares the project for its next release.

justanotherbyte pushed a new commit that applies isort and black formatting and refactors the snake_to_camel conversion to use a regex. jeremylevasseur’s recent PRs improved the snake-to-camel function, fixed formatting issues, added ASGI dependencies to the CI job, and made tests compatible with Python 3.9.

A regex-based camelCase-to-snake_case mapping has been added to the payload builder so that autumn-py can accept camelCase parameters from autumn-js hooks and stop returning 400 errors. The change preserves backward compatibility and is verified by new tests on the attach, check, and track routes, improving cross-language interoperability. Potential issues include regex performance overhead, edge cases with conflicting parameter names, and missing documentation updates.

John Yeocx pushed to the main branch, bumping Autumn from v3.1.0 to v3.1.1. The update adds an optional quantity field to the CustomerProduct model for more accurate product tracking.

This release kicks off the new model documentation and corrects the version number and parameter formatting to resolve earlier inconsistencies, making integration and usage more reliable. It’s a mix of a minor feature (docs) and bug fixes, so users and integrators will now have clearer guidance and fewer hiccups.

The change bumps the library from version 3.0.4 to 3.1.0 while reformatting several modules, correcting an incorrectly passed positional parameter by naming the expand argument, and standardizing overload signatures and import order. It mainly improves type annotations and code style consistency in preparation for a new release without altering core functionality. Key concerns include pending test and lint checks, the introduction of # type: ignore stubs, and the lack of a descriptive changelog which may conceal breaking changes for consumers.

justanotherbyte pushed an update to the main branch of autumn, bumping the version from 3.0.4 to 3.1.0. They also reformatted function signatures and import statements and fixed an incorrect parameter passing (adding expand=) in entity and customer endpoints for more consistent API calls.

On the main branch, johnyeocx bumped the autumn package to version 3.0.4 and updated both Customers and Entities clients to accept an optional expand parameter on their get methods. This change lets callers request related fields (like invoices, rewards, entities, referrals or payment methods) via query parameters.