Repository navigation
chore(mise): Update mise tools - #198
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: Renovate による mise tool の version 更新(config.toml と生成物の mise.lock)を確認しました。
config.tomlの pin 更新: claude-code・codex・pnpm・uv・yq・wrangler・vercel・pullfrog など約 30 tool が patch/minor の更新です。version は exact pin のままで、設定構造は変わっていません。gh-actions-lockの表記:0.4.0からv0.4.1へ変わりました。lock 側はversion = "0.4.1"で、既存のgh-aw(v1.0.1と lock の1.0.1)と同じ対応です。mise.lockの再生成: checksum・url・url_api・provenance が新 version に揃っています。
挙動を変える差分はなく、ユーザー名入りパスや machine 固有値の混入もありません。可搬性・ガバナンスの観点は、設定構造・文書・コメントの変更がないため対象外です。そのため specialist subagent は起動していません。
claude-sonnet-5-5 | 𝕏
43824a0 to
f012ac1
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(43824a0)以降の差分を確認しました。
fdの bump:aqua:sharkdp/fdが10.5.1から10.5.2へ変わりました。config.tomlの exact pin とmise.lockのversionが一致しています。mise.lockの再生成: linux(gnu・musl)、macOS(arm64・x86_64)、windows の全 platform で checksum・url・url_api が v10.5.2 に揃っています。
差分は version の機械的な更新だけで、構造・文書・コメントの変更や machine 固有値の混入はありません。そのため specialist subagent は起動していません。既存の Pullfrog thread はなく、P0〜P2 の未解決指摘もないため承認します。
claude-sonnet-5-5 | 𝕏
f012ac1 to
5bebc7f
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(f012ac1)以降の差分を確認しました。
fzfの bump:aqua:junegunn/fzfが0.74.5から0.75.0へ変わりました。config.tomlの exact pin とmise.lockのversionが一致し、mise.lockに0.74.5の残りはありません。mise.lockの再生成: linux(arm64・x64、musl・baseline 含む)、macOS、windows の全 platform で checksum・url・url_api が v0.75.0 に揃っています。
差分は version の機械的な更新だけで、構造・文書・コメントの変更や machine 固有値の混入はありません。そのため specialist subagent は起動していません。既存の Pullfrog thread はなく、P0〜P2 の未解決指摘もないため承認します。
claude-sonnet-5-5 | 𝕏
5bebc7f to
872b7d3
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes
前回レビュー(5bebc7f)以降の差分を確認しました。
pullfrogの更新:npm:pullfrogを 0.1.121 → 0.1.122 に上げ、config.tomlとmise.lockの両方が 0.1.122 の単一エントリで揃っています。
差分は version pin と生成 lock の更新のみで、挙動・可搬性・文書への影響はありません。未解決の指摘もないため承認します。specialist 観点別の dispatch は、差分に該当する観点(挙動を持つ変更・可搬性・文書)がないため行っていません。
claude-sonnet-5-5 | 𝕏
872b7d3 to
3580620
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes
前回レビュー(872b7d3)以降の差分を確認しました。
tmux-buildsの更新:aqua:tmux/tmux-buildsを 3.6a → 3.8 に上げました。config.tomlの exact pin とmise.lockのversionが 3.8 で一致し、mise.lockに 3.6a のエントリは残っていません。mise.lockの再生成: linux(arm64・x64、musl・baseline 含む)と macOS(arm64・x64、baseline 含む)の全 platform で checksum・url・url_api が v3.8 に揃っています。
差分は version pin と生成 lock の更新のみで、挙動・可搬性・文書への影響はありません。未解決の指摘もないため承認します。specialist 観点別の dispatch は、差分に該当する観点がないため行っていません。
claude-sonnet-5-5 | 𝕏
3580620 to
1b63daf
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(3580620)以降の差分を確認しました。
pullfrogの更新:npm:pullfrogを 0.1.122 → 0.1.123 に上げました。mise.lockも 0.1.123 の単一エントリで、config と一致しています。- main の取り込み: 差分に含まれるそれ以外の変更は main 側の変更(#201 など)で、この PR 固有ではありません。
確認した観点は通常レビューです。差分は tool version の bump と lock の更新だけで、可搬性・文書の観点を適用する変更はなく、specialist は起動していません。
claude-sonnet-5-5 | 𝕏
1b63daf to
f99e158
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(1b63daf)以降の差分を確認しました。
portlessの更新:npm:portlessを 0.16.0 → 0.17.0 に上げました。config.tomlの exact pin とmise.lockのversionが 0.17.0 で一致し、lock は単一エントリで旧 version の残りはありません。
確認した観点は通常レビューです。差分は version pin と生成 lock の更新だけで、可搬性・文書の観点を適用する変更はなく、specialist は起動していません。未解決の指摘もないため承認します。
claude-sonnet-5-5 | 𝕏
f99e158 to
1e4182c
Compare
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(f99e158)以降の差分を確認しました。
yqの更新:aqua:mikefarah/yqを 4.54.2 → 4.54.3 に上げました。config.tomlの exact pin とmise.lockのversionが 4.54.3 で一致し、全 platform の url が v4.54.3 に揃って旧 version の残りはありません。
確認した観点は通常レビューです。差分は version pin と生成 lock の更新だけで、可搬性・文書の観点を適用する変更はなく、specialist は起動していません。未解決の指摘もないため承認します。
claude-sonnet-5-5 | 𝕏
actions-lock CI は pin に v 接頭辞なしの exact semver を要求し、URL を
v{version} で組み立てる。Renovate が v0.4.1 に変えたため
`gh-actions-lock must be an exact semver pin` で落ちていた。
mise.lock 側は 0.4.1 / v0.4.1 のまま変わらない。
|
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. |
There was a problem hiding this comment.
✅ 新たな指摘はありません。
Reviewed changes: 前回レビュー(1e4182c)以降の差分を確認しました。
gh-actions-lockの pin 表記:config.tomlの version をv0.4.1から0.4.1に戻しました。mise.lockのversion = "0.4.1"と一致し、config.tomlは単一エントリです。
確認した観点は通常レビューです。差分は pin の表記修正だけで、可搬性・文書の観点を適用する変更はなく、specialist は起動していません。既存の Pullfrog thread はなく、P0〜P2 の未解決指摘もないため承認します。
claude-sonnet-5-5 | 𝕏
追記(状態変化):
|
main で aqua:supabase/cli が 3.0.0 に上がっており(#199)、この PR の 2.122.0 → 2.122.1 と競合していた。main 側の 3.0.0 を採用し(2.122.1 は ダウングレードになるため)、PR 側の他の bump(ghq 1.12.0・tmux 3.8 等)は そのまま残す。mise.lock も同じ方針で main の 3.0.0 entry を採り、 `mise lock` の再生成結果と一致することを確認した。
競合の解消(
|

Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
2.1.316→2.1.3192.1.325(+3)0.13.6→0.13.70.13.80.74.5→0.75.04.54.1→4.54.30.166.0→0.167.00.169.0(+3)12.17.0→12.18.012.21.0(+2)10.5.0→10.5.22.122.0→2.122.10.5.1→0.5.50.5.10(+4)3.6a→3.81.11.2→1.12.00.4.0→v0.4.11.4.0→1.5.01.5.2(+1)0.66.0→0.67.00.68.01.2.4→1.3.11.64.1→1.65.01.65.10.41.0→0.41.20.43.0(+1)1.0.0-beta.26→1.0.0-beta.281.0.0-beta.32(+3)0.22.0→0.23.00.23.11.26.24→1.29.00.15.12→0.17.00.1.110→0.1.1230.1.130(+6)1.7.4→1.7.61.9.0(+2)65.9.0→65.12.165.16.0(+2)4.156.0→4.158.04.163.0(+5)Release Notes
anthropics/claude-code (aqua:anthropics/claude-code)
v2.1.319Compare Source
CLAUDE_CODE_AUTO_MODE_SERVER=0to keep using it (Bedrock, Vertex and Foundry are unchanged)CLAUDE_CODE_AUTO_MODE_SERVER=1turns on the server-side check even withCLAUDE_CODE_DISABLE_EXPERIMENTAL_BETASset; if managed settings set the latter, they must set the1tooCLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUNDenvironment variable to make Claude Code wait for an MCP task inside its tool call instead of moving it to the background right awaypermissions.denyInsteadOfPromptingsetting: a tool call that would wait on a permission prompt is denied and the turn continues, in terminal sessions, subagents and teammates/claude-api latency-optimizeto find where your Claude API code makes people wait and try faster settings against your evalCLAUDE_CODE_DISABLE_FEATURE_FLAGSenvironment variable, which stops feature-flag fetching without turning off telemetry; every flag then uses its built-in default/usagefor developers behind a Claude apps gateway who have no spend limit, when the gateway runs this version or lateradmin.pooled_conflict_ruleandadmin.pooled_priority_orderto the Claude apps gateway, to set which pooled group budget pays first for a developer in several groupslogin_noticesetting to the Claude apps gateway that shows an operator-defined message on the gateway's browser verification page and on Claude Code's sign-in screenCLAUDE_GATEWAY_LOG_FORMAT=jsonto the Claude apps gateway: operational log lines become JSON withseverity,timeandmessage, for log collectors that read the level from a fieldavailableModelsalso allows a custom model id that one policy lists by namedesktopHomethat rely oncoworkTabEnabled: falseorchatSessionRetentionDays, ahead of Claude Desktop's November 10 changeant auth login, which bills usage to your Claude Console organizationant auth login/tasksthat lists finished subagents, so you can reopen one and message it even after it leaves the list or you restart/loopconfirmations in cloud sessions that a timer stops with its container, with an offer of a loop that survives--resumeHEAD/diffshowing "Diff unavailable" when a git repository has a file or folder namedHEADat its top level/diffpane opening blank in sessions where 64 or more turns edited files/contextsending its full visual grid to Claude on every later turn; Claude now reads only the tableclaude -pexiting 0 in auto mode when its actions were refused because no safety check was available: text and JSON output now exit 1/statusshowing "Auto mode server: Enabled" when the server-side review isn't reaching the session, for example behind an LLM gateway that drops it/feedbackcontinuing to appear after the server refused feedback for your organizationautoModesettings are very large: it now explains and, unlessautoModedeny rules are set, asks you in the terminalclaude -p --resumewith a prompt losing a deferred tool call when its MCP server is missing: the run now exits 1, keeps the call and refuses later inputCLAUDE_CODE_RESUME_INTERRUPTED_TURNre-running a turn that was interrupted in plan mode when the session resumes in another permission mode~/.claude.json, settings and edited files ending up empty or cut off when the disk fills during a save in a read-only folder or to a bind-mounted file (one session saving at a time)opus-5-5, telling you to update Claude Code instead of suggesting the model you meantNotebookEditchanged the wrong cell when the notebook changed while a permission prompt was open/loginsuccess screen: the dialog now dismisses immediately and the post-login refresh runs in the backgroundCLAUDE_CODE_PROXY_RESOLVES_HOSTSis set and the machine has no DNS of its ownclaude plugin evalwarnings suggestingmax: 0for a tool that must not be called, which could never pass.claude/skillsmissing a file that was deleted just after it appeared, and missing its return/rewindfailing with "No files were restored" when restoring code to a checkpoint from before/branch/claude-apiskill saying Console web settings don't apply to Managed Agents sessions, and tightened its credential and permission examplestimeout DURATION, such astimeout 30 rg fooout_dir) were refusedCLAUDE_CODE_CLIENT_CERTto collectors that require a client certificateclaude_code.session.countmetric counting Agent SDKprewarm()processes that were never claimed; a pre-started process now counts once, when it is claimed/clearkilling running commands of background agents, teammates and workflows that keep running, and foreground subagents of background agents and teammatesinvalid_token**, backticks and tags from commands waiting for approval/permissionsin cloud sessions replying only that it isn't available; it now says where the session's rules live and how to change them/cleardisappearing from the task list in Claude Code on the web until another task started or ended/rewindcould restore or delete a file through a directory symlinksedcommand could skip the permission check in accept-edits and auto modeCLAUDE_CODE_AUTO_MODE_SERVER=1in managed settings was ignored behind an LLM gateway when the gateway's URL is set only there and server-managed settings can't be fetcheddisallowedToolsentries written with a claude.ai connector's terminal name (mcp__claude_ai_Slack) were ignored in Claude Desktop (takes effect once Claude Desktop includes this version)--trust-workspace falsenow also stops hooks in the repository's settings files and skills from running/statusand the auto mode billing notice opening only part of the address when they wrapCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICwas set. With it set, Claude Code now makes a TLS handshake with the configured API host after a certificate failure, through your http:// proxy if one is set; it sends no API requestclaude remote-controlexiting silently with status 0 when a first-run question gets no answer (scripts, services, batch jobs, Ctrl+C); it now says why and exits 1claude remote-controlignoring a pipedythat has no newline after it at the first-run question; it now counts as a yes/renamereporting plain success when the new name could not be saved to the session transcript; it now warns that the new name may not last${CLAUDE_PLUGIN_ROOT}not being substituted in a plugin-providedsubagentStatusLinecommand, which can now reference the plugin's own scriptsclaude plugin updateand/plugin"Update now" not installing dependencies added by the new plugin version~/.claude.jsonemptyjavascript_toolresults of up to 60,000 characters now stay in the conversation instead of being saved to a fileclaude purgeand the clean-up of old sessions to retry a folder that could not be fully deleted, and to report it as an error if it remains/stats,/modeland/sandbox, and rejected-action messagesadmin.blocked_messageif one is set/modelpicker: older models are now grouped under a "More models" row instead of being listed after the current ones/contextat the terminal so the table Claude reads stays short: each list keeps its 10 largest rows, and MCP tools that load on demand share one row per server until they're called/usagein cloud sessions: it now links to Settings → Usage on claude.ai in a case where plan limits can't be shownDISABLE_TELEMETRY); setCLAUDE_CODE_DISABLE_MCP_TASKS=1to turn them offCLAUDE_CODE_PROXY_RESOLVES_HOSTSso that settings files can no longer set it where the host manages the network; set it in the process environmentwhichwith flags outside a lookup/display set--add-dirdirectories to register plugin marketplaces only once that directory's own trust dialog has been accepted.claude/skillsfolders below the starting folder load only if you start Claude Code there or/cdthere/loopto end when a turn finishes without rescheduling, instead of scheduling a fallback wakeup; setCLAUDE_CODE_LOOP_KEEPALIVE=1to keep the old behaviorALL_PROXYis the only proxy variable set. SetHTTPS_PROXYto the proxy's http:// URL instead/claude-api managed-agents-onboardtemplates to match the Claude Console: removed Performance tuner, renamed two, and turned off web search and fetch in five whose prompts don't use themshortcuts_listandshortcuts_execute, which listed and started shortcuts saved in the extension, from Claude Code's built-in Claude in Chrome toolsbedrockupstream sets aguardrail--use-anthropic-git-proxyor--configure-gitregistering before a failed startup check made it exit; it now exits firstCLAUDE_RUNNER_CHECKOUT_PATHso that each repository in a session gets its own folder: a folder name already taken in the session gets-2,-3, … at the end--remove-session-stateis set/clear, or Retry or Edit of a typed prompt, had removedclaude-vscode.toggleDictationcommand starting dictation in every open Claude view at once; it now acts only in the view you are using, and a second press stops it$$math fences, each shorter than the last, streams inv2.1.318Compare Source
assume_roleonmantleupstreams of the Claude apps gateway, for a role in another AWS account and for per-developer AWS cost attributioneffortoption to a mod's$.model.fork, so a quick side job can run atlowwhatever effort the session uses; the result reports the effort sentclaude auth status(loginExpiresAt) and toclaude -pJSON results (credential_expires_at)claude -ptext output, starting 10 days before a stored claude.ai sign-in ends--continuesometimes losing the earlier conversation after a malformed tool call's retries ran out (regression in 2.1.314)/logout,claude auth logoutandclaude mcp removereporting success, and changes to trust, consent or MCP settings being dropped with no word, when the config file could not be updated on a shared network home directoryNot logged inwhen another terminal or host signs in again to the same account and organization on the same homeclaude mcp addandremovewriting the config without its lock: they now wait for it or exit 1, though another job's save can still replace a saved serverclaude plugincommands exiting before a slow token refresh was saved, which could sign you out on the next runclaude plugin validatepassing a custom-named marketplace file thatclaude plugin marketplace addrejectsallowedProviderslist that another login on the same machine had storedclaude -pand SDK sessionsclaude -pand Agent SDK sessions reporting success when an API error cut off a reply while a mod hookedturn.stepclaude remote-controlhosts, the background daemon and self-hosted runners failing to start new sessions (spawn ENOENT) after an update or version cleanup removed the binary of a still-running processsudo claude) being treated as dead by version cleanup, which could delete its binary/remote-controlshowing a session as available after a failed connection/design revokereporting success when the request failed with a 404Setuphook writes toCLAUDE_ENV_FILEnot reaching the Bash tool in some cloud sessionsNODE_EXTRA_CA_CERTSfile is empty, not PEM, or starts with a damaged certificate: readable certificates are now used, with a warning on stderr/mcpin cloud sessions counting tools the model can't use; a server's row now shows how many of its tools are availableturn.stephook making a stopped reply finish as a success in headless runsclaude -pwith no~/.claude.jsonbackup: it now takes a fresh backup before deleting the last good onesetup-tokenbeing refused at start on machines withforceLoginOrgUUID, when the token belongs to a permitted organization~/.claude.jsonthat isn't valid JSON with defaults; the start now fails, says how to restore the file, and leaves it as is (#87551)~/.claude.jsonwith no backup being reported as corrupted; Claude Code now starts as it does when the file is missing~/.claude.jsonnaming an empty or cut-off backup, or failing on a read-only fileclaude -pnamesclaude auth loginandclaude setup-token~/.claude.json, settings files and the stored login survive saves on shared network home directories: they are less often deleted, briefly emptied or replaced by a near-empty or older copy/bin/bashclaude -p, SDK apps) to stop rewriting~/.claude.jsonon every run when nothing in it changed/idefrom an outside terminal or your editor's extensions viewprompt.submitto stay in the user's turn rather than go out as a system messagedeniedMcpServersURL entries to also block Anthropic-provided servers whose upstream URL matches, and connectors in cloud sessions and on self-hosted runners, where the session is given the connector's own URL; otherwise deny a connector by name/permissionsrule details, built-in rules and delete confirmation views to use the standard dialog; pressing Ctrl+C twice there now goes back or cancels instead of quitting/claude-api managed-agents-onboardto give a new agent's built-in tools, and a quickstart template's MCP tools, theautopermission policy ("Judge risky actions") by default, matching the Claude Console; say "run without asking" to opt outexternal_account) credentials file is about to expirelisten.trusted_proxies: they now say to list only a proxy that adds the connecting address toX-Forwarded-ForitselfCLAUDE_RUNNER_SPAWN_REASONto the orchestrator's spawn-runner hook environment: why Anthropic sent the request (e.g.runner_lost,resumed); unset when none was sent--release-idle-session-minis the last argument with no value (still ignored) or has a value of only spaces (still read as0)ok session=…now prints at every log level on stdout (was debug only, stderr) withreason=…afterjti=…, andnack session=…ends its fields withreason=…afterretryable=…; update scripts that matchretryable=true:orretryable=false:gh run view --logandgh apilog requests now get the log in most environments, not an unreachable redirectv2.1.317Compare Source
/schedulewhen a new cloud scheduled task gets connectors you did not ask for, with how to remove themonFailure: "block"for Agent SDK hook callbacks, so a callback that fails blocks the action instead of letting it runanthropic.plan,anthropic.seat_type,anthropic.providerandanthropic.custom_base_urlto OTel metrics, events and spansGET /v1/organizations/analytics/cost, for reading past spend over a date range in total, per developer, per day or per IdP groupadmin:set, kept foradmin.identity_retention_days, which the cost report groups byCLAUDE_CODE_DISABLE_NESTED_SESSION_ID: set it to1on a self-hosted runner to haveclaude -prun inside a session use that session's ID and transcript, as in earlier versionsclaude auth statusexiting before a slow token refresh was saved, which could sign you out on the next runeffortLevelsetting being ignored by sessions that an app starts ahead of time and then opens in the project, such as new sessions in the desktop app's Code tabclaude --from-prreporting "No conversations found" in projects with many sessions when the linked session was older than the first page/loopwakeups sometimes not being scheduled when Claude left a field out of its request/scheduleleaving a cloud scheduled task's next run time and link out of its results after creating or updating itclaude -pexiting 0 when a full disk or quota lost its transcript or ~/.claude.json writes; it now prints an error and, in text and json output, exits 1. Full NFS exports may be missed--setting-sources/team-onboardingguide when asked to delete one without naming which/team-onboardingguide was deleted when the server refused the deleteAWS_BEARER_TOKEN_BEDROCKwhen their env config sets it to empty; the variable is now unset, so the server can use the machine's own AWS credentialsConfiguration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 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.