chore(deps): update all patch updates - #737
renovate[bot] wants to merge 2 commits into
Conversation
![henry-nsheaps[bot]](https://avatars.githubusercontent.com/in/2371206?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
6478bc6 to
ba59b08
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
ba59b08 to
57e1e5e
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
57e1e5e to
08c61a5
Compare
Dismissed: new commits since last approval require re-review.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
08c61a5 to
91c08d6
Compare
Dismissed: new commits since last approval require re-review.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
91c08d6 to
13f861d
Compare
Dismissed: new commits since last approval require re-review.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
13f861d to
57eeadc
Compare
Dismissed: new commits since last approval require re-review.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
57eeadc to
0ffd602
Compare
Dismissed: new commits since last approval require re-review.
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Dismissed: new commits since last approval require re-review.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
👍 Re-triggered on the same head sha — nothing changed since my last approval, and re-verification reproduces. Still approving.
✅ Head sha unchanged at ae6fef9 — same commit my previous review approved
✅ claude-code@2.1.210 re-checked on npm (dist.shasum 8b0306a7…), op-exec v0.1.30 re-checked on GitHub (4 assets, published 2026-08-12) — same digests as last round
✅ nsheaps/agents main unchanged since last round — still pinned at 2.1.128 with allow_builds
✅ Existing unresolved threads on mise.toml:13, mise.toml:23, .github/settings.yml:231 remain current and correct — not re-raising them
⚠️ # match agents still tracked separately in #749 — deliberately not re-raised inline
🖱️ Click to expand for full details
ae6fef9 — same commit my previous review approved✅
claude-code@2.1.210 re-checked on npm (dist.shasum 8b0306a7…), op-exec v0.1.30 re-checked on GitHub (4 assets, published 2026-08-12) — same digests as last round✅
nsheaps/agents main unchanged since last round — still pinned at 2.1.128 with allow_builds✅ Existing unresolved threads on
mise.toml:13, mise.toml:23, .github/settings.yml:231 remain current and correct — not re-raising them# match agents still tracked separately in #749 — deliberately not re-raised inlineWhy this is short
This is the 12th review on this PR and my second at head ae6fef9. The previous approval, submitted ~30 minutes ago, already exhaustively covers:
- Both version bumps verified against published artifacts (
claude-code@2.1.210on npm,op-exec v0.1.30on GitHub) - The two
.githubYAML reformats confirmed to be semantic no-ops (yaml.safe_load(pre) == yaml.safe_load(post)) - Full plugin-breaking-change audit for
2.1.207(${user_config.*},pluginConfigs) and2.1.210(Write/Glob/NotebookEditwarnings) against every file inplugins/ - Cross-repo state (
nsheaps/agentsat2.1.128withallow_builds; agents#320 stalled atCONFLICTING) - Root-cause analysis of why this PR structurally cannot settle (zero-release-age preset colliding with the shared patch-update group)
What I re-verified in this round
The re-triggering workflow (run 31742854716) is a fresh repository_dispatch on the same head sha, so I re-derived the primary-source claims that could plausibly have changed in 30 minutes rather than trusting the prior review:
gh pr view 737 --json headRefOid→ae6fef990848ba6642c7b7e0b91c05022b4458b6(unchanged)gh api /repos/nsheaps/agents/contents/mise.toml→ still"npm:@anthropic-ai/claude-code" = { version = "2.1.128", allow_builds = [...] }(unchanged; agents did not roll forward)gh api /repos/nsheaps/op-exec/releases/tags/v0.1.30→ still present, 4 assets,state: uploaded,published_at: 2026-08-12T18:51:49Z(unchanged)gh api /registry.npmjs.org/@anthropic-ai/claude-code/2.1.210→ stilldist.shasum: 8b0306a7497680b242955a53db363e13b846406d, not deprecated (unchanged)- Issue #749 → still
open(unchanged)
Every relevant fact reproduces. Nothing in the PR, the target artifacts, the cross-repo pin, or the tracking issue moved in the interval between the two runs.
Existing threads
I left the three unresolved threads at head as-is because their conclusions still hold verbatim:
mise.toml:13—2.1.210audit, still cleanmise.toml:23—0.1.30binary-identity check, still holds.github/settings.yml:231— lint-autofix analysis, still current
Not re-posting them; the diff hasn't moved and neither has the analysis.
Scores
- Quality 98% — unchanged from last round; the sole blemish is the pre-existing inaccurate
# match agentsmarkers, tracked in #749. - Security 100% — both bumps still verified as patch-only from expected sources with matching hashes.
- Simplicity 100% — four changed lines, two of them pure formatting.
- Confidence 98% — up slightly from 97%. The verification surface got smaller because the deltas that mattered (op-exec binary identity, agents divergence) were already established from primary sources in earlier rounds and re-check the same. Residual 2% is that I don't execute
mise installend-to-end here.
Recommended follow-ups (non-blocking, carried forward from prior review):
- Fix the shared Renovate preset that makes this PR unable to settle.
nsheaps-zero-release-age.json5setsminimumReleaseAge: "0 days"fornsheaps/{/,}**whilegroup-patch-updates.json5puts every patch update into one group; net effect is that anyop-execrelease invalidates the in-flight review of theclaude-codebump. 12 review rounds on a 4-line diff is the symptom. - Add sync-managed paths (
.github/settings.yml,[sync]-managed workflows) to.prettierignoreto stop the quote-style tug-of-war between the org sync bot and the lint bot. - Resolve #749 so the
# match agentsmarkers stop being carried forward on every re-roll.
Footnotes
-
Workflow Run: https://github.com/nsheaps/.ai-agent-henry/actions/runs/31742854716 ↩
-
Previous approval at this same head: https://github.com/nsheaps/ai-mktpl/pull/737#pullrequestreview-4931577025 ↩
-
Sources re-verified against:
@anthropic-ai/claude-code@2.1.210on npm,nsheaps/op-exec v0.1.30release,nsheaps/agentsmise.toml at HEAD, tracking issue nsheaps/ai-mktpl#749. ↩
1 participant
This PR contains the following updates:
0.1.26→0.1.302.1.205→2.1.2102.1.231(+19)Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
nsheaps/op-exec (github:nsheaps/op-exec)
v0.1.30: Release 0.1.30Compare Source
Full Changelog: nsheaps/op-exec@v0.1.29...v0.1.30
v0.1.29: Release 0.1.29Compare Source
What's Changed
Full Changelog: nsheaps/op-exec@v0.1.28...v0.1.29
v0.1.28: Release 0.1.28Compare Source
Full Changelog: nsheaps/op-exec@v0.1.27...v0.1.28
v0.1.27: Release 0.1.27Compare Source
What's Changed
Full Changelog: nsheaps/op-exec@v0.1.26...v0.1.27
anthropics/claude-code (npm:@anthropic-ai/claude-code)
v2.1.210Compare Source
Write(path),NotebookEdit(path), andGlob(path)permission rules — useEdit(path)orRead(path)insteadisolation: 'worktree'subagents being able to run git-mutating commands against the main repo checkout instead of their own isolated worktreeultracodekeyword opt-in firing on non-human-originated input such as webhook payloads and relayed PR commentsclaude attachsometimes failing with "job not found" or "agent is still starting" errors during session transitions — attach now waits for the daemon to settle, and terminal resizes during a slow attach are applied once it completescdtook effect after its command was moved to the background; the tool result now states the working directory is unchanged/doctorskipping its auto-mode-default proposal on Bedrock, Vertex, and Foundry, where auto mode no longer needs an opt-in$1/$2positional placeholders in skills and commands being silently stripped; they are now preserved verbatimclaude agents --effort ultracodenot reaching dispatched sessions; the value was silently droppedgit worktree lockbehind; the periodic sweep now releases locks whose owning process is goneinitializecontrol request waiting until the next turn to start connectingCLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1.claude/*symlinks not being reconciled into the sandbox deny-write listv2.1.209Compare Source
claude agentsbackground sessions (reverts an overly broad guard)v2.1.208Compare Source
claude --ax-screen-reader, set CLAUDE_AX_SCREEN_READER=1, or add "axScreenReader": true to settings.vimInsertModeRemapssetting: map two-key insert-mode sequences likejjto Escape in vim modeCLAUDE_CODE_PROCESS_WRAPPER: agent view and the background service now honor a corporate launcher by running every Claude Code self-spawn through a required wrapper executableclaude agentsprocess was launched fromclaude -pCLAUDE_CODE_MAX_OUTPUT_TOKENSand similar env vars silently using the mantissa of scientific-notation values (1e6became1)apiKeyHelperscript failures being hidden behind a generic 401 after ~10 silent retries; the script's own error is now shown within 3 attempts/upgradeshowing a login flow instead of the upgrade URL when the browser fails to opencontrol_requestcarried a non-stringset_modelpayload; the CLI now answers with an error responsetoolslist resolves to nothing — it now returns a clear error naming the unrecognized entries/usageshowing stale cached bars over fresher data, and/mcpnot reclassifying placeholder servers after config edits~/.claude/workflows/instead of theCLAUDE_CONFIG_DIRlocation for user-scope saves/release-notesadding the viewed notes to the model's context — "Show all" previously injected the entire changelog into every subsequent request/tasksuntil cleanup instead of vanishing the moment they finishrm -rf ~) in commands containing$(…)/backticks/<(…)now prompt in--dangerously-skip-permissionsand auto mode, matching the plain form/install-github-appand the/mcpsettings menu no longer open in background sessions/mcpinstead of a config error/usagenow shows your last-known usage bars with an "as of" note when the usage endpoint is rate-limited, instead of an error screenv2.1.207Compare Source
CLAUDE_CODE_ENABLE_AUTO_MODEopt-in on Bedrock, Vertex AI, and Foundry; disable viadisableAutoModein settingsclaude -p, the SDK) being permanently recorded as consented without ever showing the security consent dialog~/.local/bin/claudeon every release;/doctornow reports an externally managed launchercdprompting for permission when the only output redirect was to/dev/nullextensions.worktreeConfigbeing left in the repo's.git/config(breaking go-git tools liketea) after the lastworktree.sparsePathsworktree was removed.ignore, and.worktreeincludebreaking file reads, file suggestions, and worktree creation[Pasted text #N]placeholder instead of adding a second onewaiting 3m) instead of the same timestamp twiceautoModefrom.claude/settings.local.json(repo-resident); use~/.claude/settings.jsoninsteadcredential_process): the 60-second stall guard now fires instead of waiting forever.${user_config.*}in shell-form commands is now rejected (shell-injection fix). Hooks: use exec form (argsarray) or$CLAUDE_PLUGIN_OPTION_<KEY>; monitors and headersHelper: read the value inside the script (config file or the server'senvblock).pluginConfigs) are no longer read from project-level.claude/settings.json; only user,--settings, and managed settings are honored/usage-creditsamount inputs silently stripping malformed values (e.g. a pasted timestamp) to digits; malformed amounts are now rejected with an error, and amounts over $1,000 require a typed confirmationv2.1.206Compare Source
/cd, matching/add-dirbehavior/doctorcheck that proposes trimming checked-inCLAUDE.mdfiles by cutting content Claude could derive from the codebase/commit-push-prnow auto-allowsgit pushto the repo's configured push remote (remote.pushDefault, or the sole remote when only one is configured) in addition toorigin/loginnow supports Anthropic-operated public gateway endpointsEnterWorktreenow asks for confirmation before entering a git worktree outside the project's.claude/worktrees/directory/loginclaude --resumeand--continuenot responding to keyboard input on startup--mcp-configor.mcp.jsonignoring a per-serverrequest_timeout_ms, which caused long-running MCP tool calls to time out at the 60s default in fresh sessionsCLAUDE_CODE_EXTRA_BODYbeing silently ignored byclaude agents/--bgbackground workers; the shell-exported override now follows the dispatching session--permission-prompt-toolpointing at an MCP server crashing with "MCP tool not found" on cold start before the server finishes connecting/modelpicker rows printing a price for a different model than the row named, and stopped quoting first-party list prices on providers that don't bill them/modelpicker when an entitlement or allowlist restriction drops the row they were positioned againstclaude --resumeon Windowsclaude rmleaving the removed job in the daemon roster, causing the row to reappear inclaude agents/remote-controlshowing "Unknown command" when logged out — it now explains how to sign in/statuslisting the same broken-install warning twice/doctor's update check to compare Homebrew installs against their cask's channel instead of the settings channelawsCredentialExporthelper on networks with restricted egress/code-reviewfindings quality on claude-opus-4-8 across all effort levelsConfiguration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.