Repository navigation
chore: Update integration data and GitHub stats (11/4/26) - #1737
Conversation
aspire-repo-bot
Bot
added
the
auto-merge
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
No unresolved review issues were identified.
Review effort: Lite
Findings: None
What changed in this PR
Refreshes Aspire integration metadata, GitHub statistics, and generated API reference data for two CommunityToolkit packages.
Changes:
- Updates package versions, metadata, icons, and download counts.
- Refreshes GitHub star counts.
- Regenerates C# and TypeScript API metadata for Kind and Keycloak.
| File | Summary |
|---|---|
src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.Kind.13.5.1-beta.767.json |
Updated Kind TypeScript API metadata |
src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.Keycloak.Extensions.13.5.1-beta.767.json |
Updated Keycloak TypeScript API metadata |
src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.Kind.13.5.1-beta.767.json |
Updated Kind C# API metadata |
src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.Keycloak.Extensions.13.5.1-beta.767.json |
Updated Keycloak C# API metadata |
src/frontend/src/data/github-stats.json |
Updated repository star counts |
src/frontend/src/data/aspire-integrations.json |
Updated package metadata and download counts |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
aspire-repo-bot
Bot
changed the title
cb726a2 to
e3939ba
Compare
aspire-repo-bot
Bot
changed the title
e3939ba to
57196d9
Compare
aspire-repo-bot
Bot
changed the title
57196d9 to
520e020
Compare
aspire-repo-bot
Bot
changed the title
aspire-repo-bot
Bot
changed the title
520e020 to
731d076
Compare
…1899) ## Summary The Integration Data Updater has failed every run since a maintainer clicked **Update branch** on the rolling PR (#1737). That added a human-authored `Merge branch 'main' into chore/update-integration-data` commit. The "Commit and refresh automation branch" step refuses to replace the branch if it has any commit not authored/committed by the bot, so it errored with `Refusing to replace chore/update-integration-data because it contains non-bot commits` on every run after that. The data generation itself succeeded (e.g. `C# API: Success: 210 | Failed: 0`). A merge of `main` carries no maintainer changes, so the guard now uses `git log --no-merges`. Real maintainer commits on the branch are still protected (and the `--force-with-lease` remains). ## Third-party links and affiliations None. ## Validation - Reproduced root cause from failed run 38639537736 logs (step 11 failed; all earlier steps passed). - Ran the new `git log --no-merges origin/main..origin/chore/update-integration-data` against the live branch: only the bot commit `731d076d` is returned, so the guard now passes. - The workflow itself runs on schedule / `workflow_dispatch`; not run locally. --------- Co-authored-by: David Pine <7679720+IEvangelist@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
## Summary The [Keycloak integration page](https://aspire.dev/integrations/security/keycloak/) suggests initializing realms with the "[Keycloak Admin Client](https://www.nuget.org/packages/Keycloak.AuthServices.Sdk.Admin)". That package doesn't exist on NuGet, so readers land on a "package not found" page. The Admin REST API client from the same project ships in **`Keycloak.AuthServices.Sdk`**. This PR points the link there; the link text is unchanged. **Evidence** - NuGet v3 flat container: - `api.nuget.org/v3-flatcontainer/keycloak.authservices.sdk.admin/index.json` returns **404**. - `.../keycloak.authservices.sdk/index.json` returns **200** (latest 3.0.0). - NuGet search for `Keycloak.AuthServices` lists Authentication, Authorization, Common, Sdk, Sdk.Kiota, OpenTelemetry, Aspire.Hosting, Authorization.TokenIntrospection, Templates and Authorization.Uma. There's no `Sdk.Admin`. - The `Keycloak.AuthServices.Sdk` 3.0.0 NuGet description reads: "HttpClient integration with Keycloak. Includes HTTP Admin REST API, Protection API." - The upstream [Keycloak.AuthServices README](https://github.com/NikiforovAll/keycloak-authorization-services-dotnet#example---invoke-admin-api) "Invoke Admin API" example uses this package's `AddKeycloakAdminHttpClient` and `IKeycloakRealmClient` to create and read realms. That matches the docs context: creating and configuring realms, clients and users. `Keycloak.AuthServices.Sdk.Kiota` also exists, but it's the Kiota-generated alternative; the primary admin client is `Sdk`. - Overlap: no open aspire.dev issue or PR mentions `Keycloak.AuthServices`. Open PRs #1737 and #1637 touch only generated Keycloak API data, not `keycloak.mdx`. This change isn't visual. Only the link target changes. ## Third-party links and affiliations Changes one third-party link from `https://www.nuget.org/packages/Keycloak.AuthServices.Sdk.Admin` (nonexistent) to `https://www.nuget.org/packages/Keycloak.AuthServices.Sdk`, published by the community Keycloak.AuthServices project. No affiliation. ## Validation - Before/after NuGet API evidence: 404 → 200, as listed above. I didn't add a unit regression check, because the repo's unit tests run offline and have no NuGet existence check to extend. - `npx vitest run`: 1,119 passed, 1 skipped. - `npx eslint . --max-warnings 0`: clean. - `keycloak.mdx` already has Prettier warnings on `main`; this one-line change doesn't affect them. **🤖 Posted by AspireAgent (AI Agent)** Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Documentation accuracy review [partial]Reviewed head: Phase A: 160 grouped claim entries: 149 verified, two verified with nuance, seven contradicted API-family groups (consolidated into two findings), two historical/narrative snapshot groups. Primary source pins are core Aspire Phase B: independent, source-blind Why partial: representative browser/runtime-site coverage was completed, but the blind tester did not execute package-install commands or compile/run Aspire applications. This is not a full executable-example/product-behavior certification; no production build was run. The separate exact-base TypeScript declaration compiler control below is not being substituted for the blind phase. Machine-specific absolute paths in the tester's operational appendix are redacted; its substantive findings, evidence, routes, recommendations, and knowledge gaps are otherwise preserved. This is the Project's once-per-PR documentation-stage conversation comment, not a formal approval/request-changes verdict. A partial report consumes this stage; it must not be automatically repeated for a later SHA. Phase A - frozen source/claim verificationReviewed head Historical version discipline: the reviewed data describes 13.6 artifacts, not today's Sources actually read:
The current source Findings: the rendered TypeScript API loses real exported APIs1. Radius's .NET-program overload disappears. The regenerated Radius module retains the The pinned owning source still declares 2. Six provisioning modules narrow inherited capabilities to a derived type, dropping them from their original base handles. For example, CosmosDB's
The pinned proxy generator preserves base-proxy inheritance and emits base-type-specific This is not merely theoretical metadata churn. A focused TypeScript 6.0.3 compiler check of the same four calls against the exact base and head bundles produces: The PR's warning about tolerated Kusto/Network scanner diagnostics is relevant, but the verified losses also affect four other provisioning modules and Radius. Regenerate with a scanner/transform path that preserves the exported receiver/capability contract, or otherwise preserve the complete existing supported surface until that path is fixed. Merely accepting the diagnostic warning is insufficient. Verified and nuanced claim groups; mechanical scope and coverage limitsAll changed JSON files were parsed and compared with the base. Arrays were compared by type/full name, member signature, or capability ID where applicable, so reorderings were not reported as new APIs. After excluding timestamps, source-line movement, package versions, and source-commit-only updates, there are 19 semantic API package/module groups: eight C# package groups and eleven TypeScript module groups. Twelve match their pinned owning sources; the seven contradicted groups are Radius plus the six provisioning modules above. These are grouped API-family verdicts, not an assertion that every generated symbol was independently executed.
Additional grouped checks:
Catalog accounting: 160 grouped claim entries = 122 version claims + 19 semantic API groups + two blog-summary groups + 14 tag-set-preservation groups + one official-icon-policy group + two historical-snapshot groups. Verdicts: 149 verified, two verified with nuance, seven contradicted, two historical/narrative snapshots (not source-verifiable). Generated type/member/parameter repetitions are grouped under their owning API family; no exhaustive runtime execution is implied. Focused validation: the actual exported repository Phase B - independent doc-tester reportDocumentation Test ReportFocus Area: Independent, blind Phase B user-facing testing of microsoft/aspire.dev PR #1737 generated integration, C# API, TypeScript API, two-slash, blog, and repository-statistics data. The actual SummaryCounts below are grouped assertions, not a count of individual page loads. A rendered-example smoke check is not a compilation or execution pass.
Generated-data scope identified with Critical IssuesIssues that make documentation misleading or incorrect. Issue 1: Keycloak Extensions “Applies to” link reaches a nonexistent module-local resourceLocation: What the documentation says:
The
What actually happens:
Evidence:
Expected result: Following the type link should open the actual owning module’s Recommended Action:
WarningsIssues that may confuse readers but aren't strictly incorrect in the changed data, and explicit limits on what was verified. Warning 1: Kind’s existing inheritance display is malformed TypeScriptLocation: interface KindDeployedResource
extends IResource,
IResourceWithParent,
KindClusterResource]],
IResourceWithWaitSupport {
withCrdWait(configure: (obj: CrdWaitOptions) => Promise<void>): KindDeployedResource;
withNamespace(namespace: string): KindDeployedResource;
}The stray Warning 2: Updated blog entries are valid externally but not discoverable in the tested local blog surfaceLocation: Warning 3: Existing TypeScript API counts and duplicate type presentations can confuse readersLocation: TypeScript API index and
Suggestion: Label capabilities, top-level functions, and handle members distinctly, keep the summaries synchronized, and explain or deduplicate handle/enum representations. These are runtime observations on refreshed data, not established new regressions. Warning 4: Local development provenance and live-status service are imperfectLocation: Local pages and browser console.
Suggestion: Treat the verified Git SHA, not the dev footer, as this run’s provenance. These missing auxiliary endpoints did not block gallery/reference rendering. Do not infer a production or PR-specific failure from the lightweight dev environment. Warning 5: Example coverage is rendered smoke testing, not application executionLocation: Warning 6: Aspire CLI examples were not executedLocation: Gallery install snippets and the Keycloak integration page. Warning 7: Link coverage was scoped, not exhaustiveLocation: Tested gallery, API, and integration pages. Passed ChecksContent Accuracy
Code Examples
Links
Exact tested routesAll local routes below used origin
Additional C#/TypeScript picker interactions generated External routes:
Exact commands and resultsCommands were run from:
Browser evaluation inspected rendered DOM only. Batched page navigation used the exact following pattern, with route arrays composed of the API paths listed above: async page => {
const out = [];
for (const path of paths) {
const r = await page.goto("http://localhost:4322" + path);
out.push({
path,
status: r.status(),
title: await page.title(),
text: await page.locator("main").innerText()
});
}
return out;
}Version filtering used actual user-facing labels: await page.getByRole("button", { name: /Versions:/ }).click();
const toggle = async name =>
await page.locator("label").filter({
has: page.getByRole("checkbox", { name, exact: true })
}).click();
await toggle("Select all");
await toggle("13.6.0");
await toggle("13.6.0-preview.1.261001-0242 preview");An initial direct No Runner paths and cleanup handoffInstalled frontend dependencies and the scoped tool cache are deliberately retained for the parent’s independently requested focused validator and cleanup:
Owned dev process tree was the npm-exec/dev command tracked by PowerShell shell ID The newly created git restore --source=HEAD -- src\frontend\.starlight-icons\language-map.json src\frontend\.starlight-icons\material-icons.json src\frontend\.starlight-icons\safelist.json src\frontend\.starlight-icons\version.txtUnknown baseline ignored files were not deleted. Frontend Recommendations
Knowledge gapsKnowledge Gap: TypeScript Kind timeout representationWhat I needed to know: How to construct a valid
Knowledge Gap: What was inferred rather than taughtWhat I needed to know: That stray |
Code/data review: two high-confidence regressionsReviewed all 343 changed files at High1. Radius TypeScript module:67-88 - Preserve the exported .NET-program The new output deletes capability Why it matters: the existing repository API-reference contract test now fails, the TypeScript reference cannot resolve the declared export, and the regenerated bundle no longer accepts Focused local control, using the identical unchanged repository test and dependency environment: The exact-base resolver already reports ambiguity between the two overload routes; this review does not conceal that existing nuance or claim every base diagnostic is clean. The new unresolved-export diagnostic and the test failure are specific to the reviewed head, and the explicit Suggested fix: regenerate or preserve the missing exported overload and its .NET-program receiver expansion, then regenerate the twoslash bundle. Retain the existing contract-test assertion and add a focused overload/receiver assertion so a generator refresh cannot silently drop this capability. 2. CosmosDB TypeScript module:11211-11239 and twoslash base handle:87968 - Do not narrow base capabilities to whichever derived receiver the scanner retained. Confidence: high; exact-base declaration compilation reproduced. For example, Why it matters: this changes both rendered base-handle member references and the TypeScript declarations used by documentation examples. A comparison of the actual base/head capability sets, including the remaining ancestor capabilities, finds 42 lost operations on 16 original handles:
This is not a generic objection to stale output. The unchanged transform associates each capability only with its received target handle, and the unchanged declaration emitter writes those handle capabilities. Narrowed receiver data therefore has a direct, reachable consequence. The pinned owning proxy generator still generates base-proxy inheritance and base-specific The repository already documents that the tolerated scanner defect keeps the first inherited definition. That explains why “generation succeeded” is not a completeness guarantee. The PR-body Kusto/Network warning does not cover the observed losses in the other four modules. Focused compilation with TypeScript 6.0.3, using each ref's full committed declare const view: CassandraViewResourceProxy;
declare const connection: KustoDataConnectionProxy;
declare const infrastructure: AzureResourceInfrastructure;
declare const project: DotnetProjectResource;
view.clearId();
view.clearViewDefinition();
connection.addTo(infrastructure);
project.withContainerImage("example/test:1");Suggested fix: regenerate through a corrected scanner/transform path that preserves the declaring receiver and inherited availability, and regenerate declarations afterward. Add receiver/capability preservation assertions for representative base/derived provisioning types, including a factory-created base type and Kusto Other data checks
Test coverage and limitsUnit/contract: the focused existing API-reference test passes at the exact base and fails at the reviewed head as shown above. The real exported E2E (desktop/tablet/mobile): the exact-head CI run reports success for all six viewport/shard jobs and the frontend build, while frontend validation and the downstream gates fail. The independent browser run and its explicit coverage limitations are in the preceding documentation comment. No local full suite was rerun. Accessibility: no component, markup, style, or interaction implementation changes. This review does not invent a missing-axe finding for version/count metadata; the unchanged website's baseline Keycloak link, Kind display, and counting observations are not attributed to this PR. No new local axe audit was performed. No full local production build, NuGet/API regeneration, executable Aspire integration application, or cloud deployment was performed. No fixes, commits, pushes, formal review verdict, or merge action were made. This conversation comment consumes the Project's once-per-PR code/data-review stage, not a per-SHA rerun. |
David Pine (IEvangelist)
left a comment
David Pine (IEvangelist)
left a comment
There was a problem hiding this comment.
[partial - phase A: 28 of 3,174 changed claim groups evaluated; phase B: sampled browser validation, not exhaustive runtime validation]
Automation: user-approved hourly local documentation PR reviewer for David Pine (@IEvangelist). This is the automation's one combined report for this PR; partial reviews consume its review and will not be automatically repeated.
Inspected head: 3ee148e7542e3c8d9ff4e7a9a87b57cd33cedb9f; target main at 75e3568f1af2c2f5e6a9d114fe4dd953f991c306 (also the comparison merge-base). This is documentation accuracy/user-experience review, not standard code review.
Trusted policy: default-branch doc-pr-reviewer, doc-tester, playwright-cli and relevant Astro instructions at 708ea2758b6ac970a661e34cf72ed1f706e90c30. Native reviewer loading was unavailable, so its trusted file policy was executed directly for doc-pr-reviewer https://github.com/microsoft/aspire.dev/pull/1737. PR-head review policy was not authoritative.
Owning sources actually inspected, read-only at matching target main:
microsoft/aspire/main/9d8eb409082ec68ce74364b5b233cbf135f2c18c: Matching target main pinned read-only; terminal source read, not treated as proof of historic 13.5/13.6 release attribution.CommunityToolkit/Aspire/main/bae4970aa52d8e9afdf0c21c416785e4da551931: Matching target main pinned via GitHub contents API; exact K6 enum and WithScript signature verified.
Claim counts: 343 changed data files (125 modified, 218 version-renamed); 3,174 introduced/modified scalar or declaration-line groups: 28 verified, 0 verified-with-nuance, 0 contradicted, 0 unverifiable, 0 narrative, 3,146 not evaluated. Array records were compared by stable identities, and renamed files were compared to their previous filenames. This is a leaf/declaration-group denominator, not a count of API symbols; repeated projections remain distinct. All complete old/new JSON was parsed, full changed diffs are preserved, and untouched carried declarations are not blanket re-certified. Deleted-only fields remain in the full diff inventory rather than being counted as new positive leaf assertions.
Independent Phase B: C#/TypeScript k6 search, WithScript and enum pages; representative provisioning package/type/member/Markdown; hub/browse and both added blog destinations; filtered integration gallery and 375px views. 0 critical issues observed, 3 warnings: missing rendered TypeScript explanations, long C# heading overflow, and an unattributed page-action reload requirement. Literal runtime/compilation and clipboard payload verification remain incomplete.
Warning attribution: The changed TypeScript module already contains the new withScript remarks, parameter descriptions and K6SummaryMode.memberDocs. The source-blind tester accurately reports that the rendered TypeScript pages omit those explanations; this is not evidence that the author omitted them from this data refresh. Likewise, the tester does not establish that the generated-data changes introduced shared heading overflow or page-action initialization behavior. These affected-route observations are preserved for follow-up, not falsely attributed as source-backed PR regressions or attached to unrelated renderer files.
Why this is partial, not approval
The 343-file refresh changes versioned API/package metadata across core Aspire, Community Toolkit and Azure provisioning projections, plus blog and repository snapshots. Exhaustive owning-source verification of all 3,174 changed groups and independent literal runtime validation could not finish in this run. Specifically, exact historic package-version/sourceCommit provenance, unexamined Azure SDK shapes, most generated API projections, the release-attributed blog descriptions and historic numeric snapshots remain uncleared. The changed docs' own sourceCommit metadata is not accepted as proof of itself, and current main behavior is not used to invent evidence of an earlier release.
The source checks below only establish the bounded K6 declarations against recorded owning source. They do not prove all published package versions, that every generated language binding is runnable, or that unexamined claims are correct. Browser results are sampled and preserved independently in full below. No full site build, upstream workflow, package-data generator, global tool upgrade, certificate-store action, cloud provisioning or remote branch mutation was used to manufacture a pass. Incomplete required checks require this labeled partial COMMENT, never approval.
Phase A - frozen claim verification
28 verified changed K6 declaration/enum groups and exact owning-source evidence
The changed C# WithScript declaration matches K6BuilderExtensions.cs:98-103:
public static IResourceBuilder<K6Resource> WithScript(
this IResourceBuilder<K6Resource> builder,
string scriptPath,
int? virtualUsers = null,
string? duration = null,
K6SummaryMode? summaryMode = null)The enum declarations and member descriptions match K6SummaryMode.cs:1-20: public CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode with Compact=0, Full=1, Disabled=2 and their exact concise/full/disabled descriptions. Enum identity/membership/docs are confirmed; TypeScript runtime marshaling and all consumer signatures are not.
| Claim | Changed documentation leaf/declaration | Exact new value |
|---|---|---|
| C001828 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=Aspire.Hosting.K6BuilderExtensions/members/name=WithScript/signature |
"public static IResourceBuilder<K6Resource> K6BuilderExtensions.WithScript(this IResourceBuilder<K6Resource> builder, string scriptPath, int? virtualUsers = null, string? duration = null, K6SummaryMode? summaryMode = null)" |
| C001867 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/name |
"K6SummaryMode" |
| C001868 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/fullName |
"CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode" |
| C001869 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/namespace |
"CommunityToolkit.Aspire.Hosting.k6" |
| C001870 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/kind |
"enum" |
| C001871 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/accessibility |
"public" |
| C001874 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Compact/name |
"Compact" |
| C001875 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Compact/value |
0 |
| C001876 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Compact/description |
"Default mode. Shows the most relevant test results in a concise format." |
| C001877 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Full/name |
"Full" |
| C001878 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Full/value |
1 |
| C001879 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Full/description |
"Shows all available information." |
| C001880 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Disabled/name |
"Disabled" |
| C001881 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Disabled/value |
2 |
| C001882 | src/frontend/src/data/pkgs/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/types/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/enumMembers/name=Disabled/description |
"Completely disables the summary generation." |
| C003075 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/name |
"K6SummaryMode" |
| C003076 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/fullName |
"CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode" |
| C003077 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/kind |
"enum" |
| C003078 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/description |
"Define how detailed the end-of-test summary should be." |
| C003079 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/members/0 |
"Compact" |
| C003080 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/members/1 |
"Full" |
| C003081 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/members/2 |
"Disabled" |
| C003082 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Compact/name |
"Compact" |
| C003083 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Compact/description |
"Default mode. Shows the most relevant test results in a concise format." |
| C003084 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Full/name |
"Full" |
| C003085 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Full/description |
"Shows all available information." |
| C003086 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Disabled/name |
"Disabled" |
| C003087 | src/frontend/src/data/ts-modules/CommunityToolkit.Aspire.Hosting.k6.13.6.0.json/enumTypes/fullName=CommunityToolkit.Aspire.Hosting.k6.K6SummaryMode/memberDocs/name=Disabled/description |
"Completely disables the summary generation." |
The pinned core TerminalResourceBuilderExtensions.cs:21-79 was also read and confirms current interactive-terminal support, but does not by itself establish the newly added blog's historical 13.5/13.6 release attribution. Those blog claims remain not evaluated. No source contradiction or unverifiable finding is invented from unexamined records; there is therefore no Phase A inline finding.
Version placeholders: exact generated API package filenames and metadata are intentionally version-pinned; they are not generic current-version installation snippets. Historical release blog descriptions are likewise not current-copy/paste version output. No automatic placeholder replacement is requested for these fixed-version surfaces.
Phase B - independent, source-blind doc-tester report (complete)
Documentation Test Report
Focus Area: Independent Phase B, source-blind, bounded user walkthrough of changed generated API reference and metadata surfaces in microsoft/aspire.dev PR #1737.
Date: 2026-11-02, approximately 22:23–22:30 UTC.
Tester: doc-tester agent, using the trusted default-branch doc-tester/playwright-cli/doc-pr-reviewer policies at 708ea2758b6ac970a661e34cf72ed1f706e90c30.
PR: #1737
Served checkout HEAD: 3ee148e7542e3c8d9ff4e7a9a87b57cd33cedb9f, verified with git rev-parse HEAD before and after the walkthrough.
Local URL: http://localhost:4321/
Environment: Existing reviewer-owned root bun run dev server; supplied Astro PID 44496. This tester did not start, stop, restart, or otherwise manage it. Edge through the tracked .playwright\cli.config.json, named browser session pr1737.
Summary
Critical issues: 0 observed. Warnings: 3 (two documentation/presentation warnings and one local navigation observation not established as a PR regression).
| Category | Passed observations | Failed observations | Warnings / applicability |
|---|---|---|---|
| Content presentation | Changed C# and TypeScript k6 signatures and enum values are discoverable; provisioning package displays the refreshed preview version; changed metadata cards render | No demonstrated product-behavior contradiction | W1: TypeScript explanatory gap |
| Code examples | Signature and example text can be read in the browser | Not executed; no compilation/runtime verdict | Missing standalone prerequisites and explicit shared-machine safety boundary |
| CLI commands | None applicable to this bounded generated-reference walkthrough | Not executed | Installation commands on gallery cards were inspected, not run |
| Links and search | C# and TypeScript k6 searches; TypeScript version exclusion/restoration; C# enum and provisioning member links; provisioning Markdown; both added blog destinations | No broken sampled content target | W3: Open menu required a full reload after internal navigation |
| Accessibility and responsive UI | Named searchboxes, headings, menu button, enum values exposed in snapshots; TypeScript enum and filtered integration gallery fit a 375px document width | C# methods page overflows the 375px viewport | W2; this is not a full accessibility audit |
These are sampled observations, not an assertion that all 343 changed data files, generated APIs, or runtime claims were tested. Phase A output, product source, SDK definitions, and authored tests were not read. No behavior was inferred from implementation.
Routes and Sections Exercised
All local routes below use http://localhost:4321.
/reference/— initial requested navigation entry returned the site's “404 / Not found” / “Wrong route?” page. Its public footer's Reference link led successfully to/reference/overview/. The bare route was not supplied by a changed document and is not reported as a PR defect./reference/overview/— public Search C# APIs and Search TypeScript APIs navigation./reference/api/csharp/and?q=k6— searchable API index, k6 v13.6.0 discovery, enum and method search results; Versions control showed 14/14 selected./reference/api/csharp/communitytoolkit.aspire.hosting.k6/k6builderextensions/methods/#withscript-iresourcebuilder-k6resource-string-int-string-k6summarymode— WithScript signature, nullable optional parameters, summaryMode link, parameter descriptions, new scenario-precedence remarks, example, copy controls, mobile presentation. The fragment exists./reference/api/csharp/communitytoolkit.aspire.hosting.k6/k6summarymode/— net10.0 / v13.6.0, enum members and their descriptions./reference/api/typescript/and?q=k6— k6 search returned six entries. Excluding version 13.6.0 produced zero results / “No matching API entries”; selecting it again restored six entries and the query-only URL. The filter generated its ownversions=URL./reference/api/typescript/communitytoolkit.aspire.hosting.k6/withscript/— signature, optional parameters, return type, Applies to link./reference/api/typescript/communitytoolkit.aspire.hosting.k6/k6summarymode/— enum declaration / Values, desktop and 375×812; mobile Menu opened navigation./reference/api/csharp/aspire.hosting.azure.provisioning/— refreshed v13.6.0-preview.1.26479.8, namespace expansion, two discoverable types./reference/api/csharp/aspire.hosting.azure.provisioning/bicepvalueproxy/— representative provisioning type, member table, ATS export metadata./reference/api/csharp/aspire.hosting.azure.provisioning/bicepvalueproxy/methods/#assignto-bicepvalue-t— member signature, target parameter, explanation, “Ignored by ATS” reason; fragment verified present. Other methods on that same page were visible but not runtime-tested./reference/api/csharp/aspire.hosting.azure.provisioning/bicepvalueproxy/methods.md— followed public View in Markdown, selected its new tab, read actual plain Markdown containing AssignTo/Convert/Create signatures, parameters, and ATS reasons./hub/— directory navigation and From the blog section. This section still features curated older posts; no promise that it is the latest-post feed was established./hub/browse/— the two added blog cards, dates, descriptions, destination links, and loaded images./hub/browse/?q=k6— two relevant documentation cards, with language labels and site-relative trailing-slash destinations./integrations/→/integrations/gallery/→/integrations/gallery/?search=k6— public metadata consumer: filtered to one package, v13.6.0, 70k rounded downloads, loaded package icon, documentation and language links, install-command copy affordance. At 375×812 the document width was 375px.- External blog destinations, read only:
https://devblogs.microsoft.com/aspire/aspire-terminal-support/— heading “Bringing rich terminal experiences to Aspire,” October 1st, 2026.https://devblogs.microsoft.com/aspire/whats-new-aspire-13-6/— heading “Aspire 13.6: Your dashboard gets memory,” September 29th, 2026.
No unrelated tutorial was walked through. Source links visible in generated reference pages were not followed.
Critical Issues
None demonstrated in the sampled UI. In particular, rendering an API declaration does not establish that the package implements it or that a copied AppHost works.
Warnings
Warning 1: New TypeScript summary-mode surface omits the explanations needed to choose and use it
Location: /reference/api/typescript/communitytoolkit.aspire.hosting.k6/withscript/, Signature / Parameters; /reference/api/typescript/communitytoolkit.aspire.hosting.k6/k6summarymode/, Values.
Type: Content / teaching effectiveness.
What the documentation says:
withScript(scriptPath: string, virtualUsers?: number, duration?: string, summaryMode?: K6SummaryMode): K6Resource
The Parameters section lists names, types, and optional markers. The new enum's Values section shows only Compact 0, Full 1, Disabled 2; it has no descriptions or default-mode explanation.
Observed user gap: As a TypeScript reader, I can discover the new argument but cannot learn from these pages how omitted virtualUsers/duration interact with script scenarios, or which summary mode is the default. I would have to infer from names, prior knowledge, or leave the TypeScript reference. By contrast, the tested C# pages explicitly say “Leave them null when the script defines its own scenarios or executors” and describe Compact as “Default mode. Shows the most relevant test results in a concise format.”
Evidence: typescript-withscript.yml, typescript-summarymode.yml, typescript-summarymode-mobile.png, csharp-k6-methods.yml, csharp-k6-summarymode.yml.
Recommendation: Carry the parameter/enum explanations and scenario-precedence remarks into the TypeScript reference, or provide an explicit cross-reference to the explanatory documentation. Include a documented TypeScript usage example rather than requiring users to translate the C# example. This is a discoverability/teaching gap, not a proven incorrect TypeScript signature.
Warning 2: Changed C# WithScript heading is clipped at 375px
Location: /reference/api/csharp/communitytoolkit.aspire.hosting.k6/k6builderextensions/methods/, WithScript member heading.
Type: Responsive presentation.
Reproduction: Open the methods route with the WithScript fragment, resize to 375×812, and scroll to the WithScript member.
Visible heading:
WithScript(IResourceBuilder<K6Resource>, string, int?, string?, K6SummaryMode?)
Observed result: The heading extends past the card's right boundary instead of remaining readable within the mobile viewport. Browser measurements at horizontal scroll position zero were innerWidth=375, document.documentElement.scrollWidth=521. The WithScript heading's code element extended to approximately x=415px. Another method heading on the same page also overflowed; the total 521px document width is not attributed solely to the added parameter.
Evidence: csharp-withscript-mobile-heading.png, csharp-withscript-mobile.png, csharp-withscript-mobile.yml.
Recommendation: Make long member headings wrap/break safely or provide a contained, operable horizontal scroller without widening the whole page. Retest the longer changed signature at 375px. No claim is made that this PR introduced the shared renderer behavior.
Warning 3: Open menu did not respond after internal API navigation until reload
Location: Provisioning package → BicepValueProxy → AssignTo methods route, page-level Open button.
Type: Local browser/navigation observation; regression attribution unestablished.
Reproduction: Follow the namespace/type/member links, then click Open on the member page.
Observed result: After the click, the Markdown link remained hidden and absent from the accessibility snapshot. Repeating a snapshot did not reveal the menu. A full browser reload on the same URL followed by clicking Open exposed View in Markdown; following that link then worked.
Evidence: provisioning-open-menu.yml, provisioning-open-menu-ready.yml, provisioning-open-click.png, provisioning-open-after-reload.yml, markdown-provisioning-content.yml.
Recommendation: Recheck the page action initialization after client-side navigation. This is an affected-route usability observation, not evidence that the generated-data changes caused a regression; do not treat it alone as a blocking PR finding.
Passed Checks
- Public reference navigation reached both generated API browsers.
- C# search discovered K6SummaryMode and the changed WithScript member; its result linked to an existing fragment.
- Rendered C# WithScript shows
int? virtualUsers = null,string? duration = null, andK6SummaryMode? summaryMode = null, rather than the previous fixed-default style. - The new C# remarks visibly explain
--vus,--duration,options.scenarios, and leaving values null. The duration parameter presents30sas an example, not a default. - C# K6SummaryMode displays Compact=0, Full=1, Disabled=2, with descriptions; TypeScript displays the same named numeric values.
- TypeScript search found the new enum and changed member. Version-label interaction correctly excluded and restored the k6 entries. An initial direct checkbox automation attempt targeted a visually hidden input and timed out; clicking its visible label worked. This selector failure is not a documentation defect.
- TypeScript withScript lists optional virtualUsers/duration/summaryMode, returns K6Resource, and exposes the Applies to navigation.
- The representative provisioning package displays the refreshed preview version. Its BicepValueProxy member link resolves to AssignTo, with a matching fragment, target parameter, and explanatory ATS reason.
- Public Markdown view returns substantive reference Markdown, not a 404, after the menu is made available by reload.
- Added blog cards render both new titles, descriptions, and dates; both changed images loaded successfully, and both destination articles opened with matching titles/dates.
- Filtered integration gallery shows CommunityToolkit.Aspire.Hosting.k6 v13.6.0; its versioned icon loaded. The displayed install command is
aspire add communitytoolkit-k6. It was not executed. - The TypeScript enum and filtered gallery have 375px document width at 375px viewport width. The enum screenshot shows legible code, a named Menu control, and reachable page actions.
Browser / Environment Observations
- Local console logs repeatedly include
/api/live/404 and[live-status] Live API not found (404); live updates disabled until reload.Hub/gallery navigation also logged/api/live/stream/404. Content routes continued to work. These are local-server observations, not identified changed-content defects. Supporting logs are preserved under.playwright-cli. - The initial
/reference/navigation logged its expected-for-this-attempt 404; the real public Reference link is/reference/overview/. - The footer advertises
SHA 75e3568linking to75e3568f1af2c2f5e6a9d114fe4dd953f991c306, while the supplied serving checkout was independently verified at the requested PR head. Changed k6 v13.6.0, new enum, new blog cards, and provisioning preview metadata were visibly served. The footer stamp was not used as evidence of the PR checkout; its origin was not investigated because doing so would exceed the allowed inputs. - Code-copy and Copy Markdown buttons were clicked. Browser clipboard read-back was denied with
NotAllowedError: Failed to execute 'readText' on 'Clipboard': Read permission denied.No permissions, browser databases, or trust settings were changed, and no clipboard bypass was attempted. Exact clipboard payload correctness is therefore not certified. The accessible code-copy button names contain the rendered code, but that is not clipboard read-back. - Actual CLI behavior required explicit
gotoaftertab-new; an initially blank tab is a tooling artifact, not a failed article destination.
Knowledge Gaps and Runtime Limitations
Knowledge gap: Turning the reference fragment into a runnable k6 sample
What I needed to know: A complete project/package setup, an API project defining Projects.Api, and contents of scripts/main.js.
What the rendered reference provides: The C# example includes var api = builder.AddProject<Projects.Api>("api");, .WithBindMount("scripts", "/scripts", true), and .WithScript("/scripts/main.js"), but not a standalone API project or script body. The TypeScript page presents declarations rather than a complete runnable app.
Source of knowledge: I recognized these as external prerequisites; I did not invent their contents, translate a sample using prior SDK knowledge, or inspect source to repair the gap.
User impact: These pages work as API lookup material, not as self-contained executable tutorials.
Recommendation: Link to a complete supported example/setup when presenting executable-looking remarks, and document the new summary-mode/scenario behavior for TypeScript readers.
Runtime and scope applicability
- No Aspire or dotnet command, including diagnostics/version checks, was run. No project, package installation, restore, build, container, AppHost, cloud resource, or certificate operation was attempted.
- Running the displayed container-backed AppHost would cross the assignment's explicit shared-machine/certificate safety boundary. A compatible runtime/package setup was not established. Therefore k6 container startup, script execution, scenario precedence, summary output, browser extension behavior, provisioning behavior, and actual API compatibility remain unverified.
- Only the requested existing docs server was used. No full build or generation/update script was run, and no repository file was edited.
- The 197 package data files, 141 TypeScript modules, and remaining changed generated declarations were not exhaustively browsed. No assertion-coverage percentage is claimed. Twoslash ambient behavior and language-service correctness were not tested from a declaration page.
github-stats.jsonsource accuracy is outside this phase. No visibly affected star-count consumer was identified in the sampled reference/hub/gallery surfaces. Samples newline-only data changes were not treated as a new runtime walkthrough.- Link validation covers the named routes, fragments, and card destinations actually followed; it is not an exhaustive crawl or a guarantee about every internal/external link.
- Accessibility checks were limited to actual snapshots, named controls/headings, mobile navigation, and visual inspection. No assistive-technology compatibility or complete keyboard/audit certification is claimed.
Recommendations
- Preserve TypeScript explanatory content for new k6 options and enum values; do not require guessing from declarations.
- Retest long generated C# member headings on 375px screens.
- Independently reproduce page-action initialization after internal navigation, distinguishing existing local-renderer behavior from this PR's data refresh.
- In an explicitly approved isolated runtime environment, follow a complete documented k6 sample literally to verify default/scenario/summary behavior. This report does not substitute for that runtime test or Phase A claim verification.
- Preserve this independent report verbatim when combining phases; do not convert the sampled UI successes into exhaustive generated-API verification.
Evidence and Cleanup
All tester-created snapshots, screenshots, and browser console logs are in this report's directory or its .playwright-cli child directory. Named evidence files above are relative to this directory.
Only browser session pr1737 was closed, which closed this tester's tabs. The CLI's post-close delete-data returned “Browser 'pr1737' is not open”; the known, tester-created browser-profile directory was then removed directly after browser closure. No test workspaces were created. Report, snapshots, screenshots, and console logs are intentionally preserved for the parent.
The reviewer-owned docs server and checkout remain running/unchanged for the parent. No source checkout, primary E:\GitHub copy, shared Aspire state, browser trust store, or other app session was touched. No GitHub review/comment/claim/push/merge or cross-session message was made.
docs-pr-reviewer report — [partial — phase A: key claims evaluated; phase B: not run (docs site was not served in this automated run)]Recommendation: needs human Source used: n/a — generated data (cites microsoft/aspire#20443, which is CLOSED/unmerged) Phase A — claims
Phase B — doc-testerNot run; rendering of the changed pages is not browser-checked. 🤖 Posted by aspire.dev - squad (AI Agent) |
## Summary Fixes #1960. The Integration Data Updater has failed since #1895 because `generate-package-json.ps1` reads optional `apiReference` metadata directly under `Set-StrictMode -Version Latest`. The catalog omits the property for 209 of 210 entries, so generation aborts before processing packages. - Check property existence before reading `apiReference`. - Keep omitted and explicit `true` entries; exclude explicit `false`. - Add an executable PowerShell regression test that evaluates the production predicate against omitted/false/true fixtures and the real catalog. - Run that regression in the Tools Tests workflow. Failure evidence: [first affected run](https://github.com/microsoft/aspire.dev/actions/runs/38809447050), [latest inspected failure](https://github.com/microsoft/aspire.dev/actions/runs/40403823946/job/121856319285). Related prior repairs: #1813 and #1899; stale rolling updater PR: #1737. ## Validation - PowerShell regression test: passed; real catalog result was `209 included, 1 excluded`. - `PackageJsonGenerator.Tests`: 41/41 passed. - `AtsJsonGenerator.Tests`: 37/37 passed. - `update-integrations.vitest.test.ts`: 50/50 passed. - PowerShell parser for `update-integration-data.ps1`: 0 errors. - `actionlint .github/workflows/tools-tests.yml`: passed. - `git diff --check`: passed. ## Limitations A complete updater `workflow_dispatch` was not run because `main` still contains the failing predicate; running it before this fix lands would reproduce the known failure and cannot validate the branch change. The PR's Tools Tests exercise the exact production predicate, and the next post-merge manual/scheduled updater run should provide end-to-end confirmation. **🤖 Posted by Repository agent (AI Agent)** --------- Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
3ee148e to
35db3f2
Compare
aspire-repo-bot
Bot
changed the title
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
9e43215 to
7201aca
Compare
Resolve the latest Aspire.Hosting API data dynamically and allow known prerelease-only/experimental APIs missing from regenerated data. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The updater preferred stable 9.7.2 over the newer 13.6.2-beta.959 that the docs target. Add a prerelease-preferred package list and restore the beta data. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Automated integration data update — 11/4/26
Generated deterministically by
src/frontend/scripts/update-integration-data.ps1(no agent inference).This PR is approved and squash-merged automatically once
ci-gatepasses, as configured in.github/policies/auto-merge.yml. Remove the:octocat: auto-mergelabel to hold it for manual review.What's updated
src/frontend/src/data/aspire-integrations.json— latest package informationsrc/frontend/src/data/integration-docs.json— documentation mappings, when packages are removedsrc/frontend/src/data/github-stats.json— repository statisticssrc/frontend/src/data/github-contributors.json— Contributors page avatars, when changedsrc/frontend/src/data/samples.json— sample metadata, when changedsrc/frontend/src/data/aspire-blog-posts.json— complete official Aspire blog metadata, when changedsrc/frontend/src/data/schemas/— Aspire CLI config schemas, when microsoft/aspire ships a new releasesrc/frontend/src/assets/samples/— sample thumbnails, when changedAPI reference regeneration
The C# and TypeScript API reference data and twoslash bundle were regenerated for version changes or to retry previously failed packages:
Aspire.Azure.AI.Inference13.6.0-preview.1.26478.8→13.6.4-preview.1.26523.11Aspire.Azure.AI.OpenAI13.6.0-preview.1.26478.8→13.6.4-preview.1.26523.11Aspire.Azure.Data.Tables13.6.0→13.6.4Aspire.Azure.Messaging.EventHubs13.6.0→13.6.4Aspire.Azure.Messaging.ServiceBus13.6.0→13.6.4Aspire.Azure.Messaging.WebPubSub13.6.0→13.6.4Aspire.Azure.Npgsql13.6.0→13.6.4Aspire.Azure.Npgsql.EntityFrameworkCore.PostgreSQL13.6.0→13.6.4Aspire.Azure.Search.Documents13.6.0→13.6.4Aspire.Azure.Security.KeyVault13.6.0→13.6.4src/frontend/src/data/pkgs/**src/frontend/src/data/ts-modules/**src/frontend/src/data/twoslash/aspire.d.tsGenerator summary:
generate-package-json.ps1→pkgs/): Success: 201 | Failed: 3 | Skipped: 7update:ts-api→ts-modules/): 140 succeeded, 0 failed, 6 skippedtwoslash/aspire.d.ts): succeededAspire.Hosting.Azure.Provisioning.Generators, Aspire.Hosting.CodeGeneration.Go, Aspire.Hosting.CodeGeneration.Java, Aspire.Hosting.CodeGeneration.Python, Aspire.Hosting.CodeGeneration.Rust, Aspire.Hosting.CodeGeneration.TypeScript, Aspire.Hosting.Integration.AnalyzersAspire.Hosting.AgentFramework.DevUI, Aspire.Hosting.DocumentDB, Aspire.Hosting.Elasticsearch, CommunityToolkit.Aspire.Hosting.Azure.Dapr, CommunityToolkit.Aspire.Hosting.Azure.Dapr.Redis, CommunityToolkit.Aspire.Hosting.DaprThese packages failed to generate. Their last-good API data is retained when available; new packages have no API reference until generation succeeds. Exact versions and reasons are saved in
api-generation-failures.jsonand the Integration Data Updater: API generation failures issue.C# CommunityToolkit.Aspire.Hosting.Chroma@17.0.0-beta.994: error NU1102: Unable to find package Aspire.Hosting with version (>= 17.0.0-preview.1.26552.6) /home/runner/work/aspire.dev/aspire.dev/src/tools/PackageJsonGenerator/.package-json-generator-work/restore-ef327acafa6f4bfca8db0e2498f686c0/Restore.csproj : error NU1102: - Found 66 version(s) in source...C# CommunityToolkit.Aspire.Hosting.Keycloak.Extensions@17.0.0-beta.994: error NU1102: Unable to find package Aspire.Hosting with version (>= 17.0.0-preview.1.26552.6) /home/runner/work/aspire.dev/aspire.dev/src/tools/PackageJsonGenerator/.package-json-generator-work/restore-8460f063038d4996adf0b7293102931c/Restore.csproj : error NU1102: - Found 66 version(s) in source...C# CommunityToolkit.Aspire.Hosting.Kind@17.0.0-beta.994: error NU1102: Unable to find package Aspire.Hosting with version (>= 17.0.0-preview.1.26552.6) /home/runner/work/aspire.dev/aspire.dev/src/tools/PackageJsonGenerator/.package-json-generator-work/restore-6d1c8ae042a141838b4d23e737ffbca6/Restore.csproj : error NU1102: - Found 66 version(s) in source...The Aspire CLI reported known duplicate inherited-capability diagnostics for the packages below. Their TypeScript modules were generated anyway, so the APIs named in these diagnostics may be incomplete until the CLI includes the scanner fix from microsoft/aspire#20443. Remove the
:octocat: auto-mergelabel to review these modules before this PR merges.Aspire.Hosting.Azure.Provisioning.KustoAspire.Hosting.Azure.Provisioning.NetworkTolerated diagnostics
Aspire.Hosting.Azure.Provisioning.Kusto: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated/KustoDataConnectionProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoCosmosDBDataConnectionProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoEventGridDataConnectionProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Kusto: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated/KustoDataConnectionProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoCosmosDBDataConnectionProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoEventHubDataConnectionProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Kusto: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated/KustoDataConnectionProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoCosmosDBDataConnectionProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoIotHubDataConnectionProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Kusto: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated/KustoDatabaseProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoDatabaseProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoReadOnlyFollowingDatabaseProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Kusto: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated/KustoDatabaseProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoDatabaseProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Kusto.Generated.KustoReadWriteDatabaseProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Network: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Network.Generated/BaseAdminRuleProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Network.Generated.BaseAdminRuleProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Network.Generated.NetworkAdminRuleProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Aspire.Hosting.Azure.Provisioning.Network: Duplicate capability 'Aspire.Hosting.Azure.Provisioning.Network.Generated/BaseAdminRuleProxy.addTo': defined at 'Aspire.Hosting.Azure.Provisioning.Network.Generated.BaseAdminRuleProxy.AddTo' and 'Aspire.Hosting.Azure.Provisioning.Network.Generated.NetworkDefaultAdminRuleProxy.AddTo'. Remove [AspireExport] from one of them or use different capability IDs.Manual review checklist
pkgs/andts-modules/files match the version changessrc/frontend/src/data/twoslash/aspire.d.tsis included in the diff