You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
Describe the solution you'd like
When we push a tag vX.Y.Z, a variety of actions run that, as long as the builds and all are successful, result in releasing wash to homebrew, chocolatey, snap, and packagecloud.
Describe alternatives you've considered
We could also use git webhooks in those repositories in order to listen for tag pushes / releases here. I don't see a specific reason that would be more or less efficient than managing here, but I like the idea of having all of the release actions in this repository for easy management.
Additional context
If you're looking to contribute to this issue, thoughts + advice is welcome! Our release process with homebrew is the more complex, relying on opening a PR and then applying a label to that PR, so I'm definitely interested in strategies where I can complete it automatically with an action.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!
Is your feature request related to a problem? Please describe.
Each time we create a release for
wash
, it requires a manual PR to https://github.com/wasmCloud/homebrew-wasmcloud and https://github.com/wasmCloud/chocolatey-wash in order to release with brew and choco. We should migrate those files and actions here so we can seamlessly cut releases ofwash
Describe the solution you'd like
When we push a tag
vX.Y.Z
, a variety of actions run that, as long as the builds and all are successful, result in releasing wash to homebrew, chocolatey, snap, and packagecloud.Describe alternatives you've considered
We could also use git webhooks in those repositories in order to listen for tag pushes / releases here. I don't see a specific reason that would be more or less efficient than managing here, but I like the idea of having all of the release actions in this repository for easy management.
Additional context
If you're looking to contribute to this issue, thoughts + advice is welcome! Our release process with homebrew is the more complex, relying on opening a PR and then applying a label to that PR, so I'm definitely interested in strategies where I can complete it automatically with an action.
The text was updated successfully, but these errors were encountered: