Update release version from 0.1.2 to 0.1.0 by Aureliolo · Pull Request #288 · Aureliolo/synthorg

Aureliolo · 2026-03-11T06:13:41Z

No description provided.

Signed-off-by: Aurelio <19254254+Aureliolo@users.noreply.github.com>

coderabbitai · 2026-03-11T06:13:50Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 563ef450-670f-47d3-bb6f-7326e73beb57

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch Aureliolo-patch-1

✨ Simplify code

Create PR with simplified code
Commit simplified code in branch Aureliolo-patch-1

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Copilot

Pull request overview

This PR modifies the Release Please manifest to change the tracked current release version for the root Python package.

Changes:

Update .github/.release-please-manifest.json version for package . from 0.1.2 to 0.1.0.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-11T06:15:06Z

.github/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.1.2"
+  ".": "0.1.0"


The release-please manifest version is being downgraded to 0.1.0, but the repo currently advertises 0.1.2 in other release-tracked files (e.g., pyproject.toml and src/ai_company/init.py). This mismatch will likely cause Release Please to generate duplicate/incorrect next versions (e.g., v0.1.1) and can break the release/tagging pipeline. Align the manifest with the actual current released version (or, if intentionally resetting history, update all release-tracked files/tags consistently).

Suggested change

".": "0.1.0"

".": "0.1.2"

gemini-code-assist · 2026-03-11T06:15:21Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 modifies the project's release version as defined in the release-please configuration. The change sets the version to 0.1.0, which is a decrease from the previously recorded 0.1.2.

Highlights

Release Version Update: The project's release version has been updated in the .github/.release-please-manifest.json file. The version was changed from 0.1.2 to 0.1.0, indicating a version downgrade.

Changelog

.github/.release-please-manifest.json
- Updated the project's release version.

Activity

No specific activity or comments have been recorded for this pull request yet.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

greptile-apps · 2026-03-11T06:15:29Z

Greptile Summary

This PR rolls back all four version markers (release-please manifest, CHANGELOG.md, pyproject.toml, and src/ai_company/__init__.py) from 0.1.2 to 0.1.0. The net effect is a version downgrade across the entire release infrastructure for a package that has already shipped two subsequent patch releases.

Key concerns:

Release automation will break: With the manifest reset to 0.1.0, Release Please will try to produce v0.1.1 as the next release — a tag that already exists in the repository. This will cause the release workflow to fail or create a broken/duplicate release.
Runtime version skew: __version__ in src/ai_company/__init__.py and the commitizen version in pyproject.toml now report 0.1.0, while the published package on PyPI is at 0.1.2. Any code or tooling that inspects the installed package version will see a mismatch.
CHANGELOG comparison URL is broken: The new header links to compare/v0.0.0...v0.1.0. A v0.0.0 tag does not exist in the repository, so this link will 404.
Release history erased: The individual v0.1.1 and v0.1.2 CHANGELOG sections are removed, collapsing all feature entries (including those shipped in 0.1.1 and 0.1.2) under a single v0.1.0 entry — making the listed commits inconsistent with the stated comparison range.

Confidence Score: 1/5

This PR should not be merged as-is — it will break release automation and introduce a runtime/published version mismatch.
All four changed files participate in release infrastructure that has already moved past the target version. Merging resets the manifest to a version behind existing git tags, guaranteeing a conflict on the next automated release run. The CHANGELOG also loses documented release history and gains a broken comparison URL. There is no safe path to merging this without first deciding on the intended versioning strategy (e.g., deleting the old tags, or starting at 0.2.0 to skip the conflict zone).
CHANGELOG.md and .github/.release-please-manifest.json require the most attention — the manifest drives automation behavior and the changelog has both a broken anchor link and erased history.

Important Files Changed

Filename	Overview
.github/.release-please-manifest.json	Downgrades the Release Please manifest version from 0.1.2 to 0.1.0, which conflicts with already-published git tags (v0.1.1, v0.1.2) and will cause release automation failures.
CHANGELOG.md	Rewrites the top-level CHANGELOG header to v0.1.0 with a comparison URL referencing v0.0.0, which likely does not exist as a tag, and erases the documented release history for v0.1.1 and v0.1.2.
pyproject.toml	Downgrades the commitizen version field from 0.1.2 to 0.1.0; inconsistent with the already-published PyPI package at 0.1.2.
src/ai_company/init.py	Downgrades version from 0.1.2 to 0.1.0; this is the authoritative version string used by hatchling and reported at runtime.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Manifest as .release-please-manifest.json
    participant RP as Release Please Bot
    participant Git as Git Tags
    participant PyPI as PyPI / Package

    Note over Git: v0.1.1 ✅ already exists
    Note over Git: v0.1.2 ✅ already exists

    Dev->>Manifest: Sets version to "0.1.0" (this PR)
    Manifest-->>RP: Source of truth = 0.1.0

    RP->>RP: Next release = bump(0.1.0) → 0.1.1
    RP->>Git: Attempt to push tag v0.1.1
    Git-->>RP: ❌ Tag v0.1.1 already exists!

    alt Tag conflict scenario
        RP->>PyPI: Attempt to publish 0.1.1
        PyPI-->>RP: ❌ Version 0.1.1 already published
    end

    Note over Dev,PyPI: Current package at runtime reports __version__ = "0.1.0"<br/>but PyPI has 0.1.2 — version skew visible to users

_{Last reviewed commit: 90a70f3}

greptile-apps · 2026-03-11T06:15:33Z

.github/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.1.2"
+  ".": "0.1.0"


Version downgrade will conflict with existing git tags

This change sets the Release Please manifest back to 0.1.0, but versions 0.1.1 and 0.1.2 have already been fully released — both pyproject.toml and src/ai_company/__init__.py are currently pinned to "0.1.2", and git tags v0.1.1 and v0.1.2 exist in the repository.

Release Please uses this manifest as its source of truth for "the last released version." After merging this PR:

Release Please will calculate the next version by bumping from 0.1.0 (e.g. it will try to produce 0.1.1 again).

It will also attempt to rewrite pyproject.toml and src/ai_company/__init__.py (both listed as extra-files in release-please-config.json) from 0.1.2 back toward a 0.1.1-era value.

When it tries to push a tag, the v0.1.1 (and potentially v0.1.2) tag already exists — the release workflow will either fail or, worse, create a broken/duplicate release.

If the intent is to cut a fresh release cycle starting from a clean base, the manifest should be set to 0.1.2 (the actual last released version), not 0.1.0. Downgrading the manifest value is not a supported Release Please operation and will corrupt the automated release pipeline.

Suggested change

".": "0.1.0"

".": "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 downgrade will conflict with existing git tags** This change sets the Release Please manifest back to `0.1.0`, but versions `0.1.1` and `0.1.2` have already been fully released — both `pyproject.toml` and `src/ai_company/__init__.py` are currently pinned to `"0.1.2"`, and git tags `v0.1.1` and `v0.1.2` exist in the repository. Release Please uses this manifest as its source of truth for "the last released version." After merging this PR: 1. Release Please will calculate the next version by bumping from `0.1.0` (e.g. it will try to produce `0.1.1` again). 2. It will also attempt to rewrite `pyproject.toml` and `src/ai_company/__init__.py` (both listed as `extra-files` in `release-please-config.json`) from `0.1.2` back toward a `0.1.1`-era value. 3. When it tries to push a tag, the `v0.1.1` (and potentially `v0.1.2`) tag already exists — the release workflow will either fail or, worse, create a broken/duplicate release. If the intent is to cut a fresh release cycle starting from a clean base, the manifest should be set to `0.1.2` (the actual last released version), not `0.1.0`. Downgrading the manifest value is not a supported Release Please operation and will corrupt the automated release pipeline. ```suggestion ".": "0.1.2" ``` How can I resolve this? If you propose a fix, please make it concise.

gemini-code-assist

Code Review

This pull request downgrades the project's version in the .release-please-manifest.json from 0.1.2 to 0.1.0. This is a critical issue because release-please relies on this file to determine the next version number. Downgrading it will likely cause the release process to fail or attempt to re-release existing versions, as 0.1.1 and 0.1.2 are already present in the changelog. The version in this manifest should always correspond to the latest released version.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

gemini-code-assist · 2026-03-11T06:15:48Z

.github/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.1.2"
+  ".": "0.1.0"


Downgrading the version from 0.1.2 to 0.1.0 is incorrect and will disrupt the automated release workflow. The CHANGELOG.md confirms that versions 0.1.1 and 0.1.2 have already been released. This manifest file should always reflect the latest version to allow release-please to correctly calculate the next version. Please revert this to 0.1.2 to ensure the release process functions as expected.

Suggested change

".": "0.1.0"

".": "0.1.2"

…l, and __init__.py

greptile-apps · 2026-03-11T06:18:32Z

CHANGELOG.md

 # Changelog

-## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11)
+## [0.1.0](https://github.com/Aureliolo/ai-company/compare/v0.0.0...v0.1.0) (2026-03-11)


Comparison URL references a likely non-existent tag

The new header links to compare/v0.0.0...v0.1.0. A v0.0.0 tag does not appear to have ever been created in this repository — the project's first tracked release was v0.1.0. GitHub will render this comparison link as a 404, making the CHANGELOG entry non-functional for anyone trying to trace what changed.

If the intent is to mark this as the "initial" release, the conventional approach is to use the first commit SHA or the repository creation point, not an invented v0.0.0 tag.

Suggested change

## [0.1.0](https://github.com/Aureliolo/ai-company/compare/v0.0.0...v0.1.0) (2026-03-11)

## [0.1.0](https://github.com/Aureliolo/ai-company/releases/tag/v0.1.0) (2026-03-11)

Prompt To Fix With AI

This is a comment left during a code review. Path: CHANGELOG.md Line: 3 Comment: **Comparison URL references a likely non-existent tag** The new header links to `compare/v0.0.0...v0.1.0`. A `v0.0.0` tag does not appear to have ever been created in this repository — the project's first tracked release was `v0.1.0`. GitHub will render this comparison link as a 404, making the CHANGELOG entry non-functional for anyone trying to trace what changed. If the intent is to mark this as the "initial" release, the conventional approach is to use the first commit SHA or the repository creation point, not an invented `v0.0.0` tag. ```suggestion ## [0.1.0](https://github.com/Aureliolo/ai-company/releases/tag/v0.1.0) (2026-03-11) ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-03-11T06:18:33Z

CHANGELOG.md

 # Changelog

-## [0.1.2](https://github.com/Aureliolo/ai-company/compare/v0.1.1...v0.1.2) (2026-03-11)
+## [0.1.0](https://github.com/Aureliolo/ai-company/compare/v0.0.0...v0.1.0) (2026-03-11)


Release history for v0.1.1 and v0.1.2 is silently erased

The previous CHANGELOG.md had a header for [0.1.2] comparing v0.1.1...v0.1.2. After this change, any features or fixes that were specifically shipped in v0.1.1 and v0.1.2 are now all attributed to a single v0.1.0 entry. The feature list in the body of this section still contains commits from all three releases, which means the comparison URL (v0.0.0...v0.1.0) will not actually cover all the listed commits — those commits only exist up to v0.1.2.

Users, contributors, or automated tooling (e.g., dependency bots) that look at the CHANGELOG to understand what changed between versions will get inaccurate information. The two intermediate release sections should be preserved, not collapsed.

Prompt To Fix With AI

This is a comment left during a code review. Path: CHANGELOG.md Line: 3 Comment: **Release history for v0.1.1 and v0.1.2 is silently erased** The previous `CHANGELOG.md` had a header for `[0.1.2]` comparing `v0.1.1...v0.1.2`. After this change, any features or fixes that were specifically shipped in `v0.1.1` and `v0.1.2` are now all attributed to a single `v0.1.0` entry. The feature list in the body of this section still contains commits from all three releases, which means the comparison URL (`v0.0.0...v0.1.0`) will not actually cover all the listed commits — those commits only exist up to `v0.1.2`. Users, contributors, or automated tooling (e.g., dependency bots) that look at the CHANGELOG to understand what changed between versions will get inaccurate information. The two intermediate release sections should be preserved, not collapsed. How can I resolve this? If you propose a fix, please make it concise.

Update release version from 0.1.2 to 0.1.0

90d6962

Signed-off-by: Aurelio <19254254+Aureliolo@users.noreply.github.com>

Copilot AI review requested due to automatic review settings March 11, 2026 06:13

Copilot started reviewing on behalf of Aureliolo March 11, 2026 06:14 View session

Copilot AI reviewed Mar 11, 2026

View reviewed changes

greptile-apps bot reviewed Mar 11, 2026

View reviewed changes

gemini-code-assist bot reviewed Mar 11, 2026

View reviewed changes

chore: update version from 0.1.2 to 0.1.0 in changelog, pyproject.tom…

90a70f3

…l, and __init__.py

Aureliolo merged commit 223050d into release-please--branches--main--components--ai-company Mar 11, 2026
2 checks passed

Aureliolo deleted the Aureliolo-patch-1 branch March 11, 2026 06:16

greptile-apps bot reviewed Mar 11, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update release version from 0.1.2 to 0.1.0#288

Update release version from 0.1.2 to 0.1.0#288
Aureliolo merged 2 commits intorelease-please--branches--main--components--ai-companyfrom
Aureliolo-patch-1

Aureliolo commented Mar 11, 2026

Uh oh!

coderabbitai bot commented Mar 11, 2026 •

edited

Loading

Review skipped

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Mar 11, 2026

Uh oh!

gemini-code-assist bot commented Mar 11, 2026

Uh oh!

greptile-apps bot commented Mar 11, 2026 •

edited

Loading

Uh oh!

greptile-apps bot Mar 11, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Mar 11, 2026

Uh oh!

Uh oh!

greptile-apps bot Mar 11, 2026

Uh oh!

greptile-apps bot Mar 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	## [0.1.0](https://github.com/Aureliolo/ai-company/compare/v0.0.0...v0.1.0) (2026-03-11)
	## [0.1.0](https://github.com/Aureliolo/ai-company/releases/tag/v0.1.0) (2026-03-11)

Conversation

Aureliolo commented Mar 11, 2026

Uh oh!

coderabbitai bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot commented Mar 11, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

greptile-apps bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 1/5

Important Files Changed

Sequence Diagram

Uh oh!

greptile-apps bot Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

greptile-apps bot Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

coderabbitai bot commented Mar 11, 2026 •

edited

Loading

greptile-apps bot commented Mar 11, 2026 •

edited

Loading