Bump Microsoft.Agents.AI and Microsoft.NET.Test.Sdk - #36
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps Microsoft.Agents.AI from 1.15.0 to 1.18.0 Bumps Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0 --- updated-dependencies: - dependency-name: Microsoft.Agents.AI dependency-version: 1.18.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: microsoft - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: microsoft ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/nuget/code/DRYL.Components.Agents/microsoft-fdbd03ec3e
branch
from
August 20, 2026 13:07
0471ed4 to
d987a73
Compare
Zimpi
added a commit
that referenced
this pull request
Aug 20, 2026
* fix(popover): a portal that moves the panel unchanged Re-inserting a node into the DOM resets scrollTop/scrollLeft on it and on every scrollable descendant, and the portal was two bare appendChild calls. So it did not move the panel; it moved the panel minus whatever scroll its content held, silently. DrylTimePicker is where that showed: a picker bound to 14:30 opened at 00/00 with its own value two hundred pixels out of sight. The handover recorded this as "scrollToActive is ineffective at the hidden panel, same cause as the fixed focus bug". Measured at /components/timepicker, that is wrong twice over. A hidden element keeps its layout box — called by hand against a panel with .is-open and no data-dryl-positioned, visibility confirmed hidden, the scroll landed at 310/854 exactly as when visible. And the scroll was never ineffective: hooking the module showed scrollToActive succeeding against the panel while its parent was still the anchor, then focusPanel finding parent BODY and both columns at 0. The appendChild between them discarded it. So the defect is the popover's, not the time picker's, and it is fixed in the primitive: moveKeepingScroll carries the state across both moves. Every panel built on it is covered — any component that scrolls popover content before the portal had the same defect waiting. No DrylTimePicker file is touched, which also settles SPEC-01: that component has no spec and may not be written to, while DrylPopover has one and it has been read. Verified: 14:30 opens at 310/854 with both cells in view, on first open, on re-open and for a picker with no value, in both colour modes; DrylMenu, DrylDatePicker and DrylMultiSelect opened, scrolled and closed after it with nothing stranded under <body>. 1065 tests green; light-sync, contrast, harness-links and motion-tokens all green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * chore(deps): bunit 2.9.0 and Test.Sdk 18.9.0 Test project only, so <Version> stays where it is (REL-03). 1065 tests green on both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * chore(deps): xunit.runner.visualstudio 4.0.0 A MAJOR, so it gets its own commit: if discovery or a runner behaviour regresses, this is the bisect point. All 1065 tests are still discovered and still pass, which is what the major would have broken. Test project only (REL-03). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * chore(deps): Microsoft.Agents.AI 1.18.0 (Agents 0.17.6) Unlike the three bumps before it this one is shipped: it moves the dependency floor of DRYL.Components.Agents for every consumer, so it takes an Agents PATCH and a changelog entry (REL-01, REL-02) — the same shape the 1.13.0 -> 1.15.0 bump took under [2.20.2]. Dependabot's PR #36 carries the csproj line alone, which is why the bump is taken here instead: merging it as it stands would publish a package whose floor moved with nothing saying so. Build clean, 1065 tests green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * test: one suite-wide wait timeout instead of 88 implicit ones 88 of the suite's 95 WaitForAssertion / WaitForState calls took bUnit's default of one second implicitly. One second is not a statement about any of those tests — it is a number nobody chose, and it is thin for what this suite waits on: a streamed IAsyncEnumerable draining, a canvas re-render, a DrylPresence exit watchdog. DrylAiStreamTests already carries that reasoning in a comment and its own explicit timeouts; this generalises it. Set once via BunitContext.DefaultWaitTimeout in a module initializer, rather than written onto 88 call sites: the value is a property of the machine the suite runs on, not of any single assertion, and a number repeated 95 times only invites drift. The seven sites that already pass three seconds now agree with the default; anything needing a different bound still overrides it locally. It costs a passing suite nothing, because WaitForAssertion returns the moment its assertion passes — measured at 4s before and 4s after, over three full runs. One fact comes with it, because a suite that stays green is exactly what it would look like if the initializer never ran. Tests only, so <Version> is untouched (REL-03). 1066 green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * docs: the two split-button layout screenshots, both modes Evidence for the DRYL.Website change on branch docs/split-button-loose-ends, kept here because docs/screenshots/ is where this repository's by-eye evidence lives. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L * docs: record what the four tasks actually did Two of them did not go the way the plan said, and the plan is worth less if it only records the intention. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QoXQ4L9XzgZJv5X9sZZb1L --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Contributor
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/code/DRYL.Components.Agents/microsoft-fdbd03ec3e
branch
August 20, 2026 13:40
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
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.
Updated Microsoft.Agents.AI from 1.15.0 to 1.18.0.
Release notes
Sourced from Microsoft.Agents.AI's releases.
1.18.0
What's Changed
New Contributors
Full Changelog: microsoft/agent-framework@dotnet-1.17.0...dotnet-1.18.0
1.17.0
What's Changed
1.16.0
What's Changed
New Contributors
Full Changelog: microsoft/agent-framework@python-github-copilot-1.0.0...dotnet-1.16.0
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.9.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.8.0...v18.9.0
Commits viewable in compare view.