Skip to content

Remove obsolete dojoup shell installer#3401

Open
kronosapiens wants to merge 2 commits intomainfrom
kronosapiens/rm-legacy-dojoup
Open

Remove obsolete dojoup shell installer#3401
kronosapiens wants to merge 2 commits intomainfrom
kronosapiens/rm-legacy-dojoup

Conversation

@kronosapiens
Copy link
Contributor

@kronosapiens kronosapiens commented Mar 5, 2026

Description

Removes the legacy dojoup/dojoup shell installer and associated infrastructure that have been replaced by asdf-based plugins (sozo, katana, torii, saya).

Deleted

  • dojoup/dojoup — legacy shell installer (903 lines)
  • dojoup/dojoup-install — bootstrap for legacy script
  • dojoup/post_install_check — test suite for legacy commands
  • dojoup/Dockerfile — Docker image for testing legacy flow

Updated

  • dojoup/README.md — rewritten to document current asdf-based installation
  • bin/sozo/README.md — fixed title (was incorrectly labeled as "dojoup")
  • .devcontainer/devcontainer.json — removed legacy ~/.dojo/bin from PATH
  • dojoup/install.ps1 — updated to fetch latest releases from GitHub API instead of versions.json

Related issue

Fixes #3400

Tests

  • No, because they aren't needed

Added to documentation?

  • No documentation needed

Checklist

  • I've formatted my code
  • I've linted my code
  • I've commented my code

Summary by CodeRabbit

  • Documentation

    • Updated installation guide: toolchain now installed via curl/asdf with plugins for sozo, katana, torii, saya; README headings and usage flow refreshed.
  • Chores

    • Removed legacy installer, CLI toolchain manager, installer scripts, post-install test suite, and related Docker build configuration.

The legacy dojoup/dojoup script and its associated infrastructure have been
replaced by asdf-based plugins (sozo, katana, torii, saya). This removes:
- dojoup/dojoup (legacy shell installer)
- dojoup/dojoup-install (bootstrap for legacy script)
- dojoup/post_install_check (legacy test suite)
- dojoup/Dockerfile (legacy CI)

Also updated:
- dojoup/README.md to document the new asdf-based installation
- bin/sozo/README.md to fix title
- .devcontainer/devcontainer.json to remove legacy path
- dojoup/install.ps1 to use GitHub API instead of versions.json

Fixes #3400
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 5, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 678f0766-4cd5-4ce7-b929-66f565e934a8

📥 Commits

Reviewing files that changed from the base of the PR and between ef473bd and 1e316d3.

📒 Files selected for processing (1)
  • dojoup/install.ps1
💤 Files with no reviewable changes (1)
  • dojoup/install.ps1

Ohayo, sensei!

Walkthrough

Removed the legacy dojoup installer ecosystem and related artifacts: the shell installer, its installer bootstrap, PowerShell installer, post-install test suite, and Dockerfile. Documentation and a devcontainer PATH entry were updated to reflect the removal.

Changes

Cohort / File(s) Summary
Legacy installer scripts (removed)
dojoup/dojoup, dojoup/dojoup-install, dojoup/install.ps1, dojoup/post_install_check
Deleted the legacy shell installer, its bootstrap installer, the PowerShell installer, and the post-install test suite—removes installer logic, version resolution, download/extract flows, PATH augmentation, and end-to-end tests.
Packaging config removed
dojoup/Dockerfile
Deleted Dockerfile that built an image for dojoup installation and post-install checks.
Documentation edits
dojoup/README.md, bin/sozo/README.md
Updated README content: replaced legacy usage/install instructions and adjusted headings (sozo README heading changed).
Devcontainer environment
.devcontainer/devcontainer.json
Adjusted remote PATH to remove /home/vscode/.dojo/bin, setting PATH to ${containerEnv:PATH}:/workspace/dojo/target/release.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: removal of the legacy dojoup shell installer, which aligns with the primary objective of this PR.
Linked Issues check ✅ Passed The PR fully addresses the requirements of issue #3400: removes the legacy dojoup/dojoup script, associated infrastructure (Dockerfile, dojoup-install, install.ps1, post_install_check), updates documentation, and cleans up related configuration.
Out of Scope Changes check ✅ Passed All changes are directly scoped to removing the obsolete dojoup installer infrastructure and updating related configuration/documentation as part of the migration to asdf-based installation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch kronosapiens/rm-legacy-dojoup

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Contributor

@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

🧹 Nitpick comments (1)
dojoup/install.ps1 (1)

56-62: Ohayo sensei — prefer pipeline-friendly output cmdlets over Write-Host.

Using Write-Information/Write-Verbose here keeps output redirectable and easier to automate.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@dojoup/install.ps1` around lines 56 - 62, Replace the pipeline-terminating
Write-Host calls with pipeline-friendly output cmdlets: use Write-Information
for the main installation status messages (e.g., the "Installed $($tool.Name)
v$version" and "Dojo toolchain installation complete!" messages) and/or
Write-Verbose for optional progress lines; keep Add-ToPath and $installDir
unchanged. Update the calls to include meaningful Tags or MessageData if needed
and ensure callers can see messages by documenting or setting appropriate
-InformationAction/-Verbose switches when running the script.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@dojoup/install.ps1`:
- Line 2: Update the stale usage comment in install.ps1: remove the “[version]”
argument from the shebang/usage line and replace it with the current invocation
signature (e.g. "Usage: powershell -ExecutionPolicy Bypass -File install.ps1")
so the top-of-file comment accurately reflects that install.ps1 no longer
accepts a version parameter; edit the comment line shown in the diff
accordingly.

---

Nitpick comments:
In `@dojoup/install.ps1`:
- Around line 56-62: Replace the pipeline-terminating Write-Host calls with
pipeline-friendly output cmdlets: use Write-Information for the main
installation status messages (e.g., the "Installed $($tool.Name) v$version" and
"Dojo toolchain installation complete!" messages) and/or Write-Verbose for
optional progress lines; keep Add-ToPath and $installDir unchanged. Update the
calls to include meaningful Tags or MessageData if needed and ensure callers can
see messages by documenting or setting appropriate -InformationAction/-Verbose
switches when running the script.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 24987dc1-599d-4531-a7ae-3f887e1a9ec2

📥 Commits

Reviewing files that changed from the base of the PR and between 4a374ac and ef473bd.

📒 Files selected for processing (8)
  • .devcontainer/devcontainer.json
  • bin/sozo/README.md
  • dojoup/Dockerfile
  • dojoup/README.md
  • dojoup/dojoup
  • dojoup/dojoup-install
  • dojoup/install.ps1
  • dojoup/post_install_check
💤 Files with no reviewable changes (4)
  • dojoup/post_install_check
  • dojoup/dojoup-install
  • dojoup/Dockerfile
  • dojoup/dojoup

@@ -1,92 +1,63 @@
# Function to download and extract a zip file
# Dojo toolchain installer for Windows
# Usage: powershell -ExecutionPolicy Bypass -File install.ps1 [version]
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Ohayo sensei — usage comment is stale.

Line 2 still advertises [version], but the script does not accept a version argument anymore.

Proposed doc fix
-# Usage: powershell -ExecutionPolicy Bypass -File install.ps1 [version]
+# Usage: powershell -ExecutionPolicy Bypass -File install.ps1
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# Usage: powershell -ExecutionPolicy Bypass -File install.ps1 [version]
# Usage: powershell -ExecutionPolicy Bypass -File install.ps1
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@dojoup/install.ps1` at line 2, Update the stale usage comment in install.ps1:
remove the “[version]” argument from the shebang/usage line and replace it with
the current invocation signature (e.g. "Usage: powershell -ExecutionPolicy
Bypass -File install.ps1") so the top-of-file comment accurately reflects that
install.ps1 no longer accepts a version parameter; edit the comment line shown
in the diff accordingly.

The legacy PowerShell installer had version compatibility issues and no
test coverage. Windows users can download binaries directly from GitHub
releases.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

Remove obsolete dojoup shell installer

1 participant