release-notes.html

<h1 id="foo">FOO</h1>
<h2 id="FOO_1.0.0-8">1.0.0-8</h2>
<h3 id="FOO_1.0.0-8_Prelude">Prelude</h3>
<p>Replace this text with content to appear at the top of the section for this release. All of the prelude content is merged together and then rendered separately from the items listed in other parts of the file, so the text needs to be worded so that both the prelude and the other items make sense when read independently. This may mean repeating some details. Not every release note requires a prelude. Usually only notes describing major features or adding release theme details should have a prelude.</p>
<h3 id="FOO_1.0.0-8_New Features">New Features</h3>
<ul>
<li>List new features here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Known Issues">Known Issues</h3>
<ul>
<li>List known issues here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Upgrade Notes">Upgrade Notes</h3>
<ul>
<li>List upgrade notes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Deprecation Notes">Deprecation Notes</h3>
<ul>
<li>List deprecations notes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Critical Issues">Critical Issues</h3>
<ul>
<li>Add critical notes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Security Issues">Security Issues</h3>
<ul>
<li>Add security notes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<ul>
<li>CVE-2022-39286 high not_affected no further information</li>
</ul>
<ul>
<li>GHSA-m678-f26j-3hrp high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2022-29244 high in_triage no further information</li>
</ul>
<ul>
<li>GHSA-hj9c-8jmm-8c52 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2021-27478 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2021-27482 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2021-27498 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2021-27500 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2015-20107 high not_affected no further information</li>
</ul>
<ul>
<li>CVE-2022-37454 critical not_affected we are not affected by this</li>
</ul>
<ul>
<li>CVE-2022-42919 high in_triage no further information</li>
</ul>
<ul>
<li>CVE-2022-45061 high in_triage no further information</li>
</ul>
<h3 id="FOO_1.0.0-8_Bug Fixes">Bug Fixes</h3>
<ul>
<li>Add normal bug fixes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>
<h3 id="FOO_1.0.0-8_Other Notes">Other Notes</h3>
<ul>
<li>Add other notes here, or remove this section. All of the list items in this section are combined when the release notes are rendered, so the text needs to be worded so that it does not depend on any information only available in another section, such as the prelude. This may mean repeating some details.</li>
</ul>