Generate site data during deployment
Test and deploy / deploy (push) Successful in 29s

This commit is contained in:
2026-07-25 22:06:12 -05:00
parent a601fcdb09
commit 282ef59f6f
2 changed files with 6 additions and 2 deletions
+3
View File
@@ -23,6 +23,9 @@ jobs:
- name: Install dependencies - name: Install dependencies
run: npm ci run: npm ci
- name: Generate website data
run: npm run update:generated
- name: Test the site - name: Test the site
run: npm test run: npm test
+3 -2
View File
@@ -10,8 +10,9 @@ Known and addressed issues for newly released versions are easily added using th
- Copy the issue table's HTML from the webpage using devtools. - Copy the issue table's HTML from the webpage using devtools.
- Fill out the process.html page's fields and paste in the table HTML. - Fill out the process.html page's fields and paste in the table HTML.
- Download the Markdown file and put it into the correct folder. - Download the Markdown file and put it into the correct folder.
- Run `npm run update:generated` to update `products.json`, append new stable - Optionally run `npm run update:generated` locally to preview the generated
product-tree manifest slots, and regenerate rendered test fixtures. `products.json`, product-tree manifest slots, and rendered test fixtures.
Gitea Actions runs this command again before testing and deploying.
- Submit a pull request. - Submit a pull request.
There is intentionally no automated scaping of Palo Alto's website, to avoid abuse of server resources. Also releases are not that frequent. A crawler to grab some data from the Common Crawl dataset was started but never really finished. There is intentionally no automated scaping of Palo Alto's website, to avoid abuse of server resources. Also releases are not that frequent. A crawler to grab some data from the Common Crawl dataset was started but never really finished.