dev  

Messages by Thread

• • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
  • Re: [I] Improve error reporting when /resolve/tabulated data is unavailable (tooling-trusted-releases) via GitHub
• [I] Substitute the release checklist before including into an email body (tooling-trusted-releases) via GitHub
  • Re: [I] Substitute the release checklist before including into an email body (tooling-trusted-releases) via GitHub
  • Re: [I] Substitute the release checklist before including into an email body (tooling-trusted-releases) via GitHub
• Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
• Re: [I] Deleting a file from a release causes all files to be re-scanned (tooling-trusted-releases) via GitHub
  • Re: [I] Deleting a file from a release causes all files to be re-scanned (tooling-trusted-releases) via GitHub
• [I] Reporter features from comdev (tooling-trusted-releases) via GitHub
• [PR] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • [GH] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • [GH] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • [GH] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • [GH] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • Re: [PR] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • Re: [PR] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • Re: [PR] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
  • Re: [PR] Add GitHub Actions PR labeler for automatic labeling (tooling-trusted-releases) via GitHub
• [PR] Bump actions/checkout from 6.0.0 to 6.0.1 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump actions/checkout from 6.0.0 to 6.0.1 (tooling-trusted-releases) via GitHub
• [PR] Bump actions/cache from 4.3.0 to 5.0.1 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump actions/cache from 4.3.0 to 5.0.1 (tooling-trusted-releases) via GitHub
• [PR] Bump astral-sh/setup-uv from 6.4.3 to 7.1.6 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump astral-sh/setup-uv from 6.4.3 to 7.1.6 (tooling-trusted-releases) via GitHub
• [PR] Bump advanced-security/dismiss-alerts from 2.0.1 to 2.0.2 (tooling-trusted-releases) via GitHub
  • Re: [PR] Bump advanced-security/dismiss-alerts from 2.0.1 to 2.0.2 (tooling-trusted-releases) via GitHub
• Introduction: Ravi Kumar (new contributor) Ravi Kumar
• Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
  • Re: [I] We could add the pull request labeler an action for automatically labelling pull requests (tooling-trusted-releases) via GitHub
• [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
  • Re: [I] Project features from comdev website (tooling-trusted-releases) via GitHub
• Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
• Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document which project options affect file checks (tooling-trusted-releases) via GitHub
• Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
  • Re: [I] New compose project options for license check excludes (tooling-trusted-releases) via GitHub
• [I] DOAP files in port of projects.apache.org (tooling-trusted-releases) via GitHub
  • Re: [I] DOAP files in port of projects.apache.org (tooling-trusted-releases) via GitHub
  • Re: [I] DOAP files in port of projects.apache.org (tooling-trusted-releases) via GitHub
  • Re: [I] DOAP files in port of projects.apache.org (tooling-trusted-releases) via GitHub
• Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
  • Re: [I] Discuss possible DOAP workflows and UX (tooling-trusted-releases) via GitHub
• Re: [I] Export data through Transparency Exchange API (tooling-trusted-releases) via GitHub
  • Re: [I] Export data through Transparency Exchange API (tooling-trusted-releases) via GitHub
  • Re: [I] Export data through Transparency Exchange API (tooling-trusted-releases) via GitHub
• Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
  • Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
• [I] https://github.com/apache/tooling-docs.git (tooling-docs) via GitHub
  • Re: [I] https://github.com/apache/tooling-docs.git (tooling-docs) via GitHub
• [PR] Pull previous SBOM results into the report and highlight new/changed … (tooling-trusted-releases) via GitHub
  • Re: [PR] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • Re: [PR] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • [GH] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
  • Re: [PR] Pull previous SBOM results into the report and highlight new/changed vulnerabilities/licenses (tooling-trusted-releases) via GitHub
• Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
  • Re: [I] Require two approvals for important actions (tooling-trusted-releases) via GitHub
• Re: [I] Root directory not matching ? Should we always use -source ? (tooling-trusted-releases) via GitHub
  • Re: [I] Root directory not matching ? Should we always use -source ? (tooling-trusted-releases) via GitHub
  • Re: [I] Root directory not matching ? Should we always use -source ? (tooling-trusted-releases) via GitHub
  • Re: [I] Root directory not matching ? Should we always use -source ? (tooling-trusted-releases) via GitHub
• [I] Make UX when an unauthorized users visit the vote page when the release is not in that phase (tooling-trusted-releases) via GitHub
  • Re: [I] Make UX when an unauthorized users visit the vote page when the release is not in that phase (tooling-trusted-releases) via GitHub
  • Re: [I] Fix UX when an unauthorized user visits the vote page when the release is no longer in that phase (tooling-trusted-releases) via GitHub
  • Re: [I] Fix UX when an unauthorized user visits the vote page when the release is no longer in that phase (tooling-trusted-releases) via GitHub
• Re: [I] Always show the current release phase status even on outdated phase pages (tooling-trusted-releases) via GitHub
  • Re: [I] Always show the current release phase status even on outdated phase pages (tooling-trusted-releases) via GitHub
• Re: [I] Ability to record +1 by release manager (tooling-trusted-releases) via GitHub
  • Re: [I] Ability to record +1 by release manager (tooling-trusted-releases) via GitHub
  • Re: [I] Ability to record +1 by release manager (tooling-trusted-releases) via GitHub
  • Re: [I] Ability to record +1 by release manager (tooling-trusted-releases) via GitHub
• Re: [I] Improve the SBOM license scanner (tooling-trusted-releases) via GitHub
  • Re: [I] Improve the SBOM license scanner (tooling-trusted-releases) via GitHub
  • Re: [I] Improve the SBOM license scanner (tooling-trusted-releases) via GitHub
• Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
• Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
  • Re: [I] Clarify and constrain permitted ASF TLP version numbers (tooling-trusted-releases) via GitHub
• Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases) via GitHub
• Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
  • Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
  • Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
  • Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
  • Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
  • Re: [I] Release catalog model (tooling-trusted-releases) via GitHub
• Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
• Re: [I] Make the audit log efficient to query, or the database tamper resistant (tooling-trusted-releases) via GitHub
  • Re: [I] Make the audit log efficient to query, or the database tamper resistant (tooling-trusted-releases) via GitHub
• [I] Add commands to sign and verify artifacts (tooling-releases-client) via GitHub
• Re: [I] 'discuss thread' leading up to a release (tooling-trusted-releases) via GitHub
  • Re: [I] 'discuss thread' leading up to a release (tooling-trusted-releases) via GitHub
• Re: [I] Resolve the design of emptiness and nullability for form types (tooling-trusted-releases) via GitHub
  • Re: [I] Resolve the design of emptiness and nullability for form types (tooling-trusted-releases) via GitHub
• Re: [I] Link from RAT check failure to local reproduction instructions (tooling-trusted-releases) via GitHub
  • Re: [I] Link from RAT check failure to local reproduction instructions (tooling-trusted-releases) via GitHub
  • Re: [I] Link from RAT check failure to local reproduction instructions (tooling-trusted-releases) via GitHub
• [I] Allow error check results to be turned into a TODO list (tooling-trusted-releases) via GitHub
  • Re: [I] Allow error check results to be turned into a TODO list (tooling-trusted-releases) via GitHub
  • Re: [I] Allow error check results to be turned into a TODO list (tooling-trusted-releases) via GitHub
  • Re: [I] Allow error check results to be turned into a TODO list (tooling-trusted-releases) via GitHub
• Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
  • Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
  • Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
  • Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
  • Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
  • Re: [I] Should convenience packages be rat-checked (tooling-trusted-releases) via GitHub
• [I] Allow users to configure between lightweight and RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Allow users to configure between lightweight and RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Allow users to configure between lightweight and RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Allow users to configure between lightweight and RAT checks (tooling-trusted-releases) via GitHub
  • Re: [I] Allow users to configure between lightweight and RAT checks (tooling-trusted-releases) via GitHub
• [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub
  • Re: [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub
  • Re: [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub
  • Re: [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub
  • Re: [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub
  • Re: [I] Add a tutorial explaining how to sign artifacts using OpenPGP (tooling-trusted-releases) via GitHub

• Earlier messages
• Later messages