mistercrunch commented on issue #27378: URL: https://github.com/apache/superset/issues/27378#issuecomment-1977881932
For the record, job is running here -> https://github.com/apache/superset/actions/runs/8150387426/job/22276578594 Explaining a bit more the intricacy of the different between a `release` GHA trigger and and `workflow_dispatch` on master... The former will use the old GHAs defined in the branch, while the `master` trigger will use the GHA definitions on `master`, pull the right branch, and run the build based on that. Subtle difference, but the reason for the issue here... For older release/re-release, we'll have to manually dispatch from `master` as such: <img width="1299" alt="Screenshot 2024-03-04 at 6 55 08 PM" src="https://github.com/apache/superset/assets/487433/9698364f-2414-4e29-9b4c-abe48f792828";> Moving forward, it shouldn't be an issue, unless we want to retroactively change some of the logic, say if we wanted to introduce a third build platform retroactively, we'd have to fiddle with things, trigger from `master`, ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
