Skip to content

fix: resolve release notes GitHub tag format#4499

Merged
Marc-André Moreau (mamoreau-devolutions) merged 1 commit intomainfrom
fix-release-notes
Mar 18, 2026
Merged

fix: resolve release notes GitHub tag format#4499
Marc-André Moreau (mamoreau-devolutions) merged 1 commit intomainfrom
fix-release-notes

Conversation

@mamoreau-devolutions
Copy link
Contributor

@mamoreau-devolutions Marc-André Moreau (mamoreau-devolutions) commented Mar 18, 2026

Summary

  • centralize GitHub release tag and URL generation in CoreData
  • fix WinUI release notes to open the resolved release page URL
  • fix Avalonia release notes to try the resolved GitHub tag candidates before failing
  • add regression tests for legacy and Devolutions calendar-version tag formats

Root cause

Devolutions-branded releases use GitHub tags prefixed with v such as v2026.1.2, while the app was building release note URLs from the raw version string such as 2026.1.2. That caused the Release notes action to open a GitHub 404 page and the Avalonia API lookup to fail.

Validation

  • dotnet test src/UniGetUI.Core.Data.Tests/UniGetUI.Core.Data.Tests.csproj --verbosity minimal --nologo
  • dotnet build src/UniGetUI/UniGetUI.csproj --nologo --verbosity minimal -p:Platform=x64 -p:RuntimeIdentifier=win-x64
  • dotnet build src/UniGetUI.Avalonia/UniGetUI.Avalonia.csproj --nologo --verbosity minimal

Closes #4493

@mamoreau-devolutions Marc-André Moreau (mamoreau-devolutions) merged commit dff3e70 into main Mar 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] "Release notes" opens 404 github page

2 participants