chore(main): release agi-js 0.4.3

[JacobFV]

🤖 I have created a release beep boop

0.4.3 (2026-02-11)

Features

• add comprehensive multimodal driver support (#11) (0b11341)

---

This PR was generated with Release Please. See documentation.

Greptile Overview

Greptile Summary

This automated release PR attempts to publish version 0.4.3, but the base branch is already at version 0.5.1 (from PR #13). This creates a critical version downgrade that violates semantic versioning and will cause conflicts in the npm registry.

Key Issues:

• Version would regress from 0.5.1 → 0.4.3 (a downgrade)
• Release Please's .release-please-manifest.json is out of sync with actual package.json version
• Manual version bumps in PR chore(release): bump driver to v0.4.1, release v0.5.1 #13 created a divergence from Release Please's tracking

Root Cause: The manifest was at 0.4.2 when PR #13 manually bumped the version to 0.5.1, bypassing Release Please. Now Release Please is calculating the next version as 0.4.2 → 0.4.3, unaware of the 0.5.1 bump.

Resolution Required: Update .release-please-manifest.json to "0.5.1" to sync with the current state, then let Release Please recalculate the next version (likely 0.6.0 for the new feature from PR #11). Alternatively, establish a policy to either use Release Please exclusively or manual versioning exclusively to prevent future conflicts.

Confidence Score: 0/5

• This PR is unsafe to merge and would break version management
• Score of 0 reflects a critical versioning error that would downgrade the package from 0.5.1 to 0.4.3, violating semantic versioning principles and potentially breaking dependent projects. This requires immediate correction before merging.
• Critical attention needed for package.json, package-lock.json, and .release-please-manifest.json due to version downgrade issue

Important Files Changed

Filename	Overview
package.json	Version downgraded from 0.5.1 to 0.4.3 - critical versioning conflict that would break semantic versioning
package-lock.json	Lockfile version downgraded from 0.5.1 to 0.4.3 to match package.json - same critical issue
.release-please-manifest.json	Updated to 0.4.3 but conflicts with actual package version 0.5.1 on main branch
CHANGELOG.md	Changelog entry correctly documents the multimodal feature from PR #11, but version number is incorrect

[JacobFV]

Closing - version already set to 0.5.1 manually

[greptile-apps]

_{4 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Version downgrade from 0.5.1 to 0.4.3 breaks semantic versioning and will cause package registry conflicts. The base branch (main) is at version 0.5.1 after commit b5a290f, but this PR attempts to publish 0.4.3. This indicates a conflict between Release Please's version tracking and manual version bumps. The .release-please-manifest.json needs to be synchronized with the actual package version before merging.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 3:3

Comment:
Version downgrade from 0.5.1 to 0.4.3 breaks semantic versioning and will cause package registry conflicts. The base branch (`main`) is at version 0.5.1 after commit b5a290f, but this PR attempts to publish 0.4.3. This indicates a conflict between Release Please's version tracking and manual version bumps. The `.release-please-manifest.json` needs to be synchronized with the actual package version before merging.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Manifest version 0.4.3 conflicts with current package.json version 0.5.1 on main. Update this to "0.5.1" to sync with the actual published version, then let Release Please calculate the next version based on the new feature in PR #11.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .release-please-manifest.json
Line: 2:2

Comment:
Manifest version 0.4.3 conflicts with current `package.json` version 0.5.1 on `main`. Update this to "0.5.1" to sync with the actual published version, then let Release Please calculate the next version based on the new feature in PR #11.

How can I resolve this? If you propose a fix, please make it concise.