-
Notifications
You must be signed in to change notification settings - Fork 118
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
feature: add publish action #1297
Conversation
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.
Anyway this might not work as intended unless we merge and test it on dev branch.
Current plan is to merge this and iterate through a few canary releases.
on: | ||
# Who has permission to workflow_dispatch | ||
# https://github.com/orgs/community/discussions/26622 | ||
workflow_dispatch: |
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.
if: contains('["..."]', github.actor)
does not really make sense to me
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.
workflow_dispatch
is a slightly recent feature iirc; maybe they couldn't use the feature at that moment.
I agree with using workflow_dispatch
👍
# checkout is pinned to dev branch here | ||
ref: dev | ||
- name: Setup Node | ||
uses: actions/setup-node@v3 |
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.
v4 use node 20 we should update CI before that
permissions: | ||
contents: write | ||
id-token: write |
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.
|
||
- name: Set package version | ||
run: | | ||
yarn lerna version ${{ github.event.inputs.version }} --exact --no-push --yes |
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.
I'm not sure if we need --force-publish
here
run: | | ||
git push origin ${{ github.ref_name }} | ||
|
||
- name: Upload Builds |
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.
Not sure if we want to automate the release tag on Github. There are only 3rd party solutions for now. https://github.com/actions/create-release#github-action---releases-api
.github/workflows/publish.yml
Outdated
- name: Set package version | ||
run: | | ||
yarn lerna version ${{ github.event.inputs.version }} --exact --no-push --yes | ||
yarn lerna publish from-git --dist-tag latest |
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.
it would be cool if we could make the disttag variable
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.
add in 42d5348
let's try whether it's working properly |
#1294
Description