Skip to content

Conversation

@kunstmusik
Copy link
Contributor

@kunstmusik kunstmusik commented Oct 16, 2025

Summary by CodeRabbit

  • Chores
    • Released version 3.0.5 with updated dependencies

@coderabbitai
Copy link

coderabbitai bot commented Oct 16, 2025

Walkthrough

The PR bumps the package version from 3.0.4 to 3.0.5 and updates the ardrive-core-js dependency to the matching 3.0.5 version in package.json.

Changes

Cohort / File(s) Summary
Version and dependency bumps
package.json
Bumped package version from 3.0.4 to 3.0.5; updated ardrive-core-js dependency from 3.0.4 to 3.0.5

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • ardriveapp/ardrive-cli#370: Similar version bump PR updating package.json with ardrive-core-js dependency version increments (3.0.3→3.0.4 vs. 3.0.4→3.0.5 here).

Suggested reviewers

  • fedellen

Poem

🐰 From 3.0.4, we hop to new ground,
Version 3.0.5 spins 'round and 'round,
Dependencies sync in perfect stride,
Another small bump, with nothing to hide! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title clearly and accurately states that both the ardrive-core-js dependency and the CLI version are being bumped to 3.0.5, directly reflecting the changes made in package.json. It succinctly summarizes the main change without unnecessary detail.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-core-js-and-release

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cdec094 and ad79f02.

⛔ Files ignored due to path filters (2)
  • .yarn/cache/ardrive-core-js-npm-3.0.5-29d8269aeb-c0dbf53ddb.zip is excluded by !**/.yarn/**, !**/*.zip
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • package.json (1 hunks)

Comment on lines +3 to 12
"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",
Copy link

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.

@kunstmusik kunstmusik merged commit 7919d1c into master Oct 16, 2025
2 of 3 checks passed
@kunstmusik kunstmusik deleted the update-core-js-and-release branch October 16, 2025 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants