release: 0.2.0

[scalar-docs]

Automated Release PR

0.2.0 (2026-09-18)

Features

• api: initial SDK generation (860d43a)

---

The semver version number is based on included commit messages. To release a specific version,
edit this pull request title to release: 1.2.3 — Scalar re-creates this pull request at that
version, so wait for the Release PR version check to pass before merging.

Brought to you by Scalar

---

Note

Low Risk
Version and changelog-only changes with no functional SDK or dependency updates beyond the semver bump.

Overview
Automated release-please cut that publishes gumlet 0.2.0 (from 0.1.0).

The package version is updated in pyproject.toml, src/gumlet/_version.py, and .release-please-manifest.json. A new CHANGELOG.md documents 0.2.0 with the feature note for initial OpenAPI/Scalar SDK generation (860d43a). There are no runtime or API code changes in this diff—only release metadata.

^{Reviewed by Cursor Bugbot for commit aff816e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
36346183	Triggered	Generic High Entropy Secret	860d43a	src/gumlet/resources/image_sources.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
36346183	Triggered	Generic High Entropy Secret	860d43a	src/gumlet/resources/image_sources.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-actions]

🤖 Created releases:

• v0.2.0

🌻