chore(release): v0.18.2 - #276
Merged
Merged
Conversation
Three commits have been sitting unreleased on main, two of them the same trap seen from both ends: an install that succeeds into the wrong home. #272 install.sh refuses `sudo curl … | sh` up front, before the download, instead of writing the payload into /root/.moshcode where the user who typed the command cannot read it. #274 `dns` escalates itself per command rather than telling the operator to `sudo moshcode …` — advice that was right for dns and dangerous for `update`, which self-updates through the installer and so reinstalls into root's home. #273 the /prd healthy-cwd test no longer launches a real engine; the suite went from 479s to ~70s. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreatCrush Security Scan87 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 37
…and 37 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three commits have been sitting unreleased on
mainsincev0.18.1.What's in it
#272 —
install.shrefuses a root install instead of doing the wrong one.Every path in
install.shderives from$HOME. Undersudothat is/root, mode0700, sosudo curl … | shput the payload in/root/.moshcodeand both wrappers in/root/.local/bin— where the user who typed the command cannot read them. Nothing failed at install time. It reported success and surfaced much later as:Now refused up front, before the download. A bare root shell (containers, CI images) has no
SUDO_USERand stays legitimate;MOSHCODE_ALLOW_ROOToverrides.#274 —
dnsescalates itself, andupdaterefuses to run escalated.The same trap from the other end.
dns enablegenuinely needs root, and it told the operator to runsudo moshcode dns enable. Correct fordns, dangerous everywhere else:moshcode updateself-updates by re-running the installer, whose paths come from$HOME. The habitdnstaught turnedupdateinto a silent reinstall into root's home.dnsnow re-runs its own argv undersudo/doaswith stdio inherited, so only the privileged command is raised. Where escalation isn't possible it falls back to exactly the advice printed before, so nothing that worked stops working.#273 — the
/prdhealthy-cwd test no longer launches a real engine.It was spawning Claude for real and blocking until it finished authoring a PRD. Suite: 479s → ~70s.
Verified
1319 tests, 1316 pass, 0 fail, 3 skipped.moshcode --versionreports0.18.2.Version lives only in
package.jsonand is read at runtime, so nothing else needed touching.Not an npm package — this is a tag and GitHub release; distribution is via
install.sh.🤖 Generated with Claude Code