build(deps): Bump golang.org/x/oauth2 from 0.35.0 to 0.36.0 in the go-dependencies group - #1
Merged
Conversation
Bumps the go-dependencies group with 1 update: [golang.org/x/oauth2](https://github.com/golang/oauth2). Updates `golang.org/x/oauth2` from 0.35.0 to 0.36.0 - [Commits](golang/oauth2@v0.35.0...v0.36.0) --- updated-dependencies: - dependency-name: golang.org/x/oauth2 dependency-version: 0.36.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
deleted the
dependabot/go_modules/go-dependencies-a3752b815f
branch
August 12, 2026 02:01
alicoding
added a commit
that referenced
this pull request
Aug 12, 2026
… self-cancel Owner-mandated framework, researched to the converged standard and found to need NAMING, not building: Scrum 2020's DoD (a formal artifact commitment) + Kanban University's ready-for-delivery pull criteria are the industry vocabulary for gates this repo already runs — consolidated into ONE always-loaded rule (.claude/rules/delivery-discipline.md) instead of four documents. Estimation deliberately excluded (negotiates team capacity a solo+agent loop doesn't have); peer review already settled by ADR-0034. Build-health becomes a ritual, not a wonder: gh pr checks --watch after opening a goal PR; gh run list -b main -L 1 at goal pickup. Tech debt: same queue, same DoR/DoD, never a shadow register. Plus the real config bug the research found: cancel-in-progress applied to main's post-merge runs too, so two quick merges cancelled the earlier one's verification (observed live: merges #1/#10) — now conditional per GitHub's own documented pattern; PR runs still supersede, main runs always complete. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
4 tasks
alicoding
added a commit
that referenced
this pull request
Aug 12, 2026
…nding #1) (#33) Root cause, confirmed via real CI history (6/6 shard-1 failures, all after goal 0017 merged, zero before) and local reproduction (9/20 clean-canvas repeats failed with zero artificial load): goal 0017 gave every direct-mutation service its own dataevent.Emit call, so a single MCP update_workflow write now fires mill-data-changed TWICE (SnapshotDraft + UpdateWorkflow) plus a third echo from the test's own prior UI-driven CreateWorkflow. None carry payload content, so each handler independently refetches — three fetches racing meant whichever resolved last won unconditionally, letting a stale response beat an already-applied newer one and wrongly show the external-change banner on a clean canvas. Fixed in useCanvasLiveSync.ts with a monotonic request-sequence guard (the standard out-of-order-async-response fix): drop a fetch response once a newer mill-data-changed event has arrived since it was dispatched. Verified: 88 consecutive clean local repeats post-fix vs. 9/20 before it, same build. Also: canvas-live-sync.spec.ts's cleanup hardened into an outer try/finally (both tests) so a future assertion failure can't leave an undeleted workflow / unattended-MCP-writes settings for later tests in the same worker — defense-in-depth for the observed cascade, independent of the root-cause fix. resizable-table.spec.ts's one occurrence (PR #24, drag-handle bounding box) hardened with a condition-based expect.poll wait at the point of use, additive to the suite's existing retries: 1 (goal 0024 precedent, untouched). BACKLOG.md Standing #1 checked off with the full root-cause writeup; SPEC.md's realtime-lock section gets an Update note generalizing the lesson for future mill-data-changed consumers. Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
alicoding
added a commit
that referenced
this pull request
Aug 13, 2026
…nding #1) Root cause, confirmed via real CI history (6/6 shard-1 failures, all after goal 0017 merged, zero before) and local reproduction (9/20 clean-canvas repeats failed with zero artificial load): goal 0017 gave every direct-mutation service its own dataevent.Emit call, so a single MCP update_workflow write now fires mill-data-changed TWICE (SnapshotDraft + UpdateWorkflow) plus a third echo from the test's own prior UI-driven CreateWorkflow. None carry payload content, so each handler independently refetches — three fetches racing meant whichever resolved last won unconditionally, letting a stale response beat an already-applied newer one and wrongly show the external-change banner on a clean canvas. Fixed in useCanvasLiveSync.ts with a monotonic request-sequence guard (the standard out-of-order-async-response fix): drop a fetch response once a newer mill-data-changed event has arrived since it was dispatched. Verified: 88 consecutive clean local repeats post-fix vs. 9/20 before it, same build. Also: canvas-live-sync.spec.ts's cleanup hardened into an outer try/finally (both tests) so a future assertion failure can't leave an undeleted workflow / unattended-MCP-writes settings for later tests in the same worker — defense-in-depth for the observed cascade, independent of the root-cause fix. resizable-table.spec.ts's one occurrence (PR #24, drag-handle bounding box) hardened with a condition-based expect.poll wait at the point of use, additive to the suite's existing retries: 1 (goal 0024 precedent, untouched). BACKLOG.md Standing #1 checked off with the full root-cause writeup; SPEC.md's realtime-lock section gets an Update note generalizing the lesson for future mill-data-changed consumers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
…ent registry semantics Three independent, verified changes (goal-scoped work, tasks #1/#4/#6): - task build/package/build:server now echo their real output path on success, and task run's darwin/linux/windows tasks gained a missing deps: on build:native -- previously `task run` assumed a binary already existed and would fail on a fresh clone, despite its name and summary implying it's a standalone build+launch command (run:server already had this right; desktop run: didn't). - internal/adapters/execution.New now takes a full DSN (databaseURL) instead of hardcoding "sqlite:"+dbPath internally. DBOS itself already accepts Postgres/CockroachDB DSNs; the scheme choice moves to the caller (main.go), which now reads MILL_EXECUTION_DATABASE_URL as an override, falling back to the existing MILL_EXECUTION_DB_PATH/default sqlite path unchanged. A regulated deployment needing an externally managed audit database gets there via config, not an adapter rewrite. - The three ADR-0006/ADR-0015 self-registration registries (RegisterNodeType, RegisterTrigger, RegisterAuthStrategy) have two different duplicate-key behaviors (panic vs silent overwrite), undocumented until now. Recorded on all three functions plus a SPEC.md cross-reference -- not a decision, just making a real, previously-invisible inconsistency visible. Verified: go vet, golangci-lint (0 issues), go test ./internal/... -race -cover (all pass), go build for both desktop and CGO_ENABLED=0-equivalent server tags, check-loc.sh, check-rules-frontmatter.sh. Frontend checks skipped -- zero frontend files touched, matching lefthook.yml's own glob scoping. Taskfile run: fix verified via `task --dry` (confirms build:native now runs before launch) plus one live task package run earlier in the session; full live task run execution was blocked by resource contention with an unrelated, pre-existing `task dev` session on this machine and deliberately not forced. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
…ncies-a3752b815f build(deps): Bump golang.org/x/oauth2 from 0.35.0 to 0.36.0 in the go-dependencies group
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
… self-cancel Owner-mandated framework, researched to the converged standard and found to need NAMING, not building: Scrum 2020's DoD (a formal artifact commitment) + Kanban University's ready-for-delivery pull criteria are the industry vocabulary for gates this repo already runs — consolidated into ONE always-loaded rule (.claude/rules/delivery-discipline.md) instead of four documents. Estimation deliberately excluded (negotiates team capacity a solo+agent loop doesn't have); peer review already settled by ADR-0034. Build-health becomes a ritual, not a wonder: gh pr checks --watch after opening a goal PR; gh run list -b main -L 1 at goal pickup. Tech debt: same queue, same DoR/DoD, never a shadow register. Plus the real config bug the research found: cancel-in-progress applied to main's post-merge runs too, so two quick merges cancelled the earlier one's verification (observed live: merges #1/#10) — now conditional per GitHub's own documented pattern; PR runs still supersede, main runs always complete. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
…nding #1) (#33) Root cause, confirmed via real CI history (6/6 shard-1 failures, all after goal 0017 merged, zero before) and local reproduction (9/20 clean-canvas repeats failed with zero artificial load): goal 0017 gave every direct-mutation service its own dataevent.Emit call, so a single MCP update_workflow write now fires mill-data-changed TWICE (SnapshotDraft + UpdateWorkflow) plus a third echo from the test's own prior UI-driven CreateWorkflow. None carry payload content, so each handler independently refetches — three fetches racing meant whichever resolved last won unconditionally, letting a stale response beat an already-applied newer one and wrongly show the external-change banner on a clean canvas. Fixed in useCanvasLiveSync.ts with a monotonic request-sequence guard (the standard out-of-order-async-response fix): drop a fetch response once a newer mill-data-changed event has arrived since it was dispatched. Verified: 88 consecutive clean local repeats post-fix vs. 9/20 before it, same build. Also: canvas-live-sync.spec.ts's cleanup hardened into an outer try/finally (both tests) so a future assertion failure can't leave an undeleted workflow / unattended-MCP-writes settings for later tests in the same worker — defense-in-depth for the observed cascade, independent of the root-cause fix. resizable-table.spec.ts's one occurrence (PR #24, drag-handle bounding box) hardened with a condition-based expect.poll wait at the point of use, additive to the suite's existing retries: 1 (goal 0024 precedent, untouched). BACKLOG.md Standing #1 checked off with the full root-cause writeup; SPEC.md's realtime-lock section gets an Update note generalizing the lesson for future mill-data-changed consumers. Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 24, 2026
alicoding
added a commit
that referenced
this pull request
Aug 27, 2026
…l 0235 S1) (#473) * feat: docs surface gets a grouped sidebar, breadcrumb, prev/next (goal 0235 S1) The in-app Docs surface was still goal 0125 phase 1: a flat NavList over markdown styled by the Atlas mirror-preview's bounded-box CSS. This is the structural half of a converged docs-site pass (search + TOC are S2): - Sidebar groups pages into collapsible sections by userdocs/ directory (DocsIndexEntry carries no group field, so grouping is derived client-side from each entry's rel prefix, in DocsIndex's own canonical order -- frontend/src/views/docsGroups.ts). Built on Primer NavList's own Item+SubNav accordion shape (confirmed against the installed .d.ts), not NavList.Group, which renders always-expanded. - A breadcrumb header (section, page title) replaces the bare content column; the article's own leading H1 (every userdocs/ page opens with one matching its title) is hidden to avoid repeating it. - A prev/next footer derived from DocsIndex's flat order, hidden at either end. - DocsView gets its own co-located stylesheet (~72ch measure, heading rhythm) composing the shared MarkdownProse base instead of the Atlas mirror preview's bounded-preview-box CSS. Extends the existing docs-view.spec.ts (grouped/collapsed sections, breadcrumb text, prev/next navigation) and adds docsGroups.test.ts for the pure grouping/adjacency logic. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012im1JxQQV2ahnXzZDdVmZq * test: register decision-outcome.spec.ts:132's second live-run sighting Same SUCCESS-status-polling class as the already-registered :192 entry -- the pinned-arm test hit a CI-load timeout once (PR #472's run), passed on retry #1, and ran 5/5 green locally. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012im1JxQQV2ahnXzZDdVmZq --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
Bumps the go-dependencies group with 1 update: golang.org/x/oauth2.
Updates
golang.org/x/oauth2from 0.35.0 to 0.36.0Commits
4d954e6all: upgrade go directive to at least 1.25.0 [generated]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 conditions