Open keithrfung opened 2 years ago
The idea is to have a workflow that will auto increment the package to the semantic version that is on the Milestone on the release workflow.
https://github.com/microsoft/electionguard-cpp/blob/main/.github/workflows/release.yml
So for example if the milestone is named "1.1.0 : New Release", the workflow would create a commit incrementing the package to 1.1.0.
1.1.0
These are the two sections that should be investigated: https://github.com/microsoft/electionguard-cpp/blob/99788bc9fb76ee2293e9b131965b91b85ba6fee3/bindings/netstandard/ElectionGuard/ElectionGuard.Encryption/ElectionGuard.Encryption.csproj#L10-L20
https://github.com/microsoft/electionguard-cpp/blob/da452f68f10f18f3a04ff932821f789bb5c00bb1/CMakeLists.txt#L8-L10
The easiest way is probably a GitHub action. A version file can be used if this simplifies the workflow. A single source of truth is ideal.
No response
Is there an existing issue for this?
Suggestion
The idea is to have a workflow that will auto increment the package to the semantic version that is on the Milestone on the release workflow.
https://github.com/microsoft/electionguard-cpp/blob/main/.github/workflows/release.yml
So for example if the milestone is named "1.1.0 : New Release", the workflow would create a commit incrementing the package to
1.1.0
.These are the two sections that should be investigated: https://github.com/microsoft/electionguard-cpp/blob/99788bc9fb76ee2293e9b131965b91b85ba6fee3/bindings/netstandard/ElectionGuard/ElectionGuard.Encryption/ElectionGuard.Encryption.csproj#L10-L20
https://github.com/microsoft/electionguard-cpp/blob/da452f68f10f18f3a04ff932821f789bb5c00bb1/CMakeLists.txt#L8-L10
Possible Implementation
The easiest way is probably a GitHub action. A version file can be used if this simplifies the workflow. A single source of truth is ideal.
Anything else?
No response