build(deps): bump the npm_and_yarn group across 5 directories with 7 updates - #5
Merged
LeXwDeX merged 1 commit intoApr 14, 2026
Conversation
…updates Bumps the npm_and_yarn group with 1 update in the /packages/console/app directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler). Bumps the npm_and_yarn group with 1 update in the /packages/desktop-electron directory: [electron](https://github.com/electron/electron). Bumps the npm_and_yarn group with 2 updates in the /packages/opencode directory: [@hono/node-server](https://github.com/honojs/node-server) and [minimatch](https://github.com/isaacs/minimatch). Bumps the npm_and_yarn group with 1 update in the /packages/ui directory: [dompurify](https://github.com/cure53/DOMPurify). Bumps the npm_and_yarn group with 2 updates in the /packages/web directory: [@astrojs/cloudflare](https://github.com/withastro/astro/tree/HEAD/packages/integrations/cloudflare) and [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Updates `wrangler` from 4.50.0 to 4.59.1 - [Release notes](https://github.com/cloudflare/workers-sdk/releases) - [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.59.1/packages/wrangler) Updates `electron` from 40.4.1 to 40.8.5 - [Release notes](https://github.com/electron/electron/releases) - [Commits](electron/electron@v40.4.1...v40.8.5) Updates `@hono/node-server` from 1.19.11 to 1.19.13 - [Release notes](https://github.com/honojs/node-server/releases) - [Commits](honojs/node-server@v1.19.11...v1.19.13) Updates `minimatch` from 10.0.3 to 10.2.3 - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](isaacs/minimatch@v10.0.3...v10.2.3) Updates `dompurify` from 3.3.1 to 3.3.2 - [Release notes](https://github.com/cure53/DOMPurify/releases) - [Commits](cure53/DOMPurify@3.3.1...3.3.2) Updates `@astrojs/cloudflare` from 12.6.3 to 12.6.6 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/cloudflare/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/@astrojs/cloudflare@12.6.6/packages/integrations/cloudflare) Updates `astro` from 5.7.13 to 5.18.1 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/astro@5.18.1/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@5.18.1/packages/astro) --- updated-dependencies: - dependency-name: wrangler dependency-version: 4.59.1 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: electron dependency-version: 40.8.5 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: "@hono/node-server" dependency-version: 1.19.13 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: minimatch dependency-version: 10.2.3 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: dompurify dependency-version: 3.3.2 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: "@astrojs/cloudflare" dependency-version: 12.6.6 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: astro dependency-version: 5.18.1 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Apr 14, 2026
Contributor
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
Contributor
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
Uh oh!
There was an error while loading. Please reload this page.
dependabotBot
deleted the
dependabot/npm_and_yarn/packages/console/app/npm_and_yarn-eb028ad470
branch
April 14, 2026 06:38
LeXwDeX pushed a commit
that referenced
this pull request
Jun 7, 2026
… 20/21 scenarios The replan feature (commit bd8c007) ships with full code-path coverage via the existing 96 session tests + 462 DAG suite but no dedicated tests exercising replan logic. This commit adds dedicated unit-test coverage. Architectural ruling (COMBINED path): - Path A (pure helpers) as primary — extracted 6 helpers from the replanWorkflow closure to module-level exports for direct testing. - 3 @internal module-private read getters (__internal_spawnedNodes / __internal_replanInFlight / __internal_concurrencyRegistry) for scenarios 18-20 (module-registry coordination). - Scenario 21 (history row correctness) deferred to integration tier — requires DB state inspection beyond unit-test scope. Coverage: 20/21 unit-testable scenarios, 1 deferred. Total tests added: 42 across 7 describe blocks. Session suite total: 96 existing + 42 new = 138 pass / 0 fail. Production code changes in workflow-engine.ts (pure extract-and-delegate): - 6 extracted helpers: validateReplanPreconditions, classifyReplanNodes, validateFrozenAndExistence, applyReplanPatchToConfig, validateReplanPostConfig, buildReplanDbInputs. - detectCycle (module-level, previously private) now exported for validateReplanPostConfig use and test access. - 3 @internal test-only getters at lines 313, 315, 317. - replanWorkflow body refactored to delegate to helpers in sequence (L668-695); all validation completes before atomicReplan call at L704 (sequential guard preserved). Helper signatures follow the ReplanResult discriminated-union pattern (types.ts:495-505): { ok: true, data? } | { ok: false, reason, detail? }. This avoids throwing inside pure helpers and makes test assertions simple (assert ok boolean + reason string). P0-fix test coverage (critical regression safety): - 'namespaces new_dependencies on updates' (test at L512-528): asserts ['n2'] -> [wf::n2] after applyReplanPatchToConfig. - 'preserves existing deps when new_dependencies is absent' (test at L530-553): asserts ['wf::old-dep'] -> ['wf::old-dep'] when patch omits new_dependencies field (the existing-deps fallback). - 'namespaces add_nodes dependencies for DB layer' (test at L555-570): asserts add_nodes deps receive the same wfNs treatment as updates. Behavioral tests for scenarios 18-20 (module registry coordination): - Use beforeEach to clear registries via the @internal getters (Set/Map mutable types — ReadonlySet would break .delete() test cleanup). - Assert .has().size().get() on module state AFTER patch application (not just 'no exception thrown') — real state verification. Sequential guard preserved: validateReplanPostConfig at L691 is the last validation before atomicReplan at L704. Effect.fail semantics from helpers short-circuit the Effect.gen before any DB writes. Iron Laws re-verified: - #1 state-machine only: replan modifies only config/dependencies JSON columns, never status. - #2 terminal irreversible: frozen-set covers all non-pending states. - #3 event broadcast: replan is structural mutation, not status transition; dag_workflow_history row is the audit (event emission is a pre-existing gap noted but not blocking per archgate). - #4 persist first: atomicReplan uses Database.transaction for 5 atomic writes. Verification: typecheck 0 errors; 138/138 session tests pass; 504/504 non-worktree DAG tests pass; all sanity greps (7 helpers + 3 internal getters + 6 helper call sites + sequential-guard ordering) match expected patterns. Deferred (separate follow-up WPs): - Scenario 21 — history-row DB-state inspection (integration tier). - detectCycle @internal JSDoc (INFO #1 from review #2, optional). - Test n1/n2/n3 scope hygiene refactor (INFO #5, currently safe). - Iron Law #3 replan event emission (pre-existing gap, tracked).
LeXwDeX pushed a commit
that referenced
this pull request
Jun 7, 2026
- restore API_NATIVE_MODEL_TEMPLATES for @ai-sdk/openai (gpt-5.5) and @ai-sdk/anthropic (claude-opus-4-6/4-8) - restore COPILOT_MODEL_TEMPLATES for claude-opus-4.6/4-8 and gpt-5.5 - only correct fields of already-existing models; never add/delete/rename model keys - never modify provider URL/API Key - small_model/compaction boundaries preserved (only fill on missing key, skip on bad type) - renumber sections: #4 model correction, #5 health check - OC_VERSION 1.3.5 → 1.3.6 - restore 'import copy' for deepcopy safety
LeXwDeX pushed a commit
that referenced
this pull request
Jun 14, 2026
…rompts (AHE discipline) Problem observed: WP1-WP4 delivered recoverable non-terminal state, failure_policy config field, replan remove+add replacement, and TUI/API visibility enhancements, but the agent-facing prompt files (dag.txt, dagworker.txt, dagworker-reference.md) remained at pre-WP0 state. The LLM agent could not discover or exploit the recoverable retry path because: - Node status table listed only pending/queued/running/completed/ failed/skipped — no 'recoverable' - DAGNodeConfig schema lacked 'failure_policy' field documentation - State machine diagram lacked running→recoverable/recoverable→pending/ recoverable→failed transitions - Required+recoverable nodes silently skipped required_node_failed violation — documented as always terminalizing - Replan three-tier classification (Frozen/Removable/Mutable) missing; agent couldn't know recoverable nodes are removable (not frozen) - Failure investigation flow lacked recoverable recovery sequence This made all four recoverable-related WPs effectively invisible to the orchestrating agent, defeating the core retry intent. Design intent (AHE discipline, aligned with commit bfbd5a1/95a4b3fac): - Description paragraph = facts only ('what is this', schema shapes, state machine topology) - Rules paragraph = hard constraints + rejection evidence ('cannot do what + why' with error message / rejection code) - No behavior guidance ('you should consider', 'usually', 'typically') - No cross-layer duplication beyond the allowed summary→detail expansion (dag.txt Part II → dagworker-reference.md Part II) - Every rule must state falsifiable condition (rejection code / error message / state transition legality) Implementation (3 files, +53 lines within +80 budget): dag.txt (+6 lines, 219→225): - Node status union: added 'recoverable' row with non-terminal + waiting-for-replan semantics (L19, L24) - Workflow status semantics: recoverable nodes block computeFinalWorkflowStatus from completing/failing (L35) - Action list: dagworker status output includes recoverable count; replan treats recoverable as removable (L44, L49) - DAGConfig JSON example: added failure_policy field with default 'fail' and 'recoverable' alternatives (L105) - node_complete: child agent doesn't control recoverable transition (engine decides by failure_policy; L149) - required+recoverable exception: does NOT trigger required_node_failed violation (L178; aligns with workflow-engine.ts:1514-1560 early return before L1765 violation) - Terminal immutability: recoverable non-terminal, only pending (reset) or failed (abandon) outgoing transitions allowed (L185; aligns with execution-core.ts:431) - Replan classification: recoverable = Removable; update_nodes targeting recoverable rejected (L197; aligns with execution-core.ts:287-288 + reason at L293) - **DELETED** L200 'Trigger keywords' paragraph (AHE behavioral guidance violation — 'keywords: X, Y, Z trigger this' is guidance, not constraint) - L209-215: Failure investigation replaced vague 'usually make the workflow terminal' with precise policy-based semantics: failure_policy='fail' (or unset) cascades → may terminalize; failure_policy='recoverable' stays running; replan is the recovery path; recoverable node recovery sequence (status → find recoverable → replan remove+add → resume) dagworker.txt (+1 line, 29→30): - status action: recoverable count added to real-time polling state (L11) - replan action: recoverable nodes removable for retry/replacement; frozen nodes (queued/running/completed/failed/skipped) remain immutable (L16) - Failure recovery rule #5 (new): failure_policy='recoverable' transitions running→recoverable instead of running→failed; workflow stays running/paused; parent agent uses replan to remove recoverable + add replacement with corrected worker_config; recoverable→running illegal (must reset to pending first to prevent state-machine bypass; L30) dagworker-reference.md (+46 lines, 711→757): - §5 DAGNodeConfig Schema: added failure_policy?: 'fail'|'recoverable' field with semantics (L248, L263-266) - §6 Node Status State Machine: updated diagram with running→ recoverable and recoverable→pending/recoverable→failed transitions (L324-335); added 3-row transition table entries: | running | recoverable | failure_policy='recoverable' on node failure | | recoverable | pending | reset for re-run (via replan remove+add) | | recoverable | failed | abandon — terminal, no outgoing transitions | - §7 Workflow Status State Machine: recoverable blocks completion paragraph (L388); required+recoverable note (does NOT trigger required_node_failed violation; stays running) - §11 Event Bus: added node.recoverable event with payload { workflow_id, node_name, trigger_reason, error? } (L447; aligns with state-machine/types.ts:340-345 and session-service.ts:143-150) - §13 Replan: three-tier classification subsection Frozen/Removable/ Mutable (L505-509); remove_nodes includes recoverable (L527) - §15 State Machine Rules: 'Recoverable non-terminal' subsection with 3 rules — allowed pending/failed outgoing, rejected recoverable→ running (must reset through pending first; L621-625); aligns with execution-core.ts:429/431 - §16 Replan Constraints: updated classification table adds recoverable = Removable row (L647); required+recoverable exception note (L660); common mistake: 'update_nodes on recoverable — rejected' with execution-core.ts:293 rejection reason (L668) - §17 Failure Investigation & Recovery: updated partial failure recovery subsection to explicitly use 'recoverable' term (L688-710); new 'Recoverable node recovery sequence' 5-step procedure: 1. Query workflow status; identify node with status='recoverable' 2. Optionally pause workflow (prevent further spawn attempts) 3. Replan remove_nodes=[recoverable] + add_nodes=[replacement] 4. Resume workflow; forked scheduleReadyNodes auto-triggers 5. Observe WP4 notification metadata (dag_failed_nodes array) 3 new common mistakes at L751-753: update_nodes on recoverable (rejected), recoverable→running direct (illegal bypass), skipping status query before replan Bonus fix (not in spec, harmless): - 3 pre-existing 'dapworker' typos → 'dagworker' at §17 L692/L694/ L704 (pre-existing from stable branch) Foundation code fidelity (15/15 claims validated by archgate): - execution-core.ts:429 running→recoverable legal transition - execution-core.ts:431 recoverable→[pending,failed] only - execution-core.ts:244-265 three-tier classifyReplanNodes - execution-core.ts:287-288 recoverable NOT updatable - execution-core.ts:293 rejection reason text matches §16 L668 - execution-core.ts:90 recoverable excluded from ready set - execution-core.ts:116 recoverable blocks finalization - types.ts:253 failure_policy field shape matches §5 L248 - types.ts:584-586 recoverable NOT in isNodeTerminalStatus - workflow-engine.ts:1514-1560 recoverable branch early returns before L1765 required_node_failed violation - workflow-engine.ts:1990-2013 WorkflowStatusSnapshot.recoverableCount - state-machine/types.ts:340-345 node.recoverable event shape - session-service.ts:143-150 node.recoverable event emission - dag-bus-bridge.ts:271-272 node.recoverable bridges 'recoverable' status string - scenario-36/37 TDD validates all claims INFO-level findings (non-blocking, for future iteration): - §12 Examples lacks recoverable-specific scenario (e.g., 3-node pipeline with one recoverable demonstrating remove+add). Deferred acceptable — agent can infer procedure from §17 5-step sequence. - dag.txt L176 vs dagworker-reference.md L605: pre-existing node cap discrepancy ('≤20' vs '≤100'). Not introduced by this diff (stable branch pre-existing). Recommend reconciling in separate WP to avoid agent confusion. Workflow: archgate (1 round, PASS with 15/15 foundation claims validated), implement (1 round, +53 lines in +80 budget), review (1 round, 0 blocking / 3 info all P2 non-blocking), direct commit (no patcher step required for text-only edits).
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 freeto 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.
Bumps the npm_and_yarn group with 1 update in the /packages/console/app directory: wrangler.
Bumps the npm_and_yarn group with 1 update in the /packages/desktop-electron directory: electron.
Bumps the npm_and_yarn group with 2 updates in the /packages/opencode directory: @hono/node-server and minimatch.
Bumps the npm_and_yarn group with 1 update in the /packages/ui directory: dompurify.
Bumps the npm_and_yarn group with 2 updates in the /packages/web directory: @astrojs/cloudflare and astro.
Updates
wranglerfrom 4.50.0 to 4.59.1Commits
37a8607Version Packages (#11890)99b1f32fix: execute git commands in pages deploy safely (#11889)e98c95aVersion Packages (#11836)ad65efaAdd--checkflag towrangler types(#11852)beb96affeat(unenv-preset): add support for native node:sqlite module (#11841)b0e54b2[wrangler] Add AI agent detection to analytics events (#11820)2203af4Add Node.js 24 and 25 compatibility to the test suites for Miniflare, Wrangle...b6148edchore(deps): bump the workerd-and-workers-types group with 2 updates (#11872)0eb973dDo not warn user when using a redirected config that came from a config with ...0f8d69dcontainers: users can set multiple tiers for constraints (#11755)Updates
electronfrom 40.4.1 to 40.8.5Release notes
Sourced from electron's releases.
... (truncated)
Commits
c09e2aafix: outdated execution path for COM activation (#50518)44f02f6fix: hex-encode Windows notification icon temp filenames (#50484)904fbbdfix: fall back to default DPI when GTK returns 0 on Linux (#50488)36c88a4fix: [a11y] fire AXMenuOpened event when ARIA menu is added to DOM (#50505)9bf9c36refactor: remove dead named-window lookup from guest-window-manager (#50495)d284168fix: crash calling OSR shared texture release() after texture GC'd (#50500)4aa3610fix: crash in clipboard.readImage() on malformed image data (#50491)e1c17fdchore: cherry-pick fbfb27470bf6 from chromium (#50438)2871c1dfix: read nodeIntegrationInWorker from per-frame WebPreferences (#50122) (#50...0d3f57fchore: cherry-pick 074d472db745 from chromium (#50449)Updates
@hono/node-serverfrom 1.19.11 to 1.19.13Release notes
Sourced from
@hono/node-server's releases.Commits
fd64e651.19.13025c30fMerge commit from fork6cdb5a71.19.1270250f7fix: request draining for early 413 responses (#329)cfc08b3chore: ignore claude setting (#314)Updates
minimatchfrom 10.0.3 to 10.2.3Changelog
Sourced from minimatch's changelog.
... (truncated)
Commits
ea9484010.2.30873fbaupdate depscecaad1more extglob coalescing for performance11d0df6limit nested extglob recursion, flatten extglobsc3448c4update assertValidPattern param type to unknown from any0bf499alimit recursion for **, improve perf considerably9f15c58update depsf42b23910.2.2fa2133bupdate depsb9d0153ci: update action workflowsUpdates
dompurifyfrom 3.3.1 to 3.3.2Release notes
Sourced from dompurify's releases.
Commits
5e56114Getting 3.x branch ready for 3.3.2 release (#1208)e8c95f4fix: Fixed the broken package-lock.json9636037Update package-lock.json5cad4ceGetting 3.x branch ready for 3.3.2 releas (#1205)Updates
@astrojs/cloudflarefrom 12.6.3 to 12.6.6Changelog
Sourced from
@astrojs/cloudflare's changelog.Commits
24b04c1[ci] release (#14267)fbec0e0[ci] format9ecf359Merge commit from fork4823c42feat(netlify): dev context (#14269)d471be5[ci] release (#14242)02366e9fix: don't warnign when using in static build (#14259)15b55f3Filter duplicate exports from Cloudflare adapter'snamedExports(#14234)77b18fbUpdate Astro peer dependency in adapters with auto-enabled sessions (#14240)9288133[ci] release (#14232)Updates
astrofrom 5.7.13 to 5.18.1Release notes
Sourced from astro's releases.
Changelog
Sourced from astro's changelog.
... (truncated)
Commits
434d9cc[ci] release (#15829)c2cd371fix(helpers): Backport remote patterns segments fix (#15828)011f061[ci] release (#15597)efae11cfix: X-Forwarded-Proto rejected when allowedDomains includes protocol… (#15594)751ccf0Update actionBodySizeLimit changeset and make minor (#15600)b7dd447make actionBodySizeLimit configurable (#15589)e0f1a2b[ci] release (#15571)522f880Limit action request body size (#15564)436962achore: Upgrade Vite and esbuild (#15554)e01e98bRespect remote image allowlists (#15569)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.