-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actions Find replacement for Update-Release action #359
Comments
This is actually causing a bug randomly with one of the release tags conflicting, need to address this as having to manually go in and remove XROS 03 randomly for a build success on bleeding main/master |
I do not recommend that you depend on that code. I initiated it as an experiment at the time, and since then many superior options have surfaced. |
softprops/action-gh-release ? |
I'm not sure if action-gh-release is working on projectGenerator it seemed to have some serious issues recently |
Thanks @johnwbyrd it has worked great for a long time regardless haha! There is currently an issue just manfiested today deploying gzip to release with the trailing & and failing on windows releases today |
Okay this is currently the main issue the VS releases... we need to look at replacing the GH Action |
I'm using softprops/[email protected] |
Nice this is looking good. I've just re-written the VS actions to support this softprops release and its working great. Also I've added support for TAGS to auto build to those tags. Looking good! Updating artifacts to use tags/release to fix any cache issues I could think of. Re: Tags: This will allow for @ofTheo to just tag at any point the libraries to a version and it will auto build to releases, ez pz |
Hey @danoli3 great news! I suggest we use tags for any apothecary changes, so for a specific OF release it can point to a specific Apothecary release. |
about versions: if apothecary is broken again for any reason we can hang on a specific version |
Yeah tags are now working it will build for that tag, I'm testing with Latest, but any tag will work, version number etc. Just fixing up some cache issues |
We can apply the same code to pG and oF releases also |
Yes. it will be great! we can have lots of intermediate releases in OF it will be great |
Need to find a replacement for
16 about to marked as unusable due to security issues.
OG @johnwbyrd has archived his repo, unless he wants to update it, we need to replace it with another one
The text was updated successfully, but these errors were encountered: