dev  

Messages by Thread

• [I] Consider adding zizmor action security checks (tooling-actions) via GitHub
• [PR] Check templates linter (tooling-trusted-releases) via GitHub
  • Re: [PR] Check templates linter (tooling-trusted-releases) via GitHub
  • Re: [PR] Check templates linter (tooling-trusted-releases) via GitHub
• [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
  • Re: [PR] Move auth buttons (tooling-trusted-releases) via GitHub
• [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
  • Re: [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
  • Re: [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
  • Re: [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
  • Re: [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
  • Re: [I] Login/logoff should be a button on the top nav and not a menu (tooling-trusted-releases) via GitHub
• [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
  • Re: [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
  • Re: [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
  • Re: [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
  • Re: [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
  • Re: [I] Document how to become a Trusted Publishing project (tooling-trusted-releases) via GitHub
• [I] Add user configuration for navigation pinning and colour blindness mode (tooling-trusted-releases) via GitHub
  • Re: [I] Add user configuration for navigation pinning and colour blindness mode (tooling-trusted-releases) via GitHub
• [I] Apply path ignores to implicitly classified source archives (tooling-trusted-releases) via GitHub
• [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
  • Re: [I] Add a column of file type and classifier to file lists (tooling-trusted-releases) via GitHub
• [I] Add a quarantined validation period after uploading and before checks are started (tooling-trusted-releases) via GitHub
  • Re: [I] Add a quarantined validation period after uploading and before checks are started (tooling-trusted-releases) via GitHub
  • Re: [I] Add a quarantined validation period after uploading and before checks are started (tooling-trusted-releases) via GitHub
• [I] Remove the leading `/` from RAT check results (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the leading `/` from RAT check results (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the leading `/` from RAT check results (tooling-trusted-releases) via GitHub
• [I] Nexus 3 testing of both legacy and ATR methods on repository.apache.org (tooling-trusted-releases) via GitHub
• [I] Implement the "Pause for RM" release policy option (tooling-trusted-releases) via GitHub
  • Re: [I] Implement the "Pause for RM" release policy option (tooling-trusted-releases) via GitHub
  • Re: [I] Implement the "Pause for RM" release policy option (tooling-trusted-releases) via GitHub
• [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
  • Re: [PR] File type validation on upload through web browser (tooling-trusted-releases) via GitHub
• [I] Fix RuntimeWarning about Queue.join not being awaited (tooling-trusted-releases) via GitHub
  • Re: [I] Fix RuntimeWarning about Queue.join not being awaited (tooling-trusted-releases) via GitHub
  • Re: [I] Fix RuntimeWarning about Queue.join not being awaited (tooling-trusted-releases) via GitHub
• [PR] Bump actions/setup-python from 6.1.0 to 6.2.0 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump actions/setup-python from 6.1.0 to 6.2.0 (tooling-trusted-releases) via GitHub
• [I] Remove workaround for pip-audit when pip 26.0 is available (tooling-trusted-releases) via GitHub
  • Re: [I] Remove workaround for pip-audit when pip 26.0 is available (tooling-trusted-releases) via GitHub
• [PR] Binding vote noted in email #616 (tooling-trusted-releases) via GitHub
  • Re: [PR] Binding vote noted in email #616 (tooling-trusted-releases) via GitHub
  • Re: [PR] Binding vote noted in email #616 (tooling-trusted-releases) via GitHub
• [I] Research whether structured ASFQuart permissions can be used more widely in ATR (tooling-trusted-releases) via GitHub
• [I] Improve session testing by using more realising workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Improve session testing by using more realising workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Improve session testing by using more realistic workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Improve session testing by using more realistic workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Improve session testing by using more realistic workflows (tooling-trusted-releases) via GitHub
• [PR] Bump actions/setup-python from 6.1.0 to 6.2.0 (tooling-releases-client) via GitHub
  • Re: [PR] Bump actions/setup-python from 6.1.0 to 6.2.0 (tooling-releases-client) via GitHub
• [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
  • Re: [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
  • Re: [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
  • Re: [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
  • Re: [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
  • Re: [I] Allow PMC members to perform PMC actions (tooling-trusted-releases) via GitHub
• [VOTE] Release Tooling 26.2.2 sbp
  • Re: [VOTE] Release Tooling 26.2.2 sbp
  • [VOTE] [RESULT] Release Apache Tooling 26.2.2 PASSED sbp
• [I] Indicate binding vote in mail sent to [email protected] (tooling-trusted-releases) via GitHub
  • Re: [I] Indicate binding vote in mail sent to [email protected] (tooling-trusted-releases) via GitHub
  • Re: [I] Indicate binding vote in mail sent to [email protected] (tooling-trusted-releases) via GitHub
  • Re: [I] Indicate binding vote in mail sent to [email protected] (tooling-trusted-releases) via GitHub
• [I] Discuss upstreaming of certain components (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss upstreaming of certain components (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss upstreaming of certain components (tooling-trusted-releases) via GitHub
• [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss integrations with ECMA standards (tooling-trusted-releases) via GitHub
• [I] Deploy self hosted GitHub action runners for distribution workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Deploy self hosted GitHub action runners for distribution workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Deploy self hosted GitHub action runners for distribution workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Deploy self hosted GitHub action runners for distribution workflows (tooling-trusted-releases) via GitHub
  • Re: [I] Deploy self hosted GitHub action runners for distribution workflows (tooling-trusted-releases) via GitHub
• [I] Merge env/tooling to production (tooling-trusted-releases) via GitHub
  • Re: [I] Merge env/tooling to production (tooling-trusted-releases) via GitHub
  • Re: [I] Merge env/tooling to production (tooling-trusted-releases) via GitHub
  • Re: [I] Merge env/tooling to production (tooling-trusted-releases) via GitHub
  • Re: [I] Merge env/tooling to production (tooling-trusted-releases) via GitHub
• [I] Make check ignores apply per project, not per committee (tooling-trusted-releases) via GitHub
  • Re: [I] Make check ignores apply per project, not per committee (tooling-trusted-releases) via GitHub
  • Re: [I] Make check ignores apply per project, not per committee (tooling-trusted-releases) via GitHub
• [I] Add release manager storage permissions (tooling-trusted-releases) via GitHub
• [I] Discuss refining permissions for uploading CI builds into ATR (tooling-trusted-releases) via GitHub
• [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • [GH] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
  • Re: [PR] Fix: Mitigate CRLF injection in email headers (Issue #603) (tooling-trusted-releases) via GitHub
• [I] Detect `npm pack` output and allow `package/` as its root directory (tooling-trusted-releases) via GitHub
  • Re: [I] Detect `npm pack` output and allow `package/` as its root directory (tooling-trusted-releases) via GitHub
  • Re: [I] Detect `npm pack` output and allow `package/` as its root directory (tooling-trusted-releases) via GitHub
• [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that Dependabot PRs are checked against the action allow list (tooling-trusted-releases) via GitHub
• [PR] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • [GH] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • Re: [PR] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • Re: [PR] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • Re: [PR] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • Re: [PR] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
• [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
  • Re: [I] Sanitize email header values against CRLF injection (tooling-trusted-releases) via GitHub
• [I] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
  • Re: [I] Limit archive member count to prevent zip bomb attacks (tooling-trusted-releases) via GitHub
• [I] Validate against CR/LF characters in HTTP header values (tooling-trusted-releases) via GitHub
  • Re: [I] Validate against CR/LF characters in HTTP header values (tooling-trusted-releases) via GitHub
  • Re: [I] Validate against CR/LF characters in HTTP header values (tooling-trusted-releases) via GitHub
  • Re: [I] Validate against CR/LF characters in HTTP header values (tooling-trusted-releases) via GitHub
• [I] Apply URL encoding to query parameters and paths (tooling-trusted-releases) via GitHub
  • Re: [I] Apply URL encoding to query parameters and paths (tooling-trusted-releases) via GitHub
  • Re: [I] Apply URL encoding to query parameters and paths (tooling-trusted-releases) via GitHub
  • Re: [I] Apply URL encoding to query parameters and paths (tooling-trusted-releases) via GitHub
  • Re: [I] Apply URL encoding to query parameters and paths (tooling-trusted-releases) via GitHub
• [I] Validate release workflow phase before operations (tooling-trusted-releases) via GitHub
• [I] Limit regex complexity in user-supplied ignore patterns (tooling-trusted-releases) via GitHub
  • Re: [I] Limit regex complexity in user-supplied ignore patterns (tooling-trusted-releases) via GitHub
  • Re: [I] Limit regex complexity in user-supplied ignore patterns (tooling-trusted-releases) via GitHub
• [I] Invalidate all PATs when user account is disabled (tooling-trusted-releases) via GitHub
• [I] Add project-level authorization to /published/ endpoint (tooling-trusted-releases) via GitHub
  • Re: [I] Add project-level authorization to /published/ endpoint (tooling-trusted-releases) via GitHub
• [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce absolute maximum session lifetime for web sessions (tooling-trusted-releases) via GitHub
• [I] Allow files to be excluded on upload (tooling-actions) via GitHub
  • Re: [I] Allow files to be excluded on upload (tooling-actions) via GitHub
  • Re: [I] Allow files to be excluded on upload (tooling-actions) via GitHub
  • Re: [I] Allow files to be excluded on upload (tooling-actions) via GitHub
  • Re: [I] Allow files to be excluded on upload (tooling-actions) via GitHub

• Earlier messages