sistent icon indicating copy to clipboard operation
sistent copied to clipboard

[CI] Lookup Release Version # When Manually Releasing

Open leecalcote opened this issue 2 years ago • 3 comments

          While dispatching, if one of the steps here isn't dynamically identifying the latest release tag, we might want to require the release tag as input here. 

You might like to grab the release tag lookup "function" from another one of the makefiles / workflows.

Originally posted by @leecalcote in https://github.com/layer5io/sistent/pull/95#discussion_r1323668544

leecalcote avatar Sep 27 '23 16:09 leecalcote

Updated GitHub Actions workflow to release from using lerna

But I'm running into an issue with GitHub Actions to publish a release:

https://github.com/layer5io/sistent/actions/runs/6343737428/job/17232399284

nebula-aac avatar Sep 28 '23 20:09 nebula-aac

Any reason not to use the pre-established and pre-debugged approach that we’re already using?

leecalcote avatar Sep 28 '23 20:09 leecalcote

Any reason not to use the pre-established and pre-debugged approach that we’re already using?

The workflow is still attempting to publish via GitHub Release, but before, whenever you use yarn to build and release, you can only run yarn in the current directory, not throughout the workspace.

It is better to allow a build tool to help automate this.

nebula-aac avatar Sep 28 '23 21:09 nebula-aac