Open sharath-srikanth-chellappa opened 2 days ago
What is the process here ? Since we didn't have many High Severity CVEs with a patch available, Jon mentioned we work on medium severity. My assumption was to have this merged to fasttrack/2.0 and not another branch. Do let me know the correct strategy here.
@PawelWMS
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./SPECS/LICENSES-AND-NOTICES/data/licenses.json
,./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md
,./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
Upgrading emacs version to 29.4 to address CVE.
Change Log
Does this affect the toolchain?
NO
Associated issues
xxxx
Links to CVEs
Test Methodology