-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Disable SBOM in Non-Production ADO Pipelines #14775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. Closes microsoft#14774
chiaramooney
approved these changes
Jun 12, 2025
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.79. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.78. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.77. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.76. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.75. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this pull request
Jun 12, 2025
This PR backports PR microsoft#14775 to RNW 0.74. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes microsoft#14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 13, 2025
This PR backports PR #14775 to RNW 0.79. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 13, 2025
This PR backports PR #14775 to RNW 0.76. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 13, 2025
This PR backports PR #14775 to RNW 0.78. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 13, 2025
This PR backports PR #14775 to RNW 0.75. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 13, 2025
This PR backports PR #14775 to RNW 0.77. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
jonthysell
added a commit
that referenced
this pull request
Jun 16, 2025
This PR backports PR #14775 to RNW 0.74. ## Description This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow. Closes #14774 ### What Removed SBOM tasks that ran in CI/PR. ## Screenshots N/A ## Testing N/A ## Changelog Should this change be included in the release notes: _no_
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Compliance
Workstream: ES Compliance SFI
Provide regular ES infrastructure and ensure RNW meets internal security and compliance requirements
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This removes the creation of SBOM manifests in our CI/PR pipelines, as it is no longer possible to create them unsigned.
Type of Change
Why
Our non-production ADO pipelines (CI/PR) do not need to create SBOMS, but we were doing so anyway. But since they didn't have permission to sign the SBOMs, we disabled that and create unsigned ones instead. This no longer works, and so all CI/PR are failing, blocking all codeflow.
Closes #14774
What
Removed SBOM tasks that ran in CI/PR.
Screenshots
N/A
Testing
N/A
Changelog
Should this change be included in the release notes: no
Microsoft Reviewers: Open in CodeFlow