GitHub user Xuanwo added a comment to the discussion: Release Workflow Design for OpenDAL .NET Binding
I think we should do workflow_dispatch only. Bindings should never depends on opendal's tag and we need to bump the version during the release process. The going binding is the only exception because the go ecosystem relies tags to work. > But for urgent releases (e.g., a critical bug fix), this requires multiple > steps: update .csproj → merge PR → manually trigger workflow — which adds > friction in time-sensitive situations. It's fine. We can run fast if needed, for example, we used to release a bug fix in 3 hours. But we don't to overthinking about this before it happened. GitHub link: https://github.com/apache/opendal/discussions/7394#discussioncomment-16618530 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
