Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Publish plain JSON artifacts "live" #1860

Open
ddbeck opened this issue Sep 27, 2024 · 1 comment
Open

Publish plain JSON artifacts "live" #1860

ddbeck opened this issue Sep 27, 2024 · 1 comment
Labels
enhancement New feature or request tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings

Comments

@ddbeck
Copy link
Collaborator

ddbeck commented Sep 27, 2024 •
edited
Loading

We publish a next-tagged web-features pre-release on npm on each push to main (you install it with npm install web-features@next). If you want the latest web-features data, this is convenient, unless you're not an npm user.

We ought to publish the plain JSON files on the web-features site, so that it's possible to do something like curl https://web-platform-dx.github.io/web-features/downloads/next/data.json (and likewise for the extended JSON and JSON Schema artifacts).
@ddbeck ddbeck added enhancement New feature or request tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings labels Sep 27, 2024
@ddbeck ddbeck mentioned this issue Sep 27, 2024
Closed
@tabatkins
Copy link

tabatkins commented Sep 27, 2024 •
edited
Loading

Yup, I was about to ask about this in #1853. My use-case is having the bikeshed-data project (which runs about 100 times/day) fetch the data, then digest it into the form that Bikeshed users will actually download. This is a Python project, and just pings a bunch of public URLs for its data sources, including currently the CanIUse and MDN data; I was hoping I could use this same strategy for Web Features data.

Note that CanIUse just has one giant JSON blob; MDN has a top-level directory listing, and then I download all the individual files it mentions. I can handle either way, whatever's convenient for y'all; all I need is a dependable way to get all the data without manual intervention.

ddbeck added a commit to ddbeck/web-features that referenced this issue Oct 1, 2024
@ddbeck
Create a continuous prerelease for GitHub
e19b32d 
This is like the `web-features@next` release on npm, but on GitHub and
extended to the bare JSON artifacts.

This is setup for web-platform-dx#1860.
@ddbeck ddbeck mentioned this issue Oct 1, 2024
Merged
ddbeck added a commit that referenced this issue Oct 8, 2024
@ddbeck
Create a continuous prerelease for GitHub (#1875)
d90343d 
This is like the `web-features@next` release on npm, but on GitHub and
extended to the bare JSON artifacts.

This is setup for #1860.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ddbeck @tabatkins