You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ones that have this have the starter template URLhttps://codepen.io/gkatsev/pen/GwZegv?editors=1000#0 in the commit message.
gh api \
-H "Accept: application/vnd.github+json" \
-H "X-GitHub-Api-Version: 2022-11-28" \
/repos/videojs/video.js/commits/c1a8cbf \
| jq '.commit.message'
"chore: Enable supply chain security through npm provenance attestation (#8911)\n\n## Description\r\n\r\n- Configure GitHub Actions workflow for secure publishing\r\n- Enable automatic provenance generation during npm publish\r\n- Add integrity verification through Sigstore transparency logs\r\n\r\nFollowing the recent Lottie-Player supply chain attack, it's crucial to\r\nenhance package security. NPM provenance provides cryptographic proof\r\nthat this package was built from this repository using GitHub Actions,\r\nmaking supply chain attacks significantly harder. More info in my blog\r\npost\r\nhttps://medium.com/exaforce/npm-provenance-the-missing-security-layer-in-popular-javascript-libraries-b50107927008\r\n\r\n## Specific Changes proposed\r\nChanges the workflow github to publish provenance attestation on\r\nhttps://www.npmjs.com/package/video.js\r\n\r\n## Requirements Checklist\r\n- [x] Feature implemented in CI/CD\r\n- [ ] If necessary, more likely in a feature request than a bug fix\r\n- [ ] Change has been verified in an actual browser (Chrome, Firefox,\r\nIE)\r\n - [x] Unit Tests updated or fixed\r\n - [ ] Docs/guides updated\r\n- [ ] Example created ([starter template on\r\nJSBin](https://codepen.io/gkatsev/pen/GwZegv?editors=1000#0))\r\n- [ x Has no DOM changes which impact accessiblilty or trigger warnings\r\n(e.g. Chrome issues tab)\r\n - [x] Has no changes to JSDoc which cause `npm run docs:api` to error\r\n- [ ] Reviewed by Two Core Contributors"
Current version of changelog document (this) has a broken link to an issue.
The interested section is for release 8.19.0, here:
That
1000#0
link.Also, just noticed that there are more and more instances of that down the page, e.g. for latest release 8.2.11, all closed issues in 8.18.0, etc.
HTH
The text was updated successfully, but these errors were encountered: