Skip to content

🔖(minor) bump release to 1.28.0 - #1634

Merged
lebaudantoine merged 1 commit into
mainfrom
release/1.28.0
Aug 24, 2026
Merged

🔖(minor) bump release to 1.28.0#1634
lebaudantoine merged 1 commit into
mainfrom
release/1.28.0

Conversation

@lebaudantoine

Copy link
Copy Markdown
Collaborator

No description provided.

@lebaudantoine
lebaudantoine merged commit f18d784 into main Aug 24, 2026
26 checks passed
@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Bump release version to 1.28.0

⚙️ Configuration changes 📝 Documentation 🕐 Less than 10 minutes

Grey Divider

AI Description

• Publish release 1.28.0 with date-stamped changelog entry
• Align version numbers across Python and Node packages to 1.28.0
• Keep repo-wide release metadata consistent for build/publish pipelines
Diagram

graph TD
  R["Release 1.28.0"] --> CL["CHANGELOG.md"]
  R --> A["agents/pyproject.toml"]
  R --> B["backend/pyproject.toml"]
  R --> S["summary/pyproject.toml"]
  R --> F["frontend/package.json"]
  R --> M["mail/package.json"]
  R --> K["sdk/package.json"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Single source of truth for version
  • ➕ Prevents drift between Python/Node package versions
  • ➕ Makes release bump a one-file change plus automation
  • ➖ Requires tooling to propagate version into multiple manifests
  • ➖ May not fit ecosystems that expect version in each manifest
2. Automated release tooling (e.g., semantic-release / changesets)
  • ➕ Generates changelog entries and bumps versions automatically
  • ➕ Reduces manual release errors and standardizes process
  • ➖ Non-trivial initial setup and CI integration
  • ➖ May require adopting conventional commit discipline

Recommendation: The current manual bump is appropriate for a straightforward release branch and keeps all package manifests aligned. If version drift has been an issue or releases are frequent, consider introducing a single version source (plus a small sync script) or adopting release automation to eliminate repetitive multi-file edits.

Files changed (7) +8 / -6

Documentation (1) +2 / -0
CHANGELOG.mdAdd 1.28.0 changelog section dated 2026-08-24 +2/-0

Add 1.28.0 changelog section dated 2026-08-24

• Introduces a new release header for version 1.28.0 with the release date. Leaves existing 'Added' entries under the new release section.

CHANGELOG.md

Other (6) +6 / -6
pyproject.tomlBump agents package version to 1.28.0 +1/-1

Bump agents package version to 1.28.0

• Updates the Python project version field from 1.27.0 to 1.28.0 for the agents package.

src/agents/pyproject.toml

pyproject.tomlBump backend (meet) package version to 1.28.0 +1/-1

Bump backend (meet) package version to 1.28.0

• Updates the backend Python project version from 1.27.0 to 1.28.0 in its pyproject metadata.

src/backend/pyproject.toml

package.jsonBump frontend package version to 1.28.0 +1/-1

Bump frontend package version to 1.28.0

• Updates the frontend Node package.json version from 1.27.0 to 1.28.0.

src/frontend/package.json

package.jsonBump mail_mjml package version to 1.28.0 +1/-1

Bump mail_mjml package version to 1.28.0

• Updates the mail template utility's package.json version from 1.27.0 to 1.28.0.

src/mail/package.json

package.jsonBump sdk package version to 1.28.0 +1/-1

Bump sdk package version to 1.28.0

• Updates the SDK package.json version from 1.27.0 to 1.28.0.

src/sdk/package.json

pyproject.tomlBump summary service version to 1.28.0 +1/-1

Bump summary service version to 1.28.0

• Updates the summary Python project's version field from 1.27.0 to 1.28.0.

src/summary/pyproject.toml

@sonarqubecloud

Copy link
Copy Markdown

@greptile-apps

greptile-apps Bot commented Aug 24, 2026

Copy link
Copy Markdown

Confidence Score: 5/5

The PR appears safe to merge because the release metadata is consistently updated across all affected components.

The changes are limited to synchronized version declarations, corresponding lock metadata, and the conventional changelog release transition, with no unresolved build or runtime inconsistency.

Important Files Changed

Filename Overview
CHANGELOG.md Adds the dated 1.28.0 release heading while retaining an empty Unreleased section for future changes.
src/agents/pyproject.toml Updates the agents project version to 1.28.0 in alignment with its lock file.
src/agents/uv.lock Synchronizes the locked local agents package metadata with version 1.28.0.
src/backend/pyproject.toml Updates the backend package version to 1.28.0 in alignment with its lock file.
src/backend/uv.lock Synchronizes the locked local backend package metadata with version 1.28.0.
src/frontend/package.json Updates the frontend package version to 1.28.0.
src/frontend/package-lock.json Keeps the frontend root lock metadata aligned with package.json.
src/mail/package.json Updates the mail package version to 1.28.0.
src/mail/package-lock.json Keeps the mail root lock metadata aligned with package.json.
src/sdk/package.json Updates the SDK workspace root version to 1.28.0.
src/sdk/package-lock.json Keeps the SDK root lock metadata aligned with package.json.
src/summary/pyproject.toml Updates the summary service version to 1.28.0; this service has no checked-in lock file requiring synchronization.

Reviews (1): Last reviewed commit: "🔖(minor) bump release to 1.28.0" | Re-trigger Greptile

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can switch off images and animations for a plain-text comment

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant