Azure / Azure/aks-desktop

ossf security best practice: The release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known

Open Beginner friendly
#675 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
102
Forks
25
Avg merge
1d 4h
Merged PRs (30d)
22

Description

- [ ] document this in the release process doc.

Contributor guide

Open the contributing guide

Research direction

Locate the release process document and read its existing guidance on release notes. Add the requested OSSF security best-practice criterion there, including its applicability conditions. Done means the release process documentation clearly covers the criterion and can be checked off.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, release
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.