Weekly github digest (WebAppSec specs)

Issues
------
* w3c/webappsec (+0/-0/💬1)
  1 issues received 1 new comments:
  - #666 Planning 2025-02-19 (1 by christhompson)
    https://github.com/w3c/webappsec/issues/666 

* w3c/webappsec-csp (+1/-0/💬7)
  1 issues created:
  - "source file" lacks a real defintion (by evilpie)
    https://github.com/w3c/webappsec-csp/issues/707 

  5 issues received 7 new comments:
  - #707 "source file" lacks a real defintion (1 by annevk)
    https://github.com/w3c/webappsec-csp/issues/707 
  - #706 connect-src test suite allows multiple non-interopable implementations. (1 by dveditz)
    https://github.com/w3c/webappsec-csp/issues/706 [interop] 
  - #701 How to specify 2 endpoints for Reporting-Endpoints? (1 by ciaramcmullin)
    https://github.com/w3c/webappsec-csp/issues/701 
  - #687 Should "Should navigation request of type be blocked by Content Security Policy?" set the violation object's element? (3 by dveditz, mbrodesser-Igalia)
    https://github.com/w3c/webappsec-csp/issues/687 [editorial] [clarification] 
  - #446 Address Bikeshed warnings (1 by ciaramcmullin)
    https://github.com/w3c/webappsec-csp/issues/446 



Pull requests
-------------
* w3c/webappsec-subresource-integrity (+0/-1/💬2)
  2 pull requests received 2 new comments:
  - #130 GitHub actions: replace ubuntu-20.04 with ubuntu-latest (1 by mozfreddyb)
    https://github.com/w3c/webappsec-subresource-integrity/pull/130 
  - #129 Revive require-sri-for for scripts (1 by mozfreddyb)
    https://github.com/w3c/webappsec-subresource-integrity/pull/129 

  1 pull requests merged:
  - GitHub actions: replace ubuntu-20.04 with ubuntu-latest
    https://github.com/w3c/webappsec-subresource-integrity/pull/130 

* w3c/webappsec-permissions-policy (+0/-1/💬0)
  1 pull requests merged:
  - Add allow and src attribute to potential permissions policy violation report
    https://github.com/w3c/webappsec-permissions-policy/pull/559 

* w3c/webappsec-fetch-metadata (+0/-0/💬2)
  1 pull requests received 2 new comments:
  - #89 Define `Sec-Fetch-Frame-Ancestors`. (2 by annevk, sjledoux)
    https://github.com/w3c/webappsec-fetch-metadata/pull/89 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webappsec
* https://github.com/w3c/webappsec-subresource-integrity
* https://github.com/w3c/webappsec-csp
* https://github.com/w3c/webappsec-mixed-content
* https://github.com/w3c/webappsec-upgrade-insecure-requests
* https://github.com/w3c/webappsec-credential-management
* https://github.com/w3c/permissions
* https://github.com/w3c/permissions-registry
* https://github.com/w3c/webappsec-referrer-policy
* https://github.com/w3c/webappsec-secure-contexts
* https://github.com/w3c/webappsec-clear-site-data
* https://github.com/w3c/webappsec-cowl
* https://github.com/w3c/webappsec-epr
* https://github.com/w3c/webappsec-suborigins
* https://github.com/w3c/webappsec-cspee
* https://github.com/w3c/webappsec-permissions-policy
* https://github.com/w3c/webappsec-fetch-metadata
* https://github.com/w3c/webappsec-trusted-types
* https://github.com/w3c/webappsec-change-password-url
* https://github.com/w3c/webappsec-post-spectre-webdev


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config