Skip to content

Conversation

@smaillet
Copy link
Member

Bumped version of Versioning task

  • Proper versions had a bug where it didn't provide the version for project references.
    • How NuGet deals with project references and gets a version to use for the generated NuSpec dependency is a bit of a black art. None of it is formally documented, but is critical to any automated versioning system. Sadly the versioning task got this wrong and thus the generated packages all had 1.0.0 as the version for all project reference dependencies.

* Proper versions had a bug where it didn't provide the version for project references.
    - How NuGet deals with project references and gets a version to use for the generated NuSpec dependency is a bit of a black art. None of it is formally documented, but is critical to any automated versioning system. Sadly the versioning task got this wrong and thus the generated packages all had `1.0.0` as the version for all project reference dependencies.
@github-actions
Copy link

Test Results

280 tests   172 ✅  10s ⏱️
  6 suites  108 💤
  6 files      0 ❌

Results for commit 51f10b3.

@smaillet smaillet merged commit 63b7465 into UbiquityDotNET:develop Jul 18, 2025
4 checks passed
@smaillet smaillet deleted the BumpVersionTasks branch July 18, 2025 15:58
@smaillet smaillet linked an issue Jul 18, 2025 that may be closed by this pull request
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] - Package references invalid dependencies - UNUSABLE

1 participant