Feature/merge alpha to beta #53
Conversation
set auto generation of nuget false on build
chore(backplane-client-net) :csproj update [skip ci]
Backplane client nuget package restore failing due to missing dependency in packaging.
# [backplane-client-net-v1.0.0-alpha.2](backplane-client-net-v1.0.0-alpha.1...backplane-client-net-v1.0.0-alpha.2) (2023-01-09) ### Bug Fixes * **backplane-client-net:** nuget restore ([ff4fd84](ff4fd84))
Update nuget package name in readme.
# [backplane-client-net-v1.0.0-alpha.3](backplane-client-net-v1.0.0-alpha.2...backplane-client-net-v1.0.0-alpha.3) (2023-01-09) ### Bug Fixes * **backplane-client-net:** readme ([af59ffb](af59ffb))
Fix nuget pack missing DTO dll reference.
fix(backplane-client-net): nuget pack
chore(yml): release account [skip ci]
fix(backplane-client-net): readme
chore(yml): Update github token [skip ci]
# [backplane-client-net-v1.0.0-alpha.4](backplane-client-net-v1.0.0-alpha.3...backplane-client-net-v1.0.0-alpha.4) (2023-01-18) ### Bug Fixes * **backplane-client-net:** nuget pack ([b01d7f7](b01d7f7)) * **backplane-client-net:** readme ([3a1ad97](3a1ad97)) * **readme:** grammar correction ([27b0538](27b0538))
#43 quick start guide
docs(HelloWorld.md): typos correction
There was a problem hiding this comment.
@Vivek-NatWest I'm not seeing changes from https://github.com/finos/backplane/pull/50/files in this PR - is that expected?
Also, I note the version number being merged is 1.0.0-alpha.4, should that be updated in the feature branch?
Is there documentation of how you use the alpha/beta/main branches in the project somewhere that I should review?
Sorry missed this comment before merging. This PR is to promote alpha to beta, post which to promote to main to release the new version which would contain the https://github.com/finos/backplane/pull/50/files as it is already merged to main. Correctly pointed out that the feature branch need not have version info which got into it during merging, my bad. Although that version is auto-replaced by the release version by the ci pipeline, it should be auto-corrected with the automated release workflow. In terms of branching strategy, it is based on release streams: |
|
🎉 This PR is included in version backplane-client-net-v1.0.0-beta.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version backplane-client-net-v1.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
No description provided.