Repository navigation
ci: move FOSSA template to stable/uipath.security.scans-v3 - #1970
Merged
Merged
Conversation
andreitava-uip
approved these changes
Nov 2, 2026
russellboley-uipath
force-pushed
the
chore/fossa-stable-scans-branch
branch
from
November 5, 2026 17:39
07a4b1f to
49f391c
Compare
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Inaccessible template references and linked PRs prevented verification of parameter compatibility and repository-specific FOSSA-OIDC authorization.
No open issues 🎉
What changed in this PR
Updates the security pipeline’s shared FOSSA template reference to the stable v3 branch, adopting the template’s OIDC sign-in and vault firewall support.
Changes:
- Replaces the pinned
uipath.security.fossa.3.0.17tag withstable/uipath.security.scans-v3. - Allows future stable template updates without ref bumps; pipeline parameters remain unchanged.
| File | Description |
|---|---|
.pipelines/security-scans.yml |
Points the fossa repository resource to the stable security-scans v3 branch. |
Review effort: Balanced
The FOSSA template on refs/heads/stable/uipath.security.scans-v3 signs in to FOSSA through the FOSSA-OIDC workload identity service connection instead of the vault's FossaApiKey. No caller parameter changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
russellboley-uipath
force-pushed
the
chore/fossa-stable-scans-branch
branch
from
November 5, 2026 17:42
49f391c to
2f87ea2
Compare
russellboley-uipath
changed the title
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
resources: repositories: - repository: <alias> name: UiPath/AzurePipelinesTemplates - ref: refs/tags/uipath.security.fossa.<old> # or uipath.security.scans.<old> + ref: refs/heads/stable/uipath.security.scans-v3.pipelines/security-scans.ymlfossaSecurity/fossa.steps.ymlon the stable branch signs in to FOSSA through theFOSSA-OIDCworkload identity service connection (shared with every Azure DevOps project under that name), so the long-livedFossaApiKey/FossaApiIntegrationKeyvault secrets are no longer read (AzurePipelinesTemplates#2539). It also toggles thedevopsprodauthtokenswekvfirewall for the agent with Key Vault access 1.2.8, which older tags cannot do now that the vault is firewalled (INC-522). The stable branch follows the testeduipath.security.fossareleases, so this pipeline stops needing ref bumps. No parameter changes are needed.Evidence
FossaApiKeyfrom the firewalled vault, which fails from Microsoft-hosted agents once the toggle cannot open it.Merge Danger
Door: two-way
Revert the ref to roll back.
Blast Radius: security scans
Only the FOSSA/security scan stages of the pipelines listed above.
🤖 Generated with Claude Code