Closed stephengtuggy closed 4 years ago
At work, the way we avoid issues like this is by having the CICD plug in the value from the branch name. Something to consider.
@royfalk its mixed. There's a few solutions methods; I haven't found a good one yet. Using branch/tag names makes it hard to use 0.6.x
as the branch as x
isn't valid in the numeric field, meaning we're also having to make a lot more branches.
Other solutions use environment variables, or specialized packages. Honestly I haven't seen a good one. We can certainly explore options in an Issue though.
What about adding a check and verify step to the release routine for now so we at least don't get to embarrassed in the future.
For my Python projects I usually add something to the unit tests to make sure things match up (typically b/c it's specified in multiple places)... not sure how we can do that here or if that would apply.
Opened https://github.com/vegastrike/Assets-Masters/issues/19 to continue the discussion.
The 0.6.2 version of vsUTCS still says 0.5.2 alpha in these two places. Oops!
Updating master to reflect version 0.7.0. We may want to update the 0.6.x branch as well.