Skip to content

Use pipeline IID instead of global job ID

jvyden requested to merge jvyden/zarlo.cosmos:jvyden-main-patch-43412 into main

Discussed on discord here: https://discord.com/channels/833970409337913344/834060104143208487/1121521076980166676

This MR changes the build scripts to use the pipeline IID for versioning rather than the job ID. This fixes the problems of packages depending on projects built before the dependent. (e.g. Zarlo.Cosmos@0.1.0-alpha.2 depending on Zarlo.Cosmos.Core@0.1.0-alpha.1)

The problem manifests by not being able to install the packages:

Unable to find package Zarlo.Cosmos.Core with version (>= 0.1.0-alpha.4509983725)
  - Found 3 version(s) in Zarlo [ Nearest version: 0.1.0-alpha.4509983721 ]
Unable to find package Zarlo.Cosmos.Memory with version (>= 0.1.0-alpha.4509983725)
  - Found 4 version(s) in Zarlo [ Nearest version: 0.1.0-alpha.4509983724 ]
Unable to find package Zarlo.Cosmos with version (>= 0.1.0-alpha.4509983725)
  - Found 2 version(s) in Zarlo [ Nearest version: 0.1.0-alpha.4509983719 ]

This MR also bumps the version to 0.1.1 since the pipeline IID will be way smaller than the job ID, making the new version number lower (and thus older to NuGet).

Merge request reports