chore: bump lago-types to 0.1.23#45
Merged
Merged
Conversation
## Context PR #44 added the `/fees` endpoint type support (`FeeType`, `FeeFilters`, request/response shapes) to `lago-types`, but the version on crates.io (`0.1.22`) was published on May 11, before PR #44 merged on May 19. The published `0.1.22` does not contain the fee modules. Downstream consumers — including a follow-up `lago-client` PR that adds `list_fees` / `get_fee` methods, and the Lago Agent Toolkit MCP server — need a published `lago-types` release that includes the fee modules. ## Description Bumps `lago-types` from `0.1.22` to `0.1.23` so that the maintainer can `cargo publish` a release with PR #44's fee modules included. No code changes — purely a version bump to unblock downstream work.
jdenquin
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
lago-typesfrom0.1.22to0.1.23so a publish to crates.io can include the/feesendpoint type support that landed in #44.Context
PR #44 (merged May 19) added
FeeType,FeeFilters, and the request/response shapes for/fees. Butlago-types 0.1.22on crates.io was published on May 11 — before #44 merged — so the published package doesn't contain the fee modules.Downstream work is blocked on a release that includes them:
lago-clientPR that addslist_feesandget_feemethods + examplegetlago/lago-agent-toolkitthat exposes those methods as MCP toolsThis PR is intentionally minimal — just the version bump — so it can be merged and published quickly without coupling to the follow-up code changes.
What this PR does
lago-types/Cargo.toml:0.1.22→0.1.23Cargo.lock: regenerated accordinglyNo code changes.
Action requested
After merging, please
cargo publishfromlago-types/to push0.1.23to crates.io. The dry-run is clean locally:```
Packaging lago-types v0.1.23
Packaged 75 files, 324.7KiB (50.3KiB compressed)
Verifying lago-types v0.1.23
```
(75 files vs the 69 in the older 0.1.22 — the diff is the fee modules from #44.)
I'll open the lago-client follow-up PR as soon as 0.1.23 is on the registry.
Test plan