Conversation
776d164 to
bc691ef
Compare
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request automates the release of version 0.1.2 for the ai-company project. It primarily focuses on updating the project's version number across configuration files and the main init.py file, alongside documenting recent CI/CD dependency updates in the changelog. This ensures that the project's metadata reflects the latest release and provides transparency regarding continuous integration improvements. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
📝 WalkthroughWalkthroughPatch-level version bump from 0.1.1 to 0.1.2 across release manifest, pyproject/commitizen metadata, package Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Greptile SummaryThis is an automated Release Please PR intended to release Key issues:
Confidence Score: 0/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["Release Please bot runs"] --> B{"Resolves base tag?"}
B -- "Yes → v0.1.1" --> C["Compute next version: 0.1.2"]
B -- "No — tag format mismatch\n(ai-company-v0.1.1 vs v0.1.1)" --> D["Falls back to v0.0.0 as base"]
D --> E["Computes next version: 0.1.0 ❌"]
C --> F["Writes 0.1.2 to manifest,\npyproject.toml, __init__.py,\nCHANGELOG ✅"]
E --> G["Writes 0.1.0 to manifest,\npyproject.toml, __init__.py,\nCHANGELOG ❌"]
G --> H["PR #283 as merged would\nregress version 0.1.1 → 0.1.0"]
F --> I["Correct 0.1.2 release"]
Last reviewed commit: 223050d |
There was a problem hiding this comment.
Code Review
This pull request automates the release of version 0.1.2, primarily involving version number updates across several project files. The changes are straightforward and align with the release process. However, I've identified a minor inconsistency in the CHANGELOG.md file, where some dependency updates listed in the pull request description are missing. I have provided a suggestion to correct this and ensure the changelog is complete.
| * bump anchore/scan-action from 6.5.1 to 7.3.2 ([#271](https://github.com/Aureliolo/ai-company/issues/271)) ([80a1c15](https://github.com/Aureliolo/ai-company/commit/80a1c157c69031d2d18beca6511edf5031e8595b)) | ||
| * bump docker/build-push-action from 6.19.2 to 7.0.0 ([#273](https://github.com/Aureliolo/ai-company/issues/273)) ([dd0219e](https://github.com/Aureliolo/ai-company/commit/dd0219e27d3142cfe697f0f51beff71ad14e6c17)) | ||
| * bump docker/login-action from 3.7.0 to 4.0.0 ([#272](https://github.com/Aureliolo/ai-company/issues/272)) ([33d6238](https://github.com/Aureliolo/ai-company/commit/33d6238d7d62a7c7c4902aa6a0f0108e66c7c7fc)) | ||
| * bump docker/metadata-action from 5.10.0 to 6.0.0 ([#270](https://github.com/Aureliolo/ai-company/issues/270)) ([baee04e](https://github.com/Aureliolo/ai-company/commit/baee04e81d5664317a4835a0cec315316b47d6b7)) |
There was a problem hiding this comment.
The changelog appears to be missing a couple of dependency bump entries that are present in the pull request description. To ensure the changelog is complete and easy to navigate, I've added the missing entries and sorted the entire list by their corresponding pull request number.
| * bump anchore/scan-action from 6.5.1 to 7.3.2 ([#271](https://github.com/Aureliolo/ai-company/issues/271)) ([80a1c15](https://github.com/Aureliolo/ai-company/commit/80a1c157c69031d2d18beca6511edf5031e8595b)) | |
| * bump docker/build-push-action from 6.19.2 to 7.0.0 ([#273](https://github.com/Aureliolo/ai-company/issues/273)) ([dd0219e](https://github.com/Aureliolo/ai-company/commit/dd0219e27d3142cfe697f0f51beff71ad14e6c17)) | |
| * bump docker/login-action from 3.7.0 to 4.0.0 ([#272](https://github.com/Aureliolo/ai-company/issues/272)) ([33d6238](https://github.com/Aureliolo/ai-company/commit/33d6238d7d62a7c7c4902aa6a0f0108e66c7c7fc)) | |
| * bump docker/metadata-action from 5.10.0 to 6.0.0 ([#270](https://github.com/Aureliolo/ai-company/issues/270)) ([baee04e](https://github.com/Aureliolo/ai-company/commit/baee04e81d5664317a4835a0cec315316b47d6b7)) | |
| * bump docker/metadata-action from 5.10.0 to 6.0.0 ([#270](https://github.com/Aureliolo/ai-company/issues/270)) ([baee04e](https://github.com/Aureliolo/ai-company/commit/baee04e81d5664317a4835a0cec315316b47d6b7)) | |
| * bump anchore/scan-action from 6.5.1 to 7.3.2 ([#271](https://github.com/Aureliolo/ai-company/issues/271)) ([80a1c15](https://github.com/Aureliolo/ai-company/commit/80a1c157c69031d2d18beca6511edf5031e8595b)) | |
| * bump docker/login-action from 3.7.0 to 4.0.0 ([#272](https://github.com/Aureliolo/ai-company/issues/272)) ([33d6238](https://github.com/Aureliolo/ai-company/commit/33d6238d7d62a7c7c4902aa6a0f0108e66c7c7fc)) | |
| * bump docker/build-push-action from 6.19.2 to 7.0.0 ([#273](https://github.com/Aureliolo/ai-company/issues/273)) ([dd0219e](https://github.com/Aureliolo/ai-company/commit/dd0219e27d3142cfe697f0f51beff71ad14e6c17)) | |
| * bump docker/setup-buildx-action from 3.12.0 to 4.0.0 ([#274](https://github.com/Aureliolo/ai-company/issues/274)) ([5fc06f7](https://github.com/Aureliolo/ai-company/commit/5fc06f72c4d067cf0ea157f469e9bc0214cfc6ca)) | |
| * bump sigstore/cosign-installer from 3.9.1 to 4.1.0 ([#275](https://github.com/Aureliolo/ai-company/issues/275)) ([29dd16c](https://github.com/Aureliolo/ai-company/commit/29dd16c37ae148ff509d19627a9e884160292263)) |
There was a problem hiding this comment.
Pull request overview
Release-please generated release PR for ai-company v0.1.2, updating the project’s version metadata and changelog to publish the next patch release.
Changes:
- Bump package version to
0.1.2(Hatch version source insrc/ai_company/__init__.py). - Update Commitizen version to
0.1.2for consistent tagging/changelog tooling. - Update Release Please manifest and prepend
CHANGELOG.mdwith the0.1.2release notes.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/ai_company/__init__.py |
Updates the canonical package version used by Hatch dynamic versioning. |
pyproject.toml |
Bumps Commitizen’s tracked version to match the release. |
CHANGELOG.md |
Adds the 0.1.2 changelog entry for the release. |
.github/.release-please-manifest.json |
Updates Release Please manifest version to 0.1.2. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bc691ef to
e7c635a
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 3: The changelog compare URL currently uses component-prefixed tags
("ai-company-v0.1.1...ai-company-v0.1.2") which are incorrect for this repo;
update the link in the heading string "##
[0.1.2](https://github.com/Aureliolo/ai-company/compare/ai-company-v0.1.1...ai-company-v0.1.2)
(2026-03-10)" to use plain tags "v0.1.1...v0.1.2" so the URL becomes
".../compare/v0.1.1...v0.1.2" ensuring the GitHub compare page resolves
correctly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 03f364d7-1e6a-4e8f-8d0b-503f117ddff7
📒 Files selected for processing (4)
.github/.release-please-manifest.jsonCHANGELOG.mdpyproject.tomlsrc/ai_company/__init__.py
📜 Review details
🧰 Additional context used
📓 Path-based instructions (5)
**/*.py
📄 CodeRabbit inference engine (CLAUDE.md)
**/*.py: Use Python 3.14+ (PEP 649 native lazy annotations) — do NOT usefrom __future__ import annotations
Use PEP 758 except syntax:except A, B:(no parentheses) — ruff enforces this on Python 3.14
All public functions and classes must have type hints — mypy strict mode is enforced
All public classes and functions must have Google-style docstrings — enforced by ruff D rules
Create new objects instead of mutating existing ones (immutability principle); for non-Pydantic internal collections, usecopy.deepcopy()at construction andMappingProxyTypewrapping for read-only enforcement
Fordict/listfields in frozen Pydantic models, rely onfrozen=Truefor field reassignment prevention andcopy.deepcopy()at system boundaries (tool execution, LLM provider serialization, inter-agent delegation, serializing for persistence)
Separate frozen Pydantic models for config/identity from mutable-via-copy models for runtime state that evolves; never mix static config fields with mutable runtime fields in one model
Use Pydantic v2 (BaseModel,model_validator,computed_field,ConfigDict); use@computed_fieldfor derived values instead of storing redundant fields; useNotBlankStrfor all identifier/name fields instead of manual whitespace validators
Preferasyncio.TaskGroupfor fan-out/fan-in parallel operations in new code (e.g. multiple tool invocations, parallel agent calls) over barecreate_taskfor structured concurrency
Line length: 88 characters maximum — enforced by ruff
Keep functions under 50 lines and files under 800 lines
Handle errors explicitly, never silently swallow exceptions
Validate at system boundaries (user input, external APIs, config files)
All provider calls must go throughBaseCompletionProviderwhich applies retry and rate limiting automatically — never implement retry logic in driver subclasses or calling code
RetryConfig and RateLimiterConfig are set per-provider inProviderConfig; retryable errors (RateLimitError, ...
Files:
src/ai_company/__init__.py
src/**/*.py
📄 CodeRabbit inference engine (CLAUDE.md)
src/**/*.py: Every module with business logic MUST import logging fromai_company.observabilitywithlogger = get_logger(__name__)— never useimport logging,logging.getLogger(), orprint()in application code
Always use constants from domain-specific modules underai_company.observability.eventsfor event names (e.g.,PROVIDER_CALL_STARTfromevents.provider), importing directly:from ai_company.observability.events.<domain> import EVENT_CONSTANT
Use structured logging kwargs: alwayslogger.info(EVENT, key=value)— neverlogger.info("msg %s", val)
All error paths must log at WARNING or ERROR with context before raising; all state transitions must log at INFO; DEBUG for object creation, internal flow, entry/exit of key functions
Pure data models, enums, and re-exports do NOT need logging
Use absolute paths or run commands directly in Bash — never usecdin Bash commands; working directory is already set to project root
Files:
src/ai_company/__init__.py
.github/.release-please-manifest.json
📄 CodeRabbit inference engine (CLAUDE.md)
Release Please manifest tracks version state; merging release PR creates git tag (
vX.Y.Z) + GitHub Release with changelog; tag push triggers Docker workflow for version-tagged images
Files:
.github/.release-please-manifest.json
**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
Vendor names (Anthropic, OpenAI, Claude, GPT, etc.) may only appear in DESIGN_SPEC.md when listing supported providers (not in other markdown files)
Files:
CHANGELOG.md
pyproject.toml
📄 CodeRabbit inference engine (CLAUDE.md)
pyproject.toml: Pin all dependency versions using==inpyproject.toml; organize into groups:test(pytest + plugins),dev(includes test + ruff, mypy, pre-commit, commitizen); install withuv sync
Version inpyproject.tomlunder[tool.commitizen].versionis used by CI to tag Docker images (semver)
Files:
pyproject.toml
🧠 Learnings (4)
📚 Learning: 2026-03-10T22:19:11.971Z
Learnt from: CR
Repo: Aureliolo/ai-company PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-10T22:19:11.971Z
Learning: Applies to .github/.release-please-manifest.json : Release Please manifest tracks version state; merging release PR creates git tag (`vX.Y.Z`) + GitHub Release with changelog; tag push triggers Docker workflow for version-tagged images
Applied to files:
.github/.release-please-manifest.json
📚 Learning: 2026-03-10T22:19:11.971Z
Learnt from: CR
Repo: Aureliolo/ai-company PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-10T22:19:11.971Z
Learning: Applies to .github/release-please-config.json : Release Please (Google) auto-creates a release PR on every push to main; config in `.github/release-please-config.json` and `.github/.release-please-manifest.json`; uses `RELEASE_PLEASE_TOKEN` secret so tag creation triggers downstream workflows
Applied to files:
.github/.release-please-manifest.json
📚 Learning: 2026-03-10T22:19:11.971Z
Learnt from: CR
Repo: Aureliolo/ai-company PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-10T22:19:11.971Z
Learning: Applies to pyproject.toml : Version in `pyproject.toml` under `[tool.commitizen].version` is used by CI to tag Docker images (semver)
Applied to files:
pyproject.toml
📚 Learning: 2026-03-10T22:19:11.971Z
Learnt from: CR
Repo: Aureliolo/ai-company PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-10T22:19:11.971Z
Learning: Commit messages follow `<type>: <description>` format with types: feat, fix, refactor, docs, test, chore, perf, ci — enforced by commitizen (commit-msg hook)
Applied to files:
pyproject.toml
🪛 LanguageTool
CHANGELOG.md
[style] ~3-~3: Consider using the typographical ellipsis character here instead.
Context: # Changelog ## 0.1.2 (2026-03-10) ### Fe...
(ELLIPSIS)
🔇 Additional comments (3)
src/ai_company/__init__.py (1)
3-3: Version constant is aligned.This keeps the package-exported version in sync with the rest of the release metadata.
pyproject.toml (1)
197-197: Commitizen version bump looks correct.
[tool.commitizen].versionnow matches the package and manifest bump, so CI tagging stays aligned for this release.Based on learnings, version in
pyproject.tomlunder[tool.commitizen].versionis used by CI to tag Docker images (semver)..github/.release-please-manifest.json (1)
2-2: Manifest bump is consistent.This keeps Release Please’s tracked version state aligned with the package metadata for
0.1.2.Based on learnings, Release Please manifest tracks version state; merging release PR creates git tag (
vX.Y.Z) + GitHub Release with changelog; tag push triggers Docker workflow for version-tagged images.
e7c635a to
f334cc4
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
f334cc4 to
4270854
Compare
4270854 to
28d5e5b
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CHANGELOG.md
Outdated
| @@ -1,5 +1,150 @@ | |||
| # Changelog | |||
|
|
|||
| ## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11) | |||
There was a problem hiding this comment.
The 0.1.2 compare link uses v0.1.1...v0.1.2, but the existing 0.1.1 entry below still uses ai-company-v0.1.0...ai-company-v0.1.1. If the repo only has one of these tag formats, one of the changelog links will be broken. Suggest aligning changelog compare URLs to the actual tag format used by Release Please/Commitizen (or updating both 0.1.2 and 0.1.1 headers to be consistent).
| ## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11) | |
| ## [0.1.2](https://github.com/Aureliolo/ai-company/compare/ai-company-v0.1.1...ai-company-v0.1.2) (2026-03-11) |
Signed-off-by: Aurelio <19254254+Aureliolo@users.noreply.github.com>
|
🤖 Created releases: 🌻 |
| @@ -1,3 +1,3 @@ | |||
| { | |||
| ".": "0.1.1" | |||
| ".": "0.1.0" | |||
There was a problem hiding this comment.
Version regression in manifest
The manifest is being changed from 0.1.1 to 0.1.0, which is a downgrade, not the 0.1.2 bump indicated by the PR title and description. This file is Release Please's source of truth for the current published version — setting it to 0.1.0 when the repo is already at 0.1.1 will confuse subsequent Release Please runs, potentially causing it to re-release 0.1.0 content or compute the next version incorrectly.
The expected value after a successful 0.1.2 release should be:
| ".": "0.1.0" | |
| ".": "0.1.2" |
This regression appears to stem from the same root cause as the version mismatch in pyproject.toml and src/ai_company/__init__.py (see those comments). The Release Please bot may have computed the wrong base version due to the tag-format migration (ai-company-v0.1.x → v0.1.x), causing it to regenerate a 0.1.0 release instead of computing 0.1.2.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/.release-please-manifest.json
Line: 2
Comment:
**Version regression in manifest**
The manifest is being changed from `0.1.1` to `0.1.0`, which is a **downgrade**, not the `0.1.2` bump indicated by the PR title and description. This file is Release Please's source of truth for the current published version — setting it to `0.1.0` when the repo is already at `0.1.1` will confuse subsequent Release Please runs, potentially causing it to re-release `0.1.0` content or compute the next version incorrectly.
The expected value after a successful `0.1.2` release should be:
```suggestion
".": "0.1.2"
```
This regression appears to stem from the same root cause as the version mismatch in `pyproject.toml` and `src/ai_company/__init__.py` (see those comments). The Release Please bot may have computed the wrong base version due to the tag-format migration (`ai-company-v0.1.x` → `v0.1.x`), causing it to regenerate a `0.1.0` release instead of computing `0.1.2`.
How can I resolve this? If you propose a fix, please make it concise.| [tool.commitizen] | ||
| name = "cz_conventional_commits" | ||
| version = "0.1.1" # x-release-please-version | ||
| version = "0.1.0" # x-release-please-version |
There was a problem hiding this comment.
Version downgraded instead of bumped
The commitizen version marker is being changed from 0.1.1 to 0.1.0, which is a regression. The PR title states this is a 0.1.2 release, so the marker should be bumped to 0.1.2. Merging this as-is will cause commitizen to report the package version as 0.1.0, behind the already-published 0.1.1.
| version = "0.1.0" # x-release-please-version | |
| version = "0.1.2" # x-release-please-version |
The same incorrect version appears in src/ai_company/__init__.py line 3 and .github/.release-please-manifest.json.
Prompt To Fix With AI
This is a comment left during a code review.
Path: pyproject.toml
Line: 199
Comment:
**Version downgraded instead of bumped**
The commitizen version marker is being changed from `0.1.1` to `0.1.0`, which is a **regression**. The PR title states this is a `0.1.2` release, so the marker should be bumped to `0.1.2`. Merging this as-is will cause `commitizen` to report the package version as `0.1.0`, behind the already-published `0.1.1`.
```suggestion
version = "0.1.2" # x-release-please-version
```
The same incorrect version appears in `src/ai_company/__init__.py` line 3 and `.github/.release-please-manifest.json`.
How can I resolve this? If you propose a fix, please make it concise.| """AI Company - Framework for orchestrating autonomous AI agents.""" | ||
|
|
||
| __version__ = "0.1.1" # x-release-please-version | ||
| __version__ = "0.1.0" # x-release-please-version |
There was a problem hiding this comment.
Package __version__ regresses to 0.1.0
__version__ is being set to 0.1.0 instead of 0.1.2. Any code or tooling that introspects importlib.metadata.version("ai-company") or ai_company.__version__ will see 0.1.0, even though 0.1.1 has already shipped. This can break version-gated behaviour in downstream consumers and CI pipelines that compare __version__.
| __version__ = "0.1.0" # x-release-please-version | |
| __version__ = "0.1.2" # x-release-please-version |
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/ai_company/__init__.py
Line: 3
Comment:
**Package `__version__` regresses to `0.1.0`**
`__version__` is being set to `0.1.0` instead of `0.1.2`. Any code or tooling that introspects `importlib.metadata.version("ai-company")` or `ai_company.__version__` will see `0.1.0`, even though `0.1.1` has already shipped. This can break version-gated behaviour in downstream consumers and CI pipelines that compare `__version__`.
```suggestion
__version__ = "0.1.2" # x-release-please-version
```
How can I resolve this? If you propose a fix, please make it concise.| @@ -1,5 +1,150 @@ | |||
| # Changelog | |||
|
|
|||
| ## [0.1.0](https://github.com/Aureliolo/ai-company/compare/v0.0.0...v0.1.0) (2026-03-11) | |||
There was a problem hiding this comment.
CHANGELOG section targets wrong version and wrong base tag
This new section is labelled [0.1.0] and its compare URL reads v0.0.0...v0.1.0, but the PR title and description clearly state this should be a 0.1.2 release. As a result:
- The CHANGELOG now has
[0.1.0]appearing above the already-present[0.1.1]entry (line 152 in the pre-PR file), putting the changelog in reverse-semantic-version order. - All the features listed here (JWT auth, Docker, Release Please, etc.) belong to the
0.1.2milestone, not0.1.0. - The compare URL should be
v0.1.1...v0.1.2to correctly link the diff between the two releases.
The header should read:
## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11)
This is caused by the same Release Please version-computation error that affects the manifest and version files — the bot apparently resolved the base version to 0.0.0 (i.e., it couldn't find the v0.1.1 tag) and generated a fresh 0.1.0 entry instead of incrementing to 0.1.2.
Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 3
Comment:
**CHANGELOG section targets wrong version and wrong base tag**
This new section is labelled `[0.1.0]` and its compare URL reads `v0.0.0...v0.1.0`, but the PR title and description clearly state this should be a `0.1.2` release. As a result:
1. The CHANGELOG now has `[0.1.0]` appearing **above** the already-present `[0.1.1]` entry (line 152 in the pre-PR file), putting the changelog in reverse-semantic-version order.
2. All the features listed here (JWT auth, Docker, Release Please, etc.) belong to the `0.1.2` milestone, not `0.1.0`.
3. The compare URL should be `v0.1.1...v0.1.2` to correctly link the diff between the two releases.
The header should read:
```
## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11)
```
This is caused by the same Release Please version-computation error that affects the manifest and version files — the bot apparently resolved the base version to `0.0.0` (i.e., it couldn't find the `v0.1.1` tag) and generated a fresh `0.1.0` entry instead of incrementing to `0.1.2`.
How can I resolve this? If you propose a fix, please make it concise.
🤖 I have created a release beep boop
0.1.0 (2026-03-11)
Features
Bug Fixes
Performance
Refactoring
Documentation
Tests
CI/CD
Maintenance
This PR was generated with Release Please. See documentation.