Repository navigation
Merge release/13.6 into release/17.0 after 13.6.5 security release - #22365
Closed
Jose Perez Rodriguez (joperezr) wants to merge 7 commits into
Closed
Jose Perez Rodriguez (joperezr) wants to merge 7 commits into
Jose Perez Rodriguez (joperezr) wants to merge 7 commits into
Conversation
## Description
Fix dashboard authentication when an unauthenticated user navigates to a missing route. The router's not-found content previously bypassed `AuthorizeRouteView` and could render the main layout and its UI infrastructure.
Missing routes now enforce the frontend authorization policy before rendering dashboard UI. In browser-token mode, unauthenticated users are redirected to login with the original route preserved as the return URL.
Add defense-in-depth authentication checks before initializing the main layout, dialog provider, interaction provider, and standalone terminal window. Preserve unsecured mode and the release branch's terminal route-change lifecycle.
Targets `release/13.6`.
Fixes # (issue)
### User-facing usage
With browser-token authentication enabled, navigating from the login page to `/this-page-does-not-exist` redirects back to `/login?returnUrl=%2Fthis-page-does-not-exist` instead of rendering the dashboard layout. Authenticated users can still access the not-found page.
### Validation
- Focused dashboard component tests: 106 passed, including browser-token redirects, layouts, interactions, and terminal windows.
- Authenticated and unauthenticated initialization tests cover browser-token and OpenID Connect modes.
- Dashboard integration-test project build: 0 warnings and 0 errors.
- Added a Playwright regression test for navigation from login to a missing route. Compiled but not executed because it is an outerloop test.
- `git diff --check` passed.
### Security considerations
This changes frontend authentication/authorization handling. The route authorization policy remains the primary control; the additional initialization checks reject unauthenticated users in secured modes before starting UI infrastructure. Security review is requested; no threat model or security review has been completed for this change.
## Checklist
- Is this feature complete?
- [x] Yes. Ready to ship.
- [ ] No. Follow-up changes expected.
- Are you including unit tests for the changes and scenario tests if relevant?
- [x] Yes
- [ ] No
- Did you add public API?
- [ ] Yes
- If yes, did you have an API Review for it?
- [ ] Yes
- [ ] No
- Did you add `<remarks />` and `<code />` elements on your triple slash comments?
- [ ] Yes
- [ ] No
- [x] No
- Does the change make any security assumptions or guarantees?
- [x] Yes
- If yes, have you done a threat model and had a security review?
- [ ] Yes
- [x] No
- [ ] No
----
#### AI description (iteration 1)
#### PR Classification
Bug fix: unauthenticated users hitting a missing (not-found) route in the dashboard bypassed authentication, exposing the NotFound page without login enforcement.
#### PR Summary
This PR fixes an authentication bypass where navigating to a non-existent route would skip authorization checks, and adds a defense-in-depth authentication guard across key Blazor components.
- `src/Aspire.Dashboard/Components/R...
## Description Bring the internal 13.6 release branch up to date with public `release/13.6` while preserving its internal-only history. This PR exists only in Azure DevOps; no internal commits or branches were pushed to GitHub. At preparation, `internal/release/13.6` was **5 commits behind and 1 commit ahead** of public `release/13.6`. The Azure DevOps `release/13.6` branch exactly matches the public tip, `6cfe6b409805bb21775623d501aa1475cb9ee25c`; the target tip is `0b6bfe2f538d4eed8a9ae7e11651c09dbbe886b8`. The five incoming public commits contain: - DCP 0.26.6 update. - Shared CLI log-creation helper. - Ambiguous DCP create recovery and configurable timeouts. - TypeScript Bicep parameter-expression fix for enum Azure properties. - .NET servicing dependency updates for Aspire 13.6.5. This is a branch synchronization with no manual code changes or conflict resolutions. Existing tests are carried with the upstream commits; no new API or security guarantees are introduced by the merge itself. No additional dependencies beyond those already in the public branch are introduced. Complete using **Merge (no fast-forward)** to retain both histories, not squash or rebase. **Do not delete `release/13.6`**, which is a shared branch. ### Validation - `git rev-list --left-right --count refs/remotes/InternalFork/internal/release/13.6...refs/remotes/origin/release/13.6` returned `1 5`. - `git merge-tree --write-tree refs/remotes/InternalFork/internal/release/13.6 refs/remotes/origin/release/13.6` passed without conflicts; result tree: `a6e7760090e982bec37daf3ff9c50d3ee6c36016`. - `git diff --check refs/remotes/InternalFork/internal/release/13.6 a6e7760` passed. - Rechecked both remote tips before creating the PR; the public and Azure DevOps source tips match. - Local build and tests were not run for this merge-only synchronization. Internal PR validation is required before completion. Fixes # (issue) ## Checklist - Is this feature complete? - [x] Yes. Ready to ship. - [ ] No. Follow-up changes expected. - Are you including unit tests for the changes and scenario tests if relevant? - [x] Yes - [ ] No - Did you add public API? - [ ] Yes - If yes, did you have an API Review for it? - [ ] Yes - [ ] No - Did you add `<remarks />` and `<code />` elements on your triple slash comments? - [ ] Yes - [ ] No - [x] No - Does the change make any security assumptions or guarantees? - [ ] Yes - If yes, have you done a threat model and had a security review? - [ ] Yes - [ ] No - [x] No
…anner
## Description
Stop `DeprecatedMcpCommandScanner` from unconditionally writing agent configuration paths, configuration content, and scan diagnostics to the shared temporary file `aspire-deprecated-scan.log`.
Remove only the temporary-file diagnostic logging. Preserve the existing structured `ILogger` debug messages, deprecated-command detection, configuration migration prompts, and configuration updates. This is a focused fix for `internal/release/13.6`, not a backport of the broader agent-client selection changes.
No new dependencies.
Fixes # (issue)
### User-facing usage
Running `aspire agent init` continues to detect and offer to update deprecated `aspire mcp start` configurations, without writing the scan diagnostics or configuration content to `aspire-deprecated-scan.log`.
### Validation
- `./restore.sh` — passed.
- `MSBUILDTERMINALLOGGER=false dotnet test --project tests/Aspire.Cli.Tests/Aspire.Cli.Tests.csproj --no-launch-profile -- --filter-class '*.AgentEnvironmentDetectorTests' --filter-class '*.AgentInitCommandTests' --filter-not-trait 'quarantined=true' --filter-not-trait 'outerloop=true'` — passed, 49 tests.
- `git diff --check` — passed.
## Checklist
- Is this feature complete?
- [x] Yes. Ready to ship.
- [ ] No. Follow-up changes expected.
- Are you including unit tests for the changes and scenario tests if relevant?
- [ ] Yes
- [x] No
- Did you add public API?
- [ ] Yes
- If yes, did you have an API Review for it?
- [ ] Yes
- [ ] No
- Did you add `<remarks />` and `<code />` elements on your triple slash comments?
- [ ] Yes
- [ ] No
- [x] No
- Does the change make any security assumptions or guarantees?
- [ ] Yes
- If yes, have you done a threat model and had a security review?
- [ ] Yes
- [ ] No
- [x] No
----
#### AI description (iteration 1)
#### PR Classification
Code cleanup: removal of leftover debug/temporary-file logging code.
#### PR Summary
Removes debug logging statements that wrote diagnostic information to a temporary file in the deprecated MCP command scanner.
- `src/Aspire.Cli/Agents/DeprecatedMcpCommandScanner.cs`: Removed all `File.AppendAllText` debug logging calls to a temp file, keeping only existing `_logger.LogDebug` calls for error handling.
<!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
Preserves explicit dashboard endpoint references and ordinary host-resource tunneling. Normalizes legacy host URLs into endpoint references at the dependency-discovery boundary. ---- #### AI description (iteration 1) #### PR Classification Bug fix / feature refinement: restricts automatic dashboard container tunnelling to only OTLP endpoints instead of all dashboard endpoints. #### PR Summary Adds extensive test coverage validating that dashboard tunnelling only exposes OTLP endpoints automatically while preserving explicit endpoint references and legacy tunnel behavior, along with new dashboard routing tests for authentication/authorization layout behavior. - `DcpExecutorTests.cs`: Adds many new test cases verifying `DashboardTunnelAutomaticallyExposesOnlyOtlpEndpoints` only tunnels OTLP gRPC/HTTP endpoints, not all dashboard endpoints. - `DcpExecutorTests.cs`: Adds tests ensuring explicit references (environment, arguments, expressions, properties, host-url, reference) to non-OTLP dashboard endpoints are preserved and tunneled correctly. - `DcpExecutorTests.cs`: Adds tests for caching behavior, legacy container tunnel mode compatibility, and multi-consumer endpoint accumulation. - `RoutesTests.cs` (new file): Adds tests validating dashboard routing/layout behavior under various authentication states (browser token, OpenID Connect, unsecured, pending authorization) ensuring correct layout and redirect behavior. <!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
…temporary directories
## Description
Prevent automatic MSBuild response files from affecting CLI-generated server/integration builds without changing user-authored builds. SDK command working directories move to `<ASPIRE_HOME>/tmp/sdk/<unique-id>`, with owner-only Unix permissions, local configuration isolation, and cleanup on completion or preparation failure. Normal AppHost caches are unchanged.
### User-facing usage
```bash
aspire sdk generate ./MyIntegration.csproj --language typescript --output ./generated
aspire sdk dump ./MyIntegration.csproj --format json --output capabilities.json
aspire sdk export --language typescript > api.json
```
### Validation
Manual validation to check that the `/tmp` folder was not used, all all projects for in `/tmp/sdk`.
- `./restore.sh` — passed; existing dependency vulnerability warnings were reported.
- Command below — passed, 54 tests, no failures/skips. Includes real SDK commands with adjacent/parent response files.
```bash
MSBUILDTERMINALLOGGER=false dotnet test --project tests/Aspire.Cli.Tests/Aspire.Cli.Tests.csproj \
--no-launch-profile -- --filter-method '*.SdkCommandTests.*' \
--filter-method '*.SdkDumpCommandTests.*' \
--filter-method '*.SdkResponseFileTests.*' \
--filter-method '*.ProcessInvocationOptionsTests.*' \
--filter-method '*.DotNetCliRunnerTests.RestoreAsyncRunsDotnetRestoreCommand' \
--filter-method '*.DotNetCliRunnerTests.BuildAndRestoreAsync_ControlAutomaticResponseFiles' \
--filter-method '*.DotNetCliRunnerTests.BuildAsyncRunsDotnetBuildCommand' \
--filter-method '*.AppHostServerProjectTests.BuildAsync_DisablesAutomaticResponseFiles' \
--filter-method '*.PrebuiltAppHostServerTests.PrepareAsync_WithProjectReferencesAndExplicitChannelButNoOverride_UsesAdditionalSourcesNotRestoreConfigFile' \
--filter-not-trait 'quarantined=true' --filter-not-trait 'outerloop=true'
```
- `git diff --check` — passed.
- Full suite and internal pipelines not run.
### Security considerations
Changes generated-process execution and temp placement. Local configuration keeps caches inside the cleanup boundary. Response suppression applies only to generated builds; explicit response files remain supported. Forced termination/cleanup failure can leave directories; no periodic cleanup. Dedicated security review not performed.
## Checklist
- Is this feature complete?
- [x] Yes. Ready to ship.
- [ ] No. Follow-up changes expected.
- Are you including unit tests for the changes and scenario tests if relevant?
- [x] Yes
- [ ] No
- Did you add public API?
- [ ] Yes
- If yes, did you have an API Review for it?
- [ ] Yes
- [ ] No
- Did you add `<remarks />` and `<code />` elements on your triple slash comments?
- [ ] Yes
- [ ] No
- [x] No
- Does the change make any security assumptions or guarantees?
- [x] Yes
- If yes, have you done a threat model and had a security review?
- [ ] Yes
- [x] No
- [ ] No
…l release branches ## Description Stable source builds from `internal/release/*` currently skip Prepare Installers, unlike `release/*` builds. Include the internal release prefix in the official and unofficial installer-stage conditions so internal servicing builds produce the same WinGet manifests, Homebrew cask, and npm installation validation results. Preserve the existing PR behavior, main/release eligibility, prerelease behavior, and dependency-success requirements. Signing and production-branch recognition already include internal release branches and require no changes. Prepare Installers only generates/validates files and uploads internal build artifacts. It does not submit WinGet manifests, push a Homebrew tap, or publish npm packages. Public publishing remains in the separate, manual release-publish pipeline; this change does not modify it. Fixes # (issue) ### Validation - `git -C 'C:\Users\joperezr\.copilot\session-state\b41fa7f3-1764-4a40-baab-cd20c93df4a7\files\internal-release-installer-fix' diff --check` — passed. - `node 'C:\Users\joperezr\.copilot\session-state\b41fa7f3-1764-4a40-baab-cd20c93df4a7\files\check-installer-gates.cjs' 'C:\Users\joperezr\.copilot\session-state\b41fa7f3-1764-4a40-baab-cd20c93df4a7\files\internal-release-installer-fix'` — passed 168 diagnostic cases using the extracted conditions: branch, channel, reason, and dependency-success combinations. This session-only diagnostic is not an Azure Pipelines integration test. - Official definition 1602 run [3130747](https://dev.azure.com/dnceng/internal/_build/results?buildId=3130747), revision `8f7d36254f531a80f95074b0011de97b2a695c12`, stable CLI override — queued through the ADO pipeline API and currently running. Requested `stagesToSkip: [assemble]` to exclude Assemble + Publish. Initial timeline inspected; no artifacts yet. - Stable installer execution is **unvalidated**: contributor-branch gating still intentionally excludes this personal branch. Verify the installer jobs, logs, and artifacts on `internal/release/13.6` after merge. No public release/publishing run was queued. Unofficial pipeline execution was not run. ## Checklist - Is this feature complete? - [x] Yes. Ready to ship. - [ ] No. Follow-up changes expected. - Are you including unit tests for the changes and scenario tests if relevant? - [ ] Yes - [x] No - Did you add public API? - [ ] Yes - If yes, did you have an API Review for it? - [ ] Yes - [ ] No - Did you add `<remarks />` and `<code />` elements on your triple slash comments? - [ ] Yes - [ ] No - [x] No - Does the change make any security assumptions or guarantees? - [ ] Yes - If yes, have you done a threat model and had a security review? - [ ] Yes - [ ] No - [x] No
[release/13.6] Merge internal/release/13.6 into release/13.6
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 22365Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 22365" |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The tests fail in Release builds without repository-mode setup before exercising response-file isolation, and generator-only changes can skip the regression suite because CI trigger coverage is missing.
2 open issues
1 file not reviewed
src/Aspire.Dashboard/Resources/Routes.Designer.cs: Generated file
What changed in this PR
Merges the 13.6.5 security fixes forward into release/17.0, adapting them to the current dashboard, hosting, and CLI implementations.
Changes:
- Protects dashboard routes and layouts with authentication checks, localized denial messages, and regression tests.
- Limits automatic dashboard tunnelling to telemetry endpoints while preserving explicit endpoint references.
- Isolates SDK working directories and generated builds, removes scanner temporary-file logging, and extends installer publishing conditions to internal release branches.
| File | Description |
|---|---|
| tests/Aspire.Hosting.Tests/ExecutionConfigurationGathererTests.cs | Tests endpoint discovery and legacy URL normalization. |
| tests/Aspire.Hosting.Tests/Dcp/DcpExecutorTests.cs | Tests restricted dashboard tunnels and explicit references. |
| tests/Aspire.Dashboard.Tests/Integration/Playwright/BrowserTokenAuthenticationTests.cs | Tests anonymous navigation and login redirects. |
| tests/Aspire.Dashboard.Components.Tests/Shared/TestNavigationManager.cs | Records navigation options for redirect assertions. |
| tests/Aspire.Dashboard.Components.Tests/RoutesTests.cs | Tests route authorization and layout selection. |
| tests/Aspire.Dashboard.Components.Tests/Pages/TerminalWindowTests.cs | Tests terminal authentication enforcement. |
| tests/Aspire.Dashboard.Components.Tests/Layout/WindowLayoutTests.cs | Tests protected window layout behavior. |
| tests/Aspire.Dashboard.Components.Tests/Layout/MainLayoutTests.cs | Tests rejection of unauthenticated layout initialization. |
| tests/Aspire.Dashboard.Components.Tests/Layout/DashboardDialogProviderTests.cs | Tests dialog provider authentication enforcement. |
| tests/Aspire.Dashboard.Components.Tests/Interactions/InteractionsProviderTests.cs | Tests interaction provider authentication behavior. |
| tests/Aspire.Dashboard.Components.Tests/Controls/DashboardNotAuthorizedTests.cs | Tests localized denial and safe login redirects. |
| tests/Aspire.Cli.Tests/TestServices/TestAppHostServerProjectFactory.cs | Supports SDK-specific factory calls in tests. |
| tests/Aspire.Cli.Tests/Projects/PrebuiltAppHostServerTests.cs | Checks generated builds disable automatic response files. |
| tests/Aspire.Cli.Tests/Projects/AppHostServerProjectTests.cs | Tests response-file suppression for server builds. |
| tests/Aspire.Cli.Tests/DotNet/ProcessInvocationOptionsTests.cs | Checks cloning of the response-file option. |
| tests/Aspire.Cli.Tests/DotNet/DotNetCliRunnerTests.cs | Tests response-file handling in build and restore. |
| tests/Aspire.Cli.Tests/Commands/SdkDumpCommandTests.cs | Updates expected scanner configuration files. |
| tests/Aspire.Cli.Tests/Commands/SdkCommandTests.cs | Tests SDK directory isolation, permissions, and cleanup. |
| tests/Aspire.Cli.Tests/Commands/Sdk/SdkResponseFileTests.cs | Exercises SDK commands with hostile response files. |
| src/Aspire.Hosting/Dcp/ContainerCreator.cs | Restricts implicit dashboard tunnels to telemetry endpoints. |
| src/Aspire.Hosting/ApplicationModel/ResourceExtensions.cs | Collects endpoint references from unresolved configuration. |
| src/Aspire.Hosting/ApplicationModel/HostUrl.cs | Extracts shared host-port endpoint lookup. |
| src/Aspire.Dashboard/Resources/xlf/Routes.zh-Hant.xlf | Adds pending Traditional Chinese authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.zh-Hans.xlf | Adds pending Simplified Chinese authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.tr.xlf | Adds pending Turkish authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.ru.xlf | Adds pending Russian authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.pt-BR.xlf | Adds pending Brazilian Portuguese authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.pl.xlf | Adds pending Polish authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.ko.xlf | Adds pending Korean authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.ja.xlf | Adds pending Japanese authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.it.xlf | Adds pending Italian authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.fr.xlf | Adds pending French authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.es.xlf | Adds pending Spanish authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.de.xlf | Adds pending German authorization resource. |
| src/Aspire.Dashboard/Resources/xlf/Routes.cs.xlf | Adds pending Czech authorization resource. |
| src/Aspire.Dashboard/Resources/Routes.resx | Defines the authorization-denied message. |
| src/Aspire.Dashboard/Resources/Routes.Designer.cs | Exposes the authorization resource accessor. |
| src/Aspire.Dashboard/Components/Routes.razor.cs | Moves viewport state into code-behind. |
| src/Aspire.Dashboard/Components/Routes.razor | Gates protected layouts and missing routes on authorization. |
| src/Aspire.Dashboard/Components/Pages/TerminalWindow.razor | Uses the protected window layout. |
| src/Aspire.Dashboard/Components/Layout/WindowLayout.razor.cs | Enforces authentication for window layouts. |
| src/Aspire.Dashboard/Components/Layout/WindowLayout.razor | Defines window content and tooltip rendering. |
| src/Aspire.Dashboard/Components/Layout/MainLayout.razor.cs | Checks authentication before initialization. |
| src/Aspire.Dashboard/Components/Layout/DashboardDialogProvider.cs | Checks authentication before subscribing to navigation. |
| src/Aspire.Dashboard/Components/Interactions/InteractionsProvider.cs | Checks authentication before enabling interactions. |
| src/Aspire.Dashboard/Components/Controls/DashboardNotAuthorized.razor.cs | Redirects browser-token users to login. |
| src/Aspire.Dashboard/Components/Controls/DashboardNotAuthorized.razor | Renders localized authorization denial. |
| src/Aspire.Dashboard/Authentication/DashboardAuthenticationState.cs | Centralizes defensive authentication checks. |
| src/Aspire.Cli/Utils/CliPathHelper.cs | Creates isolated, owner-only SDK working directories. |
| src/Aspire.Cli/Projects/PrebuiltAppHostServer.cs | Disables automatic response files for integration builds. |
| src/Aspire.Cli/Projects/DotNetBasedAppHostServerProject.cs | Disables automatic response files for server builds. |
| src/Aspire.Cli/Projects/AppHostServerProject.cs | Keeps temporary SDK server builds within cleanup scope. |
| src/Aspire.Cli/DotNet/DotNetCliRunner.cs | Adds response-file suppression to build and restore. |
| src/Aspire.Cli/Commands/Sdk/SdkGenerateCommand.cs | Uses isolated SDK directories and factory creation. |
| src/Aspire.Cli/Commands/Sdk/SdkExportCommand.cs | Uses isolated SDK directories and factory creation. |
| src/Aspire.Cli/Commands/Sdk/SdkDumpCommand.cs | Isolates both SDK dump execution paths. |
| src/Aspire.Cli/Agents/DeprecatedMcpCommandScanner.cs | Removes temporary-file diagnostic logging. |
| eng/pipelines/azure-pipelines.yml | Includes internal release branches in publishing conditions. |
| eng/pipelines/azure-pipelines-unofficial.yml | Aligns unofficial publishing conditions for internal releases. |
| docs/specs/cli-output-formats.md | Documents SDK working-directory isolation and cleanup. |
Review effort: Balanced
Comment on lines
+34
to
+35
| var repoRoot = AspireRepositoryDetector.DetectRepositoryRoot(AppContext.BaseDirectory); | ||
| Assert.NotNull(repoRoot); |
| var outputPath = Path.Combine(workspace.Path, "output"); | ||
| string[] arguments = commandName switch | ||
| { | ||
| "generate" => ["sdk", "generate", integrationProject, "--language", "typescript", "--output", outputPath], |
This was referenced Nov 17, 2026
Member
Author
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.


Description
Merges
release/13.6forward intorelease/17.0after the 13.6.5 security release so the MSRC fixes also ship in 17.0.Commits brought forward:
A local check confirmed the dashboard not-found auth, OTLP-only tunnelling, and SDK temp-directory isolation fixes are not yet present in
release/17.0. Merge conflicts are expected (e.g. dashboardRoutes.razorhas diverged in 17.0) and need manual resolution.cc Jose Perez Rodriguez (@joperezr)
Checklist
<remarks />and<code />elements on your triple slash comments?