GitHub user Fatorin edited a comment on the discussion: .NET release: align package name and trigger strategy before enabling publication
I agree that we should not proceed with an official release yet, as the stability of this package has not been fully verified. NuGet Trusted Publishing is not yet activated, so the current workflow will not publish packages to NuGet. Based on the [dotnet pack documentation](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-pack), we can control the package version via additional parameters, so there is no need to introduce a special dotnet- tag format. We can derive the package version directly from the repository tag and pass it to dotnet pack via /p:PackageVersion, which avoids hardcoding the version in the .csproj. This also allows us to handle RC or test versions more cleanly. Since the package is still in a testing phase, I’m considering enforcing an RC suffix during packing for now (e.g., --version-suffix "rc"), with proper normalization if the tag already includes an RC suffix. I will open an issue and submit a PR within the next couple of days to address these points. And I recommend using OpenDAL instead of DotOpenDAL. GitHub link: https://github.com/apache/opendal/discussions/7345#discussioncomment-16395047 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
