Skip to content

Commit 4f5f610

Browse files
committed
Fix CSharpier formatting for package Version metadata
Align BlazorCanvas2d.csproj Version conditions with tag builds so the formatter check passes in CI.
1 parent 33d7c79 commit 4f5f610

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

BlazorCanvas2d/BlazorCanvas2d.csproj

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@
1212
<!--
1313
Package versioning:
1414
- On tag builds: use the tag name (optionally prefixed with 'v').
15-
- On PR/branch builds (e.g. refs/pull/*/merge where GITHUB_REF_NAME can contain '/'):
16-
use a valid SemVer pre-release so `dotnet restore` doesn't fail.
15+
- On non-tag CI builds: use a SemVer pre-release based on the run number.
16+
- Locally: use a fixed SemVer version.
1717
-->
1818
<Version
19-
Condition="'$(GITHUB_REF_NAME)' != '' and $([System.String]::Copy('$(GITHUB_REF_NAME)').Contains('/')) == 'false'"
19+
Condition="'$(Version)' == '' and '$(GITHUB_REF_TYPE)' == 'tag' and '$(GITHUB_REF_NAME)' != ''"
2020
>
2121
$(GITHUB_REF_NAME.TrimStart('v'))
2222
</Version>

0 commit comments

Comments
 (0)