-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
Fix pypi deploy for patch releases #3113
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.
Thanks!
Well this still doesn't work. |
I think it will work when we release a new version with a tag, as |
I don't think the but I get the response:
|
https://github.com/pyodide/pyodide/actions/runs/3064780993 but I see it was triggered 3 days ago? |
That was a manual trigger from the web interface, not from |
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.
That was a manual trigger from the web interface, not from curl. Since this PR was merged, I have been unable to trigger the job via curl.
Oh, okay. I thought that it was triggered by curl.
https://api.github.com/repos/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME}/dispatches \ | ||
-d '{"event_type":"deploy-release","client_payload":{}}' | ||
-H "Authorization: Bearer ${GITHUB_TOKEN}" \ | ||
https://api.github.com/repos/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME}/dispatches/deploy-release \ |
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 seems like the order is different? (+ the filename)
/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches
https://api.github.com/repos/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME}/dispatches/deploy-release \ | |
https://api.github.com/repos/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME}/actions/workflows/deploy_release.yml/dispatches \ |
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.
Can create an API token and test this out? I tried a bunch of different variations like this and none of them were working for me. But maybe I was just being dumb.
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 removed the type: [deploy-release]
part in deploy_release.yml, and I was able to run a workflow with curl.
I think it was blocking a workflow run (it is mentioned in repository_dispatch
docs, but probably it was also affecting workflow_dispatch
:
When you make a request to create a repository_dispatch event, you must specify an event_type to describe the activity type.
By default, all repository_dispatch activity types trigger a workflow to run.
You can use the types keyword to limit your workflow to run when a specific event_type value is sent in the repository_dispatch webhook payload.
Apparently
repository_dispatch
only works on the main branch and what we need isworkflow_dispatch
. After we merge this, we can backport it to stable and I can do an ad-hoc test by trying to use it to deploy pyodide-build v0.21.3.