-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
Build assets on release #6982
Build assets on release #6982
Conversation
- name: "Install Node" | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version-file: ".nvmrc" | ||
cache: "yarn" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copied from the Assets workflow haha
cd "$TMP_FOLDER"/"$RELEASE_FOLDER"/"$VERSION" && yarn install --non-interactive | ||
cd "$TMP_FOLDER"/"$RELEASE_FOLDER"/"$VERSION" && yarn run --non-interactive build:prod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested those commands locally and they work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't you remove the assets from git then? And maybe also remove the assets
workflow?
@j0k3r yes! but wanted to have this merged first and see it working in the next release before cleaning the code :) |
I think you can clean it right now :) |
@j0k3r answering you I realize that with assets still in the repo the release will work anyway... 😅 so I'll clean now |
4b4030e
to
7526069
Compare
Assuming the release script is used only through the GitHub action
similar to wallabag/docker#362 but for ZIP releases