entvex opened a new pull request, #184: URL: https://github.com/apache/pulsar-dotpulsar/pull/184
**Issue Link**: [GitHub Issue #117](https://github.com/apache/pulsar-dotpulsar/issues/117) ### Description This GitHub Actions (GHA) workflow automates the release process for our software to NuGet. The process involves the following steps:  1. Create or select an existing tag. 2. Enter a release title. 3. Generate release notes. 4. Push the release to GitHub. However, there's a limitation: it won't upload the NuGet package to the release assets due to the need for additional GitHub permissions. Obtaining the required permissions might require a request to the Apache team to create a dedicated token for this purpose. Alternatively, the entire process could be automated when a maintainer creates a tag. But, once again, this requires a GitHub access token, and it's uncertain whether Apache would provide one. There are third-party GitHub Actions available for this purpose, but they are deprecated ([example](https://github.com/actions/upload-release-asset)). Additionally, the 'action-gh-release' action is no longer maintained ([details](https://github.com/softprops/action-gh-release/issues/107)). As a workaround, I'm exploring the possibility of using the GitHub CLI within GitHub Actions to obtain the necessary permissions. ### Testing Testing this workflow is challenging since GitHub doesn't offer a straightforward testing environment. I initially tested it on my personal project, [nugettestrepo_delete_me_soon](https://github.com/entvex/nugettestrepo_delete_me_soon), and confirmed its functionality. Later, I adapted the GHA configuration to match the DotPulsar folder structure. Unfortunately, due to GitHub's limitations, there are no comprehensive testing options available beyond these steps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
