💻
What problem are you trying to solve?
Each time upstream compat-data have been updated, maintainers have to manually open a pull request.
Describe the solution you'd like
Use the same approach as https://github.com/babel/babel/blob/main/.github/workflows/update-parser-tests.yml
Having a CRON in GitHub action that will check if there are any updates on the following sources:
- https://github.com/kangax
- "@mdn/browser-compat-data": "^4.0.10",
- "core-js-compat": "^3.20.2",
- "electron-to-chromium": "^1.3.893"
Then, run existing scripts in the repo like make build-compat-data
Open a pull request!
Thanks @JLHwung, for the idea 🙌
Describe alternatives you've considered
Didn't imagine any alternative here 💩.
Documentation, Adoption, Migration Strategy
No response
💻
What problem are you trying to solve?
Each time upstream compat-data have been updated, maintainers have to manually open a pull request.
Describe the solution you'd like
Use the same approach as https://github.com/babel/babel/blob/main/.github/workflows/update-parser-tests.yml
Having a CRON in GitHub action that will check if there are any updates on the following sources:
Then, run existing scripts in the repo like
make build-compat-dataOpen a pull request!
Thanks @JLHwung, for the idea 🙌
Describe alternatives you've considered
Didn't imagine any alternative here 💩.
Documentation, Adoption, Migration Strategy
No response