Skip to content

Refactor publishing of .NET client to be inline with other clients and use dispatch workflow #4766

@mladjan-gadzic

Description

@mladjan-gadzic

Is your feature request related to a problem? Please describe.

With increasing number of Armada clients, it makes sense to publish those in consistent manner. For example Java/Python/Scala and Rust are using dispatch workflow (manual publish). It works by:

  • bumping up version in respective build file
  • creating a PR
  • merging it to the master
  • running workflow manually which publishes artifact

.NET client is different because it uses tags and based on semver it does publishing.

Describe the solution you'd like

All clients should follow same pattern of publishing - ideally dispatch workflow (less refactoring needed).

Describe alternatives you've considered

Using semvar tags is more automated but it has to be documented somewhere. By using dispatch workflow nothing needs to be documented.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions