Update Spectre.Console to latest version (blocked by hyperlink rendering change)

[joperezr]

Summary

Spectre.Console 0.54.1-alpha.0.37 introduced a behavioral change in how [link=url] markup renders ANSI hyperlink escape sequences (OSC 8). This broke the ConsoleActivityLoggerTests.WriteSummary_WithMarkdownLinkInPipelineSummary_RendersClickableLink test, which verifies that markdown links in pipeline summary output are converted to clickable ANSI hyperlinks.

The update was attempted in #14549 and reverted back to 0.52.1-preview.0.5.

What broke

The test at tests/Aspire.Cli.Tests/Utils/ConsoleActivityLoggerTests.cs:46 creates a Spectre.Console instance with AnsiSupport.Yes and ColorSystem.TrueColor, renders a pipeline summary containing a markdown link, and verifies the output contains an ANSI OSC 8 hyperlink escape sequence:

string hyperlinkPattern =
    $@"\u001b\]8;[^;]*;{expectedUrl}\u001b\\.*link.*\u001b\]8;;\u001b\\";
Assert.Matches(hyperlinkPattern, result);

With Spectre.Console 0.52.1-preview.0.5, the [link=url]text[/] markup correctly emits ANSI OSC 8 sequences (\u001b]8;...). With 0.54.1-alpha.0.37, the output no longer contains these escape sequences — the test value showed only separator dashes ("--------------------------------------------------") instead of the expected hyperlink markup.

How it works

1. MarkdownToSpectreConverter.ConvertLinks() (src/Aspire.Cli/Utils/MarkdownToSpectreConverter.cs:199) converts markdown [text](url) to Spectre markup [cyan][link=$2]$1[/][/]
2. ConsoleActivityLogger.FormatPipelineSummaryKvp() (src/Aspire.Cli/Utils/ConsoleActivityLogger.cs:314) uses this converter to format pipeline summary key-value pairs
3. Spectre.Console is expected to render the [link=url] markup as ANSI OSC 8 hyperlinks when the console supports it

What needs to happen

To upgrade Spectre.Console:

1. Investigate the rendering change: Determine if Spectre.Console 0.54.x changed how [link=url] is rendered (different escape format, new API, or removed feature)
2. Update MarkdownToSpectreConverter: If the link markup syntax changed, update ConvertLinks() to use the new syntax
3. Update the test: Adjust the regex pattern in ConsoleActivityLoggerTests to match the new escape sequence format, or update the test approach if links are rendered differently
4. Verify all Spectre-dependent functionality: The CLI uses Spectre.Console extensively for tables, progress bars, markup rendering, and interactive prompts — verify these still work correctly

Files involved

• src/Aspire.Cli/Utils/MarkdownToSpectreConverter.cs — link conversion logic
• src/Aspire.Cli/Utils/ConsoleActivityLogger.cs — pipeline summary rendering
• tests/Aspire.Cli.Tests/Utils/ConsoleActivityLoggerTests.cs — the failing test
• Directory.Packages.props — Spectre.Console version (currently 0.52.1-preview.0.5)

Current version

• Pinned at: 0.52.1-preview.0.5
• Target: 0.54.1-alpha.0.37 or latest pre-release at time of upgrade

References

• PR that discovered this: Update external NuGet dependencies to latest versions #14549
• Spectre.Console repo: https://github.com/spectreconsole/spectre.console

[patriksvensson]

@joperezr All our (Spectre.Console) link tests pass, so curious about this. I made a small console application with the latest version, and everything seems to be fine.

Do you, by any chance, have a minimal reproducible example for this?
I see that you don't close the link tag properly. Maybe this is what causes the problem?

[patriksvensson]

@joperezr Ah, nevermind, that is markdown, not markup.

A reproducable example would be great though. I'll take a look at this when I have some spare time.

[patriksvensson]

@joperezr I tried to reproduce this, but I was unable to.

Upgrading to version 0.54.1-alpha.0.37 (and also the later 0.54.1-alpha.0.49) produces the following result that both passes the test and looks like it should to me:

------------------------------------------------------------
^[38;5;2m✓ 0 steps succeeded^[0m • Total time: 1.82ms
^[38;5;2m✓ PIPELINE SUCCEEDED^[0m

  ^[38;5;12m☁️ Target^[0m: Azure
  ^[38;5;12m📦 Resource Group^[0m: VNetTest5 ^]8;id=885487190;https://portal.azure.com/#/resource/subscriptions/sub-id/resourceGroups/VNetTest5/overview^\^[38;5;14mlink^[0m^]8;;^\
  ^[38;5;12m🔑 Subscription^[0m: sub-id
  ^[38;5;12m🌐 Location^[0m: eastus
------------------------------------------------------------

(Note, I replaced \x1B with ^ in the code block to make it easier to read)

[JamesNK]

I believe I've fixed this. The problem was a new default enricher that detected GitHub CI environment and then forced text links. That makes sense when writing to file output in GitHub, but that's not what we want in this test, which is to pretend we're a real terminal.

This environment detection is why the test passes locally but fails when run in CI.

Fix: Enrichment = new ProfileEnrichment { UseDefaultEnrichers = false }