Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add base64 requirement #4500

Merged
merged 7 commits into from
Oct 29, 2024
Merged

docs: add base64 requirement #4500

merged 7 commits into from
Oct 29, 2024

Conversation

lennessyy
Copy link
Contributor

@lennessyy lennessyy commented Oct 29, 2024

Describe the Change

This PR adds the requirement that CA certificates have to be in base 64 format.

Changed Pages

💻 Add Preview URL for Page

Jira Tickets

🎫 PE-5453

Backports

Can this PR be backported?

  • Yes.

@lennessyy lennessyy added auto-backport Enable backport backport-version-4-3 Backport change to version 4.3 backport-version-4-4 Backport change to version 4.4 backport-version-4-5 Backport changes to the version-4-5 branch. labels Oct 29, 2024
@lennessyy lennessyy marked this pull request as ready for review October 29, 2024 20:52
@lennessyy lennessyy requested a review from a team as a code owner October 29, 2024 20:52
Copy link

netlify bot commented Oct 29, 2024

Deploy Preview for docs-spectrocloud ready!

Name Link
🔨 Latest commit 792158b
🔍 Latest deploy log https://app.netlify.com/sites/docs-spectrocloud/deploys/672168cd6a4dce0008d917d3
😎 Deploy Preview https://deploy-preview-4500--docs-spectrocloud.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/docs-content/security-bulletins/reports/cve-2023-45283.md|64 col 5| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-3715.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-3715.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-3715.md|30 col 87| [Vale.Spelling] Did you really mean 'parameter_transform'?
docs/docs-content/security-bulletins/reports/cve-2022-3715.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-3715.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-45285.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-45285.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-45285.md|30 col 160| [Vale.Terms] Use 'HTTPS' instead of 'https'.
docs/docs-content/security-bulletins/reports/cve-2023-45285.md|30 col 339| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/docs-content/security-bulletins/reports/cve-2023-45285.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7245.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7245.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7245.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7245.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|30 col 68| [Vale.Spelling] Did you really mean 'cgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|30 col 93| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|30 col 141| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|30 col 485| [Vale.Spelling] Did you really mean 'gccgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29405.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|30 col 70| [Vale.Spelling] Did you really mean 'ciphertexts'?
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|30 col 145| [Vale.Spelling] Did you really mean 'ciphertexts'?
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 70| [Vale.Spelling] Did you really mean 'cgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 119| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 151| [Vale.Spelling] Did you really mean 'cgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 176| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 321| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 330| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|30 col 395| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|30 col 8| [Vale.Spelling] Did you really mean 'unsanitized'?
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|30 col 442| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|30 col 1| [Vale.Spelling] Did you really mean 'libpcre'?
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|30 col 233| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|30 col 241| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 68| [Vale.Spelling] Did you really mean 'cgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 93| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 141| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 482| [Vale.Spelling] Did you really mean 'gc'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 489| [Vale.Spelling] Did you really mean 'gccgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|30 col 134| [Vale.Spelling] Did you really mean 'rtree'?
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-27191.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-27191.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|30 col 187| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|30 col 344| [Vale.Spelling] Did you really mean 'callouts'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|31 col 61| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|31 col 222| [Vale.Spelling] Did you really mean 'callouts'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|31 col 251| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|30 col 30| [Vale.Spelling] Did you really mean 'perl'?
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|30 col 125| [Vale.Spelling] Did you really mean 'perl'?
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|30 col 63| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|30 col 99| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|30 col 333| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|30 col 683| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|30 col 736| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|30 col 105| [Vale.Spelling] Did you really mean 'unparsable'?
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|30 col 143| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|30 col 238| [Vale.Spelling] Did you really mean 'unparsable'?
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|30 col 225| [Vale.Spelling] Did you really mean 'Rego'?
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|30 col 1| [Vale.Spelling] Did you really mean 'Libgcrypt'?
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|30 col 153| [Vale.Spelling] Did you really mean 'mpi_powm'?
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|30 col 32| [Vale.Spelling] Did you really mean 'Kerberos'?
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|30 col 353| [Vale.Spelling] Did you really mean 'Kerberos'?
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|30 col 1| [Vale.Spelling] Did you really mean 'ncurses'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|30 col 45| [Vale.Spelling] Did you really mean 'setuid'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|30 col 155| [Vale.Spelling] Did you really mean 'terminfo'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

@@ -203,7 +203,7 @@ The `stylus.site` blocks accept the following parameters.

| Parameter | Description | Default |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- |
| `stylus.site.caCerts` | The Secure Sockets Layer (SSL) certificate authority (CA) certificates. | |
| `stylus.site.caCerts` | The Secure Sockets Layer (SSL) certificate authority (CA). The certificates must be base64-encoded. | |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[spectrocloud-docs-internal.acronym] Use title case to define the acronym '(CA)'.


## Initial Publication

10/4/2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.


## Last Update

10/4/2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.


## Revision History

1. 10/11/2024: Advisory assigned with HIGH severity
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.

## Revision History

1. 10/11/2024: Advisory assigned with HIGH severity
2. 10/18/2024: Advisory is now impacting.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

6. 10/18/2024: Advisory is now impacting.
7. 10/18/2024: Advisory is no longer impacting.
8. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
9. 10/18/2024: Advisory is now impacting.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

7. 10/18/2024: Advisory is no longer impacting.
8. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
9. 10/18/2024: Advisory is now impacting.
10. 10/18/2024: Advisory is no longer impacting.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

8. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
9. 10/18/2024: Advisory is now impacting.
10. 10/18/2024: Advisory is no longer impacting.
11. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

9. 10/18/2024: Advisory is now impacting.
10. 10/18/2024: Advisory is no longer impacting.
11. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
12. 10/18/2024: Advisory is now impacting.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

10. 10/18/2024: Advisory is no longer impacting.
11. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used in the product.
12. 10/18/2024: Advisory is now impacting.
13. 10/18/2024: Advisory is no longer impacting.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remaining comments which cannot be posted as a review comment to avoid GitHub Rate Limit

vale

docs/docs-content/security-bulletins/reports/cve-2023-29402.md|31 col 86| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|31 col 95| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|32 col 39| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/docs-content/security-bulletins/reports/cve-2023-29402.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|29 col 70| [Vale.Spelling] Did you really mean 'ciphertexts'?
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|30 col 28| [Vale.Spelling] Did you really mean 'ciphertexts'?
docs/docs-content/security-bulletins/reports/cve-2024-0553.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|29 col 8| [Vale.Spelling] Did you really mean 'unsanitized'?
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|32 col 99| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41716.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-0567.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|29 col 1| [Vale.Spelling] Did you really mean 'libpcre'?
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-20838.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|31 col 1| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|31 col 9| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2023-39323.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|29 col 68| [Vale.Spelling] Did you really mean 'cgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|29 col 93| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|30 col 27| [spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|33 col 19| [Vale.Spelling] Did you really mean 'gc'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|33 col 26| [Vale.Spelling] Did you really mean 'gccgo'?
docs/docs-content/security-bulletins/reports/cve-2023-29404.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|30 col 18| [Vale.Spelling] Did you really mean 'rtree'?
docs/docs-content/security-bulletins/reports/cve-2019-8457.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-27191.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-27191.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|30 col 66| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|31 col 102| [Vale.Spelling] Did you really mean 'callouts'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|31 col 115| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|32 col 98| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|36 col 61| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|37 col 107| [Vale.Spelling] Did you really mean 'callouts'?
docs/docs-content/security-bulletins/reports/cve-2023-46129.md|38 col 18| [Vale.Spelling] Did you really mean 'nkeys'?
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-1304.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|29 col 30| [Vale.Spelling] Did you really mean 'perl'?
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|30 col 4| [Vale.Spelling] Did you really mean 'perl'?
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-47038.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|29 col 63| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|29 col 99| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|31 col 93| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|34 col 93| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|35 col 46| [Google.Quotes] Commas and periods go inside quotation marks.
docs/docs-content/security-bulletins/reports/cve-2022-41720.md|55 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|52 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2017-7246.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|29 col 105| [Vale.Spelling] Did you really mean 'unparsable'?
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|30 col 28| [Vale.Terms] Use 'HTTP' instead of 'http'.
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|31 col 4| [Vale.Spelling] Did you really mean 'unparsable'?
docs/docs-content/security-bulletins/reports/cve-2022-2880.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|30 col 106| [Vale.Spelling] Did you really mean 'Rego'?
docs/docs-content/security-bulletins/reports/cve-2024-8260.md|51 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/15/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|29 col 1| [Vale.Spelling] Did you really mean 'Libgcrypt'?
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|30 col 39| [Vale.Spelling] Did you really mean 'mpi_powm'?
docs/docs-content/security-bulletins/reports/cve-2021-33560.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|29 col 32| [Vale.Spelling] Did you really mean 'Kerberos'?
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|32 col 1| [Vale.Spelling] Did you really mean 'Kerberos'?
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2018-5709.md|55 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|17 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|21 col 1| [Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|29 col 1| [Vale.Spelling] Did you really mean 'ncurses'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|29 col 45| [Vale.Spelling] Did you really mean 'setuid'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|30 col 36| [Vale.Spelling] Did you really mean 'terminfo'?
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|53 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.
docs/docs-content/security-bulletins/reports/cve-2023-29491.md|54 col 4| [Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

5. 10/18/2024: Official summary added
6. 10/18/2024: Advisory is now impacting.
7. 10/18/2024: Advisory is no longer impacting.
8. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

in the product.
9. 10/18/2024: Advisory is now impacting.
10. 10/18/2024: Advisory is no longer impacting.
11. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.

in the product.
12. 10/18/2024: Advisory is now impacting.
13. 10/18/2024: Advisory is no longer impacting.
14. 10/18/2024: Official summary revised: This CVE is non impacting as the impacting symbol and/or function is not used
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/18/2024'.


## Initial Publication

10/4/2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.


## Last Update

10/4/2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/4/2024'.


## Last Update

10/11/2024
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Google.DateFormat] Use 'July 31, 2016' format, not '10/11/2024'.


## NIST CVE Summary

The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'cgo'?

## NIST CVE Summary

The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when
running a go program which uses cgo. This may occur when running an untrusted module which contains directories with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.

## NIST CVE Summary

The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when
running a go program which uses cgo. This may occur when running an untrusted module which contains directories with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'cgo'?

## NIST CVE Summary

The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when
running a go program which uses cgo. This may occur when running an untrusted module which contains directories with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[spectrocloud-docs-internal.ableism] Avoid using ableism terms. Use 'operating' instead of 'running'.

@lennessyy lennessyy merged commit ab546a7 into master Oct 29, 2024
15 checks passed
@lennessyy lennessyy deleted the PE-5453 branch October 29, 2024 23:36
vault-token-factory-spectrocloud bot pushed a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)
vault-token-factory-spectrocloud bot pushed a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)
vault-token-factory-spectrocloud bot pushed a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)
@vault-token-factory-spectrocloud
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
version-4-3
version-4-4
version-4-5

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

vault-token-factory-spectrocloud bot added a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)

Co-authored-by: Lenny Chen <[email protected]>
vault-token-factory-spectrocloud bot added a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)

Co-authored-by: Lenny Chen <[email protected]>
vault-token-factory-spectrocloud bot added a commit that referenced this pull request Oct 29, 2024
* docs: add clarification

* docs: fix font awesome

* docs: style guide

* docs: fix font awesome

* docs: add prereq

* docs: fix typo

---------

Co-authored-by: Lenny Chen <[email protected]>
(cherry picked from commit ab546a7)

Co-authored-by: Lenny Chen <[email protected]>
@vault-token-factory-spectrocloud
Copy link
Contributor

🎉 This issue has been resolved in version 4.5.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Enable backport backport-version-4-3 Backport change to version 4.3 backport-version-4-4 Backport change to version 4.4 backport-version-4-5 Backport changes to the version-4-5 branch. released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants