@dpuse/dpuse-development 1.0.124 → 1.0.125

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -69,8 +69,32 @@ jobs:
69
69
  - name: Lint
70
70
  run: npm run lint
71
71
 
72
+ # Only in projects with end-to-end tests. 'vite.config.ts' serves over HTTPS with a certificate from
73
+ # '../../localhost/', which exists only on a developer's machine, so the runner gets a throwaway self-signed one
74
+ # at the same path. 'playwright.config.ts' accepts it on CI.
75
+ - name: Create localhost certificate
76
+ if: hashFiles('playwright.config.ts') != ''
77
+ run: |
78
+ mkdir -p ../../localhost
79
+ openssl req -x509 -newkey rsa:2048 -nodes -days 1 -subj "/CN=localhost" -keyout ../../localhost/localhost+1-key.pem -out ../../localhost/localhost+1.pem
80
+
81
+ # Only in projects with end-to-end tests. Chromium alone, which is all 'playwright.config.ts' runs on CI.
82
+ - name: Install Playwright browsers
83
+ if: hashFiles('playwright.config.ts') != ''
84
+ run: npx playwright install --with-deps chromium
85
+
72
86
  - name: Test
73
87
  run: npm test
74
88
 
89
+ # Only in projects with end-to-end tests, and only when a step fails. Playwright saves a trace of each failed
90
+ # test in 'test-results/', which the runner discards. Kept for a week, to open with 'npx playwright show-trace'.
91
+ - name: Upload Playwright results
92
+ if: failure() && hashFiles('playwright.config.ts') != ''
93
+ uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
94
+ with:
95
+ name: playwright-results
96
+ path: test-results/
97
+ retention-days: 7
98
+
75
99
  - name: Audit
76
100
  run: npm run audit
@@ -71,9 +71,33 @@ jobs:
71
71
  - name: Lint
72
72
  run: npm run lint
73
73
 
74
+ # Only in projects with end-to-end tests. 'vite.config.ts' serves over HTTPS with a certificate from
75
+ # '../../localhost/', which exists only on a developer's machine, so the runner gets a throwaway self-signed one
76
+ # at the same path. 'playwright.config.ts' accepts it on CI.
77
+ - name: Create localhost certificate
78
+ if: hashFiles('playwright.config.ts') != ''
79
+ run: |
80
+ mkdir -p ../../localhost
81
+ openssl req -x509 -newkey rsa:2048 -nodes -days 1 -subj "/CN=localhost" -keyout ../../localhost/localhost+1-key.pem -out ../../localhost/localhost+1.pem
82
+
83
+ # Only in projects with end-to-end tests. Chromium alone, which is all 'playwright.config.ts' runs on CI.
84
+ - name: Install Playwright browsers
85
+ if: hashFiles('playwright.config.ts') != ''
86
+ run: npx playwright install --with-deps chromium
87
+
74
88
  - name: Test
75
89
  run: npm test
76
90
 
91
+ # Only in projects with end-to-end tests, and only when a step fails. Playwright saves a trace of each failed
92
+ # test in 'test-results/', which the runner discards. Kept for a week, to open with 'npx playwright show-trace'.
93
+ - name: Upload Playwright results
94
+ if: failure() && hashFiles('playwright.config.ts') != ''
95
+ uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
96
+ with:
97
+ name: playwright-results
98
+ path: test-results/
99
+ retention-days: 7
100
+
77
101
  # One step for every project: the action publishes to npm, uploads to DPUse, or both, as the module type requires.
78
102
  # Called directly rather than through a package.json script, as a script named 'publish' would be run again by
79
103
  # 'npm publish' itself. The project's own commands, such as 'wrangler', are put on the path first, which
package/README.md CHANGED
@@ -166,9 +166,6 @@ This section is updated each time `npm run document` is run. Settings come from
166
166
 
167
167
  This project is working towards the [OpenSSF Best Practices](https://www.bestpractices.dev) Passing badge, a self-certification covering security policy, vulnerability reporting, build processes, code quality, and more. Currently the [OpenSSF Scorecard](https://scorecard.dev) provides an independent automated assessment of the project's security practices and is an ongoing area of improvement.
168
168
 
169
- > [!NOTE]
170
- > Apart from the Best Practices badge above, the remaining Scorecard gaps need multi-person review or a pull-request workflow, which this solo-maintained project doesn't use.
171
-
172
169
  ### Reporting Vulnerabilities
173
170
 
174
171
  Please do not open public GitHub issues for security vulnerabilities. Use [GitHub private vulnerability reporting](https://github.com/dpuse/dpuse-development/security/advisories/new) instead. See [SECURITY.md](./SECURITY.md) for the full disclosure policy, contact details, and expected response times.