Issues
- MODELING PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASEMODELING-686Former user
- Identify helm chart version number to use for the releaseMODELING-685Resolved issue: MODELING-685Former user
- Create a Release BranchMODELING-684Resolved issue: MODELING-684Former user
- Complete Key Updates PageMODELING-683Resolved issue: MODELING-683Former user
- Release CandidateMODELING-682Resolved issue: MODELING-682Former user
- PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR MONTREAL RELEASEMODELING-681Resolved issue: MODELING-681Former user
- New utills for R13.MODELING-680Resolved issue: MODELING-680zhuguanyu
- Finalize DocumentationMODELING-679Resolved issue: MODELING-679Former user
- Verify that Pairwise Testing has been CompletedMODELING-678Resolved issue: MODELING-678Former user
- Create a Release BranchMODELING-677Resolved issue: MODELING-677Former user
- Complete Key Updates PageMODELING-676Resolved issue: MODELING-676Former user
- Review license scan issuesMODELING-675Resolved issue: MODELING-675Former user
- Release CandidateMODELING-674Resolved issue: MODELING-674Former user
- Jira CleanupMODELING-673Resolved issue: MODELING-673Former user
- Complete Project TestingMODELING-672Resolved issue: MODELING-672Former user
- Release Sign OffMODELING-671Resolved issue: MODELING-671Former user
- Update the Platform Maturity goals and CII badgingMODELING-670Resolved issue: MODELING-670Former user
- Review and update INFO.yamlMODELING-669Resolved issue: MODELING-669Former user
- Complete preliminary documentationMODELING-668Resolved issue: MODELING-668Former user
- Finish assigning Jira issues to the London ReleaseMODELING-667Resolved issue: MODELING-667Former user
- Start OOM review with updated container imageMODELING-666Resolved issue: MODELING-666Former user
- Feature FreezeMODELING-665Resolved issue: MODELING-665Former user
- Resolve high/highest priority JIRA issuesMODELING-664Resolved issue: MODELING-664Former user
- Review license scan issuesMODELING-663Resolved issue: MODELING-663Former user
- Verify that there are no merge requests older than 36 hoursMODELING-662Resolved issue: MODELING-662Former user
- Verify that test coverage goals have been metMODELING-661Resolved issue: MODELING-661Former user
- Finalized Code SubmissionMODELING-660Resolved issue: MODELING-660Former user
- Color code Impact View Per Component pageMODELING-659Resolved issue: MODELING-659Former user
- Complete release planning templateMODELING-658Resolved issue: MODELING-658Former user
- Review and update the document tracking tableMODELING-657Resolved issue: MODELING-657Former user
- Update documented risksMODELING-656Resolved issue: MODELING-656Former user
- Complete Architectural subcommittee reviewMODELING-655Resolved issue: MODELING-655Former user
- Share data models with Modeling subcommitteeMODELING-654Resolved issue: MODELING-654Former user
- Verify that there are no merge requests older than 36 hoursMODELING-653Resolved issue: MODELING-653Former user
- Communicate API changes to other projectsMODELING-652Resolved issue: MODELING-652Former user
- Specification FreezeMODELING-651Resolved issue: MODELING-651Former user
- Review Code Coverage goal vs. actualsMODELING-650Resolved issue: MODELING-650Former user
- Update the FOSS wiki pageMODELING-649Resolved issue: MODELING-649Former user
- Request an architectural subcommittee reviewMODELING-648Resolved issue: MODELING-648Former user
- Global Requirements ApprovalMODELING-647Resolved issue: MODELING-647Former user
- PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR LONDON RELEASEMODELING-646Resolved issue: MODELING-646Former user
- Kohn Release Note not updatedMODELING-645Former user
- Kohn Release Note not updatedMODELING-644Former user
- fix doc config files in master and kohn branchMODELING-643Resolved issue: MODELING-643Former user
- create kohn branchMODELING-642Resolved issue: MODELING-642Former user
- Enable SBOM on modeling/etsicatalog projectMODELING-641Resolved issue: MODELING-641Former user
- Resolve high/highest priority JIRA issuesMODELING-640Resolved issue: MODELING-640Former user
- Review license scan issuesMODELING-639Resolved issue: MODELING-639Former user
- Verify that there are no merge requests older than 36 hoursMODELING-638Resolved issue: MODELING-638Former user
- Verify that test coverage goals have been metMODELING-637Resolved issue: MODELING-637Former user
50 of 683
MODELING PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR NEW DELHI RELEASE
Details
Assignee
Former userFormer user(Deactivated)Reporter
Amy ZwaricoAmy ZwaricoDue date
May 16, 2024Fix versions
Priority
Highest
Details
Details
Assignee
Former user
Former user(Deactivated)Reporter
Amy Zwarico
Amy ZwaricoDue date
May 16, 2024
Fix versions
Priority
Created February 17, 2024 at 8:57 PM
Updated February 20, 2024 at 5:46 PM
Resolved February 17, 2024 at 8:57 PM
Activity
Show:
Former user February 20, 2024 at 3:56 PM
Perhaps my account just doesn't have the access right... And thanks for checking.
Amy Zwarico February 20, 2024 at 3:40 PMEdited
I was clicked on the link to the spreadsheet and was able to download. Let me investigate further.
I was also able to reach New Delhi Package Updates - Security Vulnerabilities - Confluence (onap.org)
Former user February 20, 2024 at 1:20 PM
, I checked the wiki pages provided in the description, but get "page not found". Could you help provide more details on which repos and packeges are affected by the analysis?
Update the vulnerable direct dependencies following the recommendations of SECCOM in the MODELING tab of the spreadsheet (https://wiki.onap.org/download/attachments/212402352/MasterReportNewDelhi_02-14-24.xlsx?version=2&modificationDate=1708099784000&api=v2) on the https://wiki.onap.org/display/SV/New+Delhi+Package+Updates page in the protected Security Vulnerabilities space.
SECCOM will upload a status spreadsheet each week to help projects track their status.
Submit a LF Ticket for access to the Security Vulnerabilities space.