This will be part of a hot-fix release where we aim to recover from some of the issues that went wrong with the publishing jobs during the v2.0.0 release.
The root cause of most of the problems is that we've been moved to a new GitHub org which then rendered a lot of the publishing workflows/jobs invalid due them hard-coding the GitHub org as hyperledger instead of using the context variable github.repository_owner [1] [2]
Publishing workflows have been updated where possible to not hardcode the repository owner as hyperledger
The changes were tested against a 2.0.1-alpha.1 release.
If 2) succeeded then we are good to go. If it did not produce the expected release artifacts then iterate with 2.0.1-alpha.2, 2.0.1-alpha.3, etc. until we get it all hammered out.
Description
This will be part of a hot-fix release where we aim to recover from some of the issues that went wrong with the publishing jobs during the v2.0.0 release.
The root cause of most of the problems is that we've been moved to a new GitHub org which then rendered a lot of the publishing workflows/jobs invalid due them hard-coding the GitHub org as
hyperledgerinstead of using the context variablegithub.repository_owner[1] [2][1] https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context [2] https://stackoverflow.com/a/70709545/698470
(add more description and relevant links)
Acceptance Criteria
hyperledger2.0.1-alpha.1release.2.0.1-alpha.2,2.0.1-alpha.3, etc. until we get it all hammered out.@VRamakrishna @sandeepnRES