[salehadk59-boop]

Work flow -Enable prereleases and beta releases
To run the workflow manually from the command line with the
GitHub CLI instead of the UI:

gh auth login
gh workflow run build-and-release.yml --ref -f release-version=12.0.1
gh run list --workflow build-and-release.yml --limit 3
gh run watch

[sumanthkb44]

@salehadk59-boop please check the conflicts

[salehadk59-boop]

@sumanthkb44 resolved the conflicts

[sumanthkb44]

@salehadk59-boop What will be the release process ?
Update the Contributing.md , which give a clear picture how to release a Release Versions.

[crvreddy]

@salehadk59-boop Pre release version won't release directly.First should create draft version.

[salehadk59-boop]

@crvreddy Implemented the changes, now Pre release version won't release directly, it will create as draft version.
GitHub Release is created as a draft, marked as a pre-release. It won't be visible publicly/"released" until someone manually reviews and publishes it.

[NaveenkumarBasavarajappa]

Please schedule the internal demo

[NaveenkumarBasavarajappa]

please schedule the internal demo

[crvreddy]

@saleha.khathun.ext@siemens.com Raise PR to development branch

[salehadk59-boop]

@saleha.khathun.ext@siemens.com Raise PR to development branch

@crvreddy yes changed to development branch

[NaveenkumarBasavarajappa]

@salehadk59-boop : What will happen to the existing .nuspec and .csproj files? Will the versions in those files remain unchanged, or do we need to update them manually?

[salehadk59-boop]

@salehadk59-boop : What will happen to the existing .nuspec and .csproj files? Will the versions in those files remain unchanged, or do we need to update them manually?

[salehadk59-boop]

@salehadk59-boop : What will happen to the existing .nuspec and .csproj files? Will the versions in those files remain unchanged, or do we need to update them manually?

@NaveenkumarBasavarajappa
The versions in the .csproj and .nuspec files will remain unchanged. No manual update is required because the pipeline overrides them at build/pack time using -p:Version=${{ env.SEMVER }} and nuget pack -Version ${{ env.SEMVER }}. As a result, the generated DLLs and NuGet package use the correct release version, while the hardcoded values only act as a fallback for local builds executed without those overrides.

For the CA.nuspec file, we can replace the hardcoded version with NuGet's $version$ token, which is automatically populated by the existing -Version argument.

For the .csproj files, We can remove the hardcoded versions and use a Directory.Build.props approach to provide a centralized fallback version.