Conversation
Add patch-backport manifest json Update security-scan to allow ignoring backported patches
sachinh-amazon
approved these changes
Feb 17, 2026
skazantsev
approved these changes
Feb 17, 2026
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
3 participants
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.
Issue
V2104769527
Description of Changes
Added backport manifest json at
patches/backported-patches.jsonAdded a mechanism to security-scan workflow to ignore findings with IDs which have a record in the backport manifest json file
Backported high severity findings from the Code-OSS repository (
GHSA-3pwg-f3hj-wp8p/CVE-2026-21523)CVE-2026-21523describes multiple findings, of which only one is applicable for a Code Editor use case:Testing
It is a one-line backport, no additional testing has been performed other than running the GitHub Actions to verify that the scan ignores the backported finding (as expected), and that the backported patch could be properly applied.
Security scan workflow run (on fork): https://github.com/azmkercso/code-editor/actions/runs/22104274205
Build workflow run (on fork): https://github.com/azmkercso/code-editor/actions/runs/22104494664
Screenshots/Videos
N/A
Additional Notes
N/A
Backporting
Yes, a separate PR is being made for all release branches (
1.0,1.1,main)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.