Add publish dates for cross build environments#6248
Conversation
|
Ah, looks like we also need to update pyodide-build for this. Let me do that in a bit. |
|
Oh, wait. pyodide-build does not accept extra parameters? That's bad... I should've allowed it. |
|
No worries! |
There was a problem hiding this comment.
This change is only made for this PR for the CI to be green, i.e., this branch points to my PR at pyodide/pyodide-build#349. We have a bit of a "bootstrapping problem" :D
I'll revert this change in another PR after we merge this PR and the v2 JSON goes live on GitHub Pages, and then CI will be green on that pyodide-build PR as well.
- Adds a script to add v2 metadata for nightly cross-build environments in a JSON file (see generated JSON file) - The `publish.yml` workflow file now pushes a commit to `main`. I chose to not use a PR because it adds a bit of churn, but I can change the approach if asked - Added a `pages.yml` workflow to deploy the file on GitHub Pages There is no v1 file here, just v2, because it's the first time we are doing it and it doesn't make sense to go with the old spec. I will follow this up by putting together a PR in pyodide-build to use this metadata for those who would like to use nightly and nightly-debug builds. xref pyodide/pyodide#6248, pyodide/pyodide-build#349
ryanking13
left a comment
ryanking13
left a comment
There was a problem hiding this comment.
Thanks! As I commented, I think it is okay to freeze v1 and start publishing v2 only.
|
Done! |
|
I think we shouldn't have frozen v1 so quickly: I'm creating a pyodide-build v0.35.0 release and will manually patch the v1 JSON file here in this case to ease things. |
2 participants
Description
Adds
published_atfield for cross-build environments. It's the same as what we get from the GitHub API for releases, so it's kind of self-documenting. I am trying to use this data downstream in cibuildwheel to improve its supply chain for Pyodide package builders via cooldowns. See pypa/cibuildwheel#2841.