Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

[BUG] Does not use the VERSION_STATIC property #46

Open
csharpfritz opened this issue Sep 27, 2020 · 2 comments
Open

[BUG] Does not use the VERSION_STATIC property #46

csharpfritz opened this issue Sep 27, 2020 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@csharpfritz
Copy link

Describe the bug
Does nothing with the version number assigned through VERSION_STATIC

Failed Action Log URL (Required)
A URL to the failed action log.

To Reproduce
Steps to reproduce the behavior:

  1. Assign value to VERSION_STATIC

Expected Behavior
NuGet package should be created with the assigned version

Environment:

@itniels
Copy link

itniels commented Aug 29, 2021

I ran into this issue as well, I have the Action create the version, and would like to set it manually for the NuGet package.

@Kritner
Copy link

Kritner commented Nov 22, 2021

Yeah I'm a bit unclear on how this is supposed to be integrated, or if this should just be more of a boolean flag?

GitVersioning just as an example seems to already "come up with" the version itself, and it produces a package file with that version accordingly (assuming doing GeneratePackageOnBuild). I'm tinkering around a bit with this build action right now and running into that problem.

Seems like some examples that show off the use of this feature may be worthwhile, like how it all fits together. Though based on some of the issues and prs in this repo, perhaps it's been abandoned?

@lukebakken lukebakken added this to the 2.6.0 milestone May 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants