Skip to content

release: 0.132.0 - #202

Merged
rgarcia merged 3 commits into
mainfrom
release-please--branches--main--changes--next
Oct 27, 2026
Merged

rgarcia merged 3 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@kernel-internal

@kernel-internal kernel-internal Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Automated Release PR

0.132.0 (2026-10-26)

Features

  • Return last_used_at on API keys (001991a)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


Note

Low Risk
Additive optional response field on API key types with version/changelog-only packaging; no breaking changes to client behavior.

Overview
Release 0.132.0 bumps package version metadata (pyproject.toml, src/kernel/_version.py, release manifest) and documents the release in CHANGELOG.md.

The SDK change mirrors the API: APIKey responses now include optional last_used_at (last authenticated use, ~20-minute granularity; null if never used since tracking started). List/get/rotate and other endpoints that return APIKey pick up the field automatically via the shared type.

Reviewed by Cursor Bugbot for commit 6d5a1ef. Bugbot is set up for automated code reviews on this repo. Configure here.

Stainless-Generated-From: 959674773a75beaa802aca49638c53043f13ea1b

@rgarcia rgarcia 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.

Release 0.132.0: api_keys.last_used_at from kernel/kernel#4991.

@rgarcia
rgarcia merged commit 6512c8f into main Oct 27, 2026
11 checks passed
@kernel-internal

Copy link
Copy Markdown
Contributor Author

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.

1 participant