Add server release notes

[kunalmohan-work]

• Have you updated CHANGELOG.md with relevant non-documentation file changes?
• Have you updated the documentation for this change?

---

[Copilot]

🟡 Changes recommended

The newly added release notes content has several objective consistency/formatting issues (heading capitalization, punctuation, inline code formatting, and trailing whitespace) that should be corrected before merging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds Livepatch Server release notes entries to the documentation so readers can track server changes across recent versions.

Changes:

• Added a new release notes entry for v2.3.0 (features, optimizations, deprecations).
• Added release notes entries for v2.0.0 and v1.21.3 (features and bug fixes).

File summaries

File	Description
docs/release-notes/server/index.md	Adds new server version release note sections and bullets.

Review details

Suppressed comments (1)

docs/release-notes/server/index.md:48

• The “Bug Fixes:” heading includes a trailing colon and the bullet line has trailing whitespace; align this heading with the file’s “Bug fixes” style and remove trailing spaces.

### Bug Fixes:

- Fixed config parsing logic which caused invalid handling of nested config struct pointers. 

• Files reviewed: 1/1 changed files
• Comments generated: 4
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🔵 Needs a closer look

The newly added release note sections contain avoidable style inconsistencies (headings/tense/formatting) and trailing whitespace that should be cleaned up before approval.

Review details

Suppressed comments (7)

Previously missed (1) — in code that hasn't changed since the last review.

docs/release-notes/server/index.md:46

• This heading uses inconsistent capitalization and includes an unnecessary colon; please normalize to the same “Bug fixes” style used elsewhere on the page.

docs/release-notes/server/index.md:25

• These bullets read like imperatives and contain a bare function name; for release notes, use past tense and format identifiers as code for clarity (and hyphenate “parallel-safe”).

- Mark the comparable_patch_version function as parallel safe for faster patch version lookups.

### Deprecations

- Deprecate SSO Macaroon issuance, SSO Macaroon based admin auth and SSO Auth config from the server.

docs/release-notes/server/index.md:29

• Heading capitalization is inconsistent with the rest of this page (most sections use “New features”). Consider normalizing to match the existing style.

### New Features

docs/release-notes/server/index.md:35

• Heading capitalization is inconsistent with other “Bug fixes” sections on this page; please normalize casing.

### Bug Fixes

docs/release-notes/server/index.md:31

• Remove the trailing whitespace at end of this list item to avoid noisy diffs / markdown lint failures.

- Removed the `/api/auth-tokens` endpoint. 

docs/release-notes/server/index.md:44

• These list items have trailing whitespace; please remove it to keep markdown clean and avoid lint noise.

- Added support for new ping types sent by client machines which improves monitoring of client machines. 
- Fixed CVE data is now denormalized for faster database lookups. 

docs/release-notes/server/index.md:48

• Remove the trailing whitespace at end of this list item to avoid noisy diffs / markdown lint failures.

- Fixed config parsing logic which caused invalid handling of nested config struct pointers. 

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Lite

[Copilot]

🟡 Changes recommended

The release notes and wordlist updates introduce consistency/maintainability issues that should be corrected before merging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (2)

Previously missed (1) — in code that hasn't changed since the last review.

docs/release-notes/server/index.md:21

• The optimization note is written as an internal implementation detail (mentions a specific function name) rather than a user-visible change; release notes are more useful when they describe the impact (e.g., improved lookup performance) without requiring knowledge of code internals.

This issue also appears on line 45 of the same file.

docs/release-notes/server/index.md:47

• This heading is inconsistent with the other release note sections in the same file ("### Bug fixes" is used elsewhere) and the trailing colon makes it stand out. Aligning it improves scanability and consistency.

### Bug Fixes:

- Fixed config parsing logic which caused invalid handling of nested config struct pointers. 

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

[Copilot]

🔵 Needs a closer look

The new release-note text has terminology/service-name inconsistencies with existing patch storage documentation and there’s a heading/whitespace inconsistency that should be corrected.

Review details

Suppressed comments (2)

Previously missed (2) — in code that hasn't changed since the last review.

docs/release-notes/server/index.md:17

• The release note uses a new term (“Public Cloud Stores”) and some service names that don’t match the existing patch storage reference (e.g., “Azure Blob Store” vs “Azure Blob Storage”, “Oracle Cloud Storage” vs OCI Object Storage). Aligning terminology with the reference page will avoid confusing readers and keep naming consistent.
  docs/release-notes/server/index.md:48
• This heading is inconsistent with the rest of the page (“Bug fixes” elsewhere) and the bullet has trailing whitespace plus slightly awkward phrasing. Normalizing the heading and tightening the sentence improves consistency and avoids lint issues from trailing spaces.

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Lite