Skip to content

Bump ardrive-core-js and cli version to 3.0.5 #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kunstmusik merged 1 commit into from
Oct 16, 2025
Merged

Bump ardrive-core-js and cli version to 3.0.5 #372

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
Binary file renamed ...re-js-npm-3.0.4-250f704d37-01868c5649.zip → ...re-js-npm-3.0.5-29d8269aeb-c0dbf53ddb.zip
View file
Open in desktop
Binary file not shown.
4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
{
"name": "ardrive-cli",
"version": "3.0.4",
"version": "3.0.5",
"description": "The ArDrive Command Line Interface (CLI is a Node.js application for terminal-based ArDrive workflows. It also offers utility operations for securely interacting with Arweave wallets and inspecting various Arweave blockchain conditions.",
"main": "./lib/index.js",
"bin": {
"ardrive": "./lib/index.js"
},
"types": "./lib/index.d.ts",
"dependencies": {
"ardrive-core-js": "3.0.4",
"ardrive-core-js": "3.0.5",
"arweave": "1.15.7",
Comment on lines +3 to 12
Copy link

@coderabbitai coderabbitai bot Oct 16, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Update the lockfile to pick up 3.0.5.

Bumping ardrive-core-js here is not enough—without the corresponding yarn.lock/package-lock.json update, installs will still resolve to 3.0.4, so the release won’t actually ship the new core. Please regenerate the lockfile (e.g., yarn install) and include it in the PR.

🤖 Prompt for AI Agents 
In package.json around lines 3 to 12, you bumped ardrive-core-js to 3.0.5 but
did not update the lockfile, so installs will still pull 3.0.4; regenerate and
commit the appropriate lockfile (run yarn install if using Yarn or npm install
if using npm) so yarn.lock or package-lock.json reflects 3.0.5, verify the
lockfile contains ardrive-core-js@3.0.5, and include that updated lockfile in
the PR before merging.

"axios": "^0.21.1",
"commander": "^8.2.0",
Expand Down
10 changes: 5 additions & 5 deletions yarn.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2245,7 +2245,7 @@ __metadata:
"@types/source-map-support": ^0
"@typescript-eslint/eslint-plugin": ^6.2.1
"@typescript-eslint/parser": ^6.2.1
ardrive-core-js: 3.0.4
ardrive-core-js: 3.0.5
arweave: 1.15.7
axios: ^0.21.1
chai: ^4.3.4
Expand All @@ -2272,9 +2272,9 @@ __metadata:
languageName: unknown
linkType: soft

"ardrive-core-js@npm:3.0.4":
version: 3.0.4
resolution: "ardrive-core-js@npm:3.0.4"
"ardrive-core-js@npm:3.0.5":
version: 3.0.5
resolution: "ardrive-core-js@npm:3.0.5"
dependencies:
"@ardrive/ardrive-promise-cache": ^1.1.4
"@ardrive/turbo-sdk": ^1.0.1
Expand All @@ -2294,7 +2294,7 @@ __metadata:
smartweave: ^0.4.49
utf8: ^3.0.0
uuid: ^9.0.1
checksum: 01868c56499c389e716c6ca369093f34dab432964be71af090ac1faf0b69d17ee2e75b7d394fd08656ab0868883bc7b1d356c184caa2876db0392cd90f83a801
checksum: c0dbf53ddb8e3d00f920ede965c03497becb87476a30a1ba3fede0a5f3d4e82b4db62b51ef27d868f72400d4f1bb9d86d2fa89198df6d8e06bee23ac00f31f1e
languageName: node
linkType: hard

Expand Down
Loading