Skip to content

chore(main): release 0.28.0 - #728

Merged
neubig merged 1 commit into
mainfrom
release-please--branches--main--components--extensions
Oct 5, 2026
Merged

neubig merged 1 commit into
mainfrom
release-please--branches--main--components--extensions

Conversation

@openhands-release-bot

@openhands-release-bot openhands-release-bot Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.28.0 (2026-10-05)

What's Changed

Features

Bug Fixes

Documentation

Maintenance

New Contributors

Full Changelog: v0.27.0...v0.28.0


This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot added the type: chore Maintenance / chores label Oct 4, 2026
@openhands-release-bot
openhands-release-bot Bot force-pushed the release-please--branches--main--components--extensions branch 2 times, most recently from 0b6fb3f to 9fe50e9 Compare October 4, 2026 14:24
@openhands-release-bot openhands-release-bot Bot changed the title chore(main): release 0.27.1 chore(main): release 0.28.0 Oct 4, 2026
@openhands-release-bot
openhands-release-bot Bot force-pushed the release-please--branches--main--components--extensions branch from 9fe50e9 to 66b2f8b Compare October 4, 2026 14:46

@all-hands-bot all-hands-bot 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.

This review was posted by an AI agent (OpenHands).

Review: chore(main): release 0.28.0

Scope: This is a release-please version-bump PR owned by this repository. It only bumps the version to 0.28.0 across the four files release-please is configured to touch, which is exactly in scope for OpenHands/extensions. No product/architecture decision is required.

Verification performed on head 66b2f8b:

  • All four version sites are consistent at 0.28.0: package.json, pyproject.toml ([project].version), python/openhands_extensions/_version.py (_FALLBACK_VERSION, with the # x-release-please-version annotation correctly kept on the assignment line), and .release-please-manifest.json. A grep finds no stray 0.27.0 references.
  • uv run pytest tests/test_version_alignment.py -q -> 3 passed. This is the repository's own guard against JS/Python version drift.
  • The changelog body covers exactly the four merged PRs since v0.27.0 (#602, #686, #696, #725); each is confirmed merged on GitHub, and no additional non-merge commits exist in v0.27.0..66b2f8b. The new-contributor note for @Rohithmatham12 matches #696.
  • GitHub Actions for this head are green (including test, check, check-pr-artifacts, sync-extensions, sync-sdk-skill, validate-claude-code, and the pr-title checks).

Findings: None material. The change is a mechanical, correctly-generated release bump with no behavioral or security impact.

✅ APPROVED

@openhands-release-bot
openhands-release-bot Bot force-pushed the release-please--branches--main--components--extensions branch 6 times, most recently from 88faa46 to d284b2f Compare October 4, 2026 20:54
@all-hands-bot
all-hands-bot requested a review from neubig October 4, 2026 21:02
@openhands-release-bot
openhands-release-bot Bot force-pushed the release-please--branches--main--components--extensions branch 2 times, most recently from ef8073e to 17728ba Compare October 4, 2026 21:32

@neubig neubig left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Good taste

The release PR is a minimal, internally consistent version bump across the manifest, npm package, Python project, and fallback version. It adds no dependencies, executable scripts, workflow behavior, secrets, or product behavior. The head is mergeable, all applicable CI checks pass, and this content-only release bookkeeping is exempt from runtime/screenshot evidence.

[RISK ASSESSMENT]

  • [Overall PR] ⚠️ Risk Assessment: 🟢 LOW
    Mechanical release metadata only; no supply-chain or runtime surface is introduced.

VERDICT:
✅ Worth merging: The release metadata is synchronized and CI is green.

KEY INSIGHT:
The change preserves one version value consistently across every published package surface.

This review was generated by OpenHands AI on behalf of neubig.

@openhands-release-bot
openhands-release-bot Bot force-pushed the release-please--branches--main--components--extensions branch from 17728ba to 1f45d14 Compare October 5, 2026 01:14
@neubig
neubig merged commit 3ed8861 into main Oct 5, 2026
15 checks passed
@neubig
neubig deleted the release-please--branches--main--components--extensions branch October 5, 2026 01:17
@openhands-release-bot

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants