chore(main): release agi-js 0.4.3

[JacobFV]

🤖 I have created a release beep boop

0.4.3 (2026-02-10)

Features

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

---

This PR was generated with Release Please. See documentation.

Greptile Overview

Greptile Summary

This PR is an automated Release Please release bump for @agi_inc/agi-js, updating the release manifest, changelog, and npm metadata/lockfile to reflect version 0.4.3 and the features from #11.

The main issue is that package.json’s version is being decreased from 0.5.0 (current on base) to 0.4.3, which will break npm publishing and makes the repo’s release metadata inconsistent.

Confidence Score: 2/5

• Not safe to merge until version metadata is corrected.
• Although this is mostly a standard Release Please bump, the PR regresses package.json version from 0.5.0 to 0.4.3, which will cause publish failures and inconsistent release state.
• package.json (version field)

Important Files Changed

Filename	Overview
.release-please-manifest.json	Bumps release-please manifest from 0.4.2 to 0.4.3.
CHANGELOG.md	Adds 0.4.3 changelog entry referencing multimodal driver support.
package-lock.json	Updates lockfile package version fields to 0.4.3.
package.json	Sets package version to 0.4.3, which regresses from 0.5.0 in base commit and will break publishing/version consistency.

Sequence Diagram

sequenceDiagram
  participant Dev as Maintainer
  participant RP as Release Please
  participant Repo as Repository Files

  Dev->>RP: Trigger release workflow
  RP->>Repo: Update .release-please-manifest.json (0.4.3)
  RP->>Repo: Append CHANGELOG.md entry (0.4.3)
  RP->>Repo: Set package.json version
  RP->>Repo: Update package-lock.json version
  Dev->>Repo: Merge release PR

Loading

[JacobFV]

Closing — version 0.5.0 was already set in #11. Will create release manually.

[greptile-apps]

_{4 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Version regression in release

This release commit sets "version": "0.4.3" even though the base commit had "version": "0.5.0" (see diff). Publishing a lower version than the current package version will fail on npm and makes the repo state inconsistent with the release manifest/changelog. The version here should be bumped forward from the current value, not decreased.

Prompt To Fix With AI

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

Comment:
**Version regression in release**

This release commit sets `"version": "0.4.3"` even though the base commit had `"version": "0.5.0"` (see diff). Publishing a lower version than the current package version will fail on npm and makes the repo state inconsistent with the release manifest/changelog. The version here should be bumped forward from the current value, not decreased.

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