Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "0.4.2"
".": "0.4.3"
}
12 changes: 12 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
# Changelog

## [0.4.3](https://github.com/agi-inc/agi-node/compare/agi-js-v0.4.2...agi-js-v0.4.3) (2026-02-17)


### Features

* add comprehensive multimodal driver support ([#11](https://github.com/agi-inc/agi-node/issues/11)) ([0b11341](https://github.com/agi-inc/agi-node/commit/0b1134116bee8ec1770be78beb126d7f09cd286d))


### Bug Fixes

* **docs:** remove invalid `const` from `await using` declaration ([4989ee8](https://github.com/agi-inc/agi-node/commit/4989ee82e85bbd3e67147c47a99843be3e75b905))

## [0.4.2](https://github.com/agi-inc/agi-node/compare/agi-js-v0.4.1...agi-js-v0.4.2) (2026-02-09)


Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@agi_inc/agi-js",
"version": "0.5.1",
"version": "0.4.3",
Copy link

Choose a reason for hiding this comment

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

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.

"description": "Official TypeScript/JavaScript SDK for AGI.tech API",
"main": "./dist/index.js",
"module": "./dist/index.mjs",
Expand Down
Loading