chore(main): release agi-js 0.4.3

[JacobFV]

🤖 I have created a release beep boop

0.4.3 (2026-02-17)

Features

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

Bug Fixes

• docs: remove invalid const from await using declaration (4989ee8)

---

This PR was generated with Release Please. See documentation.

Greptile Summary

Automated Release Please PR to release agi-js v0.4.3, adding a changelog entry for the multimodal driver support feature (#11) and a docs fix. However, this PR downgrades package.json from 0.5.1 to 0.4.3 because the .release-please-manifest.json was never updated when the version was manually bumped to 0.5.0/0.5.1 in commit b5a290f.

• Version downgrade: package.json and package-lock.json version goes from 0.5.1 → 0.4.3. This is because Release Please tracks versions via its manifest (which was at 0.4.2), and the manual 0.5.x bumps were done outside of its workflow.
• Changelog gap: The CHANGELOG.md has no entries for versions 0.5.0 or 0.5.1, which existed on main. The new 0.4.3 entry correctly references the feature and fix commits since 0.4.2.
• Risk assessment: If 0.5.1 was never published to npm (no 0.5.x git tags exist and the package is not found on npm), this realignment is likely safe. If it was published, this would be a semver violation.

Confidence Score: 2/5

• This PR downgrades the package version from 0.5.1 to 0.4.3 — needs confirmation this is intentional before merging.
• The version downgrade from 0.5.1 to 0.4.3 is the primary concern. While the release-please automation is working correctly based on its manifest, the manifest was out of sync with the actual package version. This could cause issues if 0.5.1 was consumed by any downstream users. The changelog and manifest changes themselves are correct.
• Pay close attention to package.json — the version is being downgraded from 0.5.1 to 0.4.3. Verify that 0.5.1 was never published before merging.

Important Files Changed

Filename	Overview
package.json	Version downgraded from 0.5.1 to 0.4.3 due to release-please manifest being out of sync with manually bumped package version.
package-lock.json	Version downgraded from 0.5.1 to 0.4.3 in lockfile, consistent with package.json change.
.release-please-manifest.json	Manifest correctly bumped from 0.4.2 to 0.4.3 per release-please tracking.
CHANGELOG.md	New 0.4.3 changelog entry added correctly, but the changelog has no entries for the manual 0.5.0/0.5.1 versions that existed on main.

Flowchart

flowchart TD
    A["v0.4.2 release<br/>(release-please #10)"] --> B["Manual bump to v0.5.0<br/>(multimodal driver #11)"]
    B --> C["Manual bump to v0.5.1<br/>(driver deps fix #13)"]
    C --> D["This PR: release-please<br/>sets version to v0.4.3"]

    E[".release-please-manifest.json"] --> |"Tracked: 0.4.2"| F["Release Please computes<br/>next version: 0.4.3"]
    F --> D

    style D fill:#f96,stroke:#333,stroke-width:2px
    style E fill:#69f,stroke:#333,stroke-width:1px
    style F fill:#69f,stroke:#333,stroke-width:1px

Loading

_{Last reviewed commit: 9be0871}

[greptile-apps]

_{4 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Version downgrade from 0.5.1 to 0.4.3

This PR changes the version from 0.5.1 to 0.4.3, which is a version downgrade. Commit b5a290f ("chore(release): bump driver to v0.4.1, release v0.5.1") manually bumped package.json to 0.5.0 and then 0.5.1 without updating .release-please-manifest.json. Release Please still believes the last release was 0.4.2, so it generated this 0.4.3 bump — effectively reverting the manual version changes.

If 0.5.1 was never published to npm (it doesn't appear to be, and there are no 0.5.x git tags), this may be acceptable to realign with Release Please's tracking. However, if any consumers are already depending on 0.5.x, this downgrade would break semver expectations.

Please confirm this is intentional 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**

This PR changes the version from `0.5.1` to `0.4.3`, which is a version downgrade. Commit `b5a290f` ("chore(release): bump driver to v0.4.1, release v0.5.1") manually bumped `package.json` to `0.5.0` and then `0.5.1` without updating `.release-please-manifest.json`. Release Please still believes the last release was `0.4.2`, so it generated this `0.4.3` bump — effectively reverting the manual version changes.

If `0.5.1` was never published to npm (it doesn't appear to be, and there are no `0.5.x` git tags), this may be acceptable to realign with Release Please's tracking. However, if any consumers are already depending on `0.5.x`, this downgrade would break semver expectations.

Please confirm this is intentional before merging.

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