Latest updates added to changelog

[pajef-ipo]

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other: <!-- Please describe: -->

What is the current behavior?

Issue Number: #3272

What is the new behavior?

Changelog that shows on Extension's page on VSCode indicates latest updates.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

I did this manually, but it seems to be automatable; probably easy for an LLM agent to parse the commit tree and make abbreviated list of changes

[pantoaibot]

Do you want me to review this PR? Please comment /review .

[pajef-ipo]

/review

[pantoaibot]

PR Summary:

Add new 5.7.10 changelog entry and housekeeping lines; documents CORS behavior change, new response-headers feature, and other minor updates.

• Added version 5.7.10 entry describing:
  • fix: clarify and update CORS settings in docs and code; CORS is now configurable and disabled by default (behavioral change — may affect consumers that relied on CORS being enabled).
  • feat: ability to set additional response headers (feat: add ability to set additional response headers #3198).
  • fix: update .gitignore to exclude node_modules and virtual environment directories.
  • minor: grammar update in appModel.ts ([Bug]: updated grammar in appModel.ts #2568).
• Inserted a placeholder row for "5.7.9 and earlier" asking to populate changelog from commit messages.
• Reordered/retained the previous 5.6.1 entry below the new entries.

Reviewed by Panto AI

[pantoaibot]

[REFACTORING] The new 5.7.10 table cell (line 4) is very dense and uses HTML entities (—) and multiple
tags inside a table cell. That makes the Markdown hard to read and brittle for CI/consumers. Actionable suggestions: 1) Replace the HTML
and — fragments with a simple Markdown bullet list or move the detailed bullet list below the table as the release notes body. 2) Use past-tense consistently (e.g. "Made CORS configurable..." instead of "Make CORS configurable..."). 3) Keep the table cell concise (one-line summary) and link to a longer release-note section for details so the table remains render-friendly.

# Changelog
| Version | Date | Changelog |
|---|---|---|
|5.7.10|27.02.2026|CORS defaults clarified and made configurable; ignore patterns and headers support updated. See details below.|
|5.7.9 and earlier|-|See previous entries below.|
|5.6.1|17.04.19|Fixed `Extension host terminated unexpectedly` *[[#431](https://github.com/ritwickdey/vscode-live-server/issues/431)]*

### 5.7.10
- fix: clarify CORS default behavior and configuration in documentation and code
- fix: update `.gitignore` to exclude `node_modules` and virtual environment directories
- fix: made CORS configurable in the extension settings and disabled it by default ([#3257](https://github.com/ritwickdey/vscode-live-server/issues/3257))
- feat: add ability to set additional response headers ([#3198](https://github.com/ritwickdey/vscode-live-server/issues/3198))
- chore: update grammar in `appModel.ts` ([#2568](https://github.com/ritwickdey/vscode-live-server/issues/2568))

[pantoaibot]

[REFACTORING] The row for "5.7.9 and earlier" (line 5) contains a FIXME placeholder instructing to "please update with changelog data from the commit messages". Do not merge/publish a changelog with this placeholder. Actionable steps: replace the FIXME with the actual aggregated changes or remove the row entirely if you can't populate it now. If you intend to fill it later, use a draft branch rather than shipping a placeholder in main.

|5.7.10|27.02.2026|CORS defaults clarified and made configurable; ignore patterns and headers support updated. See details below.|
|5.6.1|17.04.19|Fixed `Extension host terminated unexpectedly` *[[#431](https://github.com/ritwickdey/vscode-live-server/issues/431)]*

[pantoaibot]

Reviewed up to commit:5d9af0b71f2020f80d7faa81b5c70b9a9570951d

Additional Suggestion

Others

- Cross-check the changelog wording about CORS (disabled by default / configurable) with docs and README: docs/settings.md and package.json indicate CORS default=false, README currently contains ambiguous phrasing "CORS Enabled [(disabled by default)]". Actionable: update README/docs to use consistent wording (e.g. "CORS disabled by default; enable via liveServer.settings.cors or use liveServer.settings.headers for fine-grained control") and ensure the changelog's phrasing matches the final behavior shipped in code (headers, package settings, and the live-server implementation).

<!-- README.md Features section -->
* CORS support (disabled by default). Enable via `liveServer.settings.cors: true` or, preferably, configure specific CORS/other headers via `liveServer.settings.headers`.

<!-- CHANGELOG.md 5.7.10 row/body wording -->
|5.7.10|27.02.2026|Clarified CORS default (disabled) and configuration options; added headers support; updated ignore patterns.|

### 5.7.10
- fix: clarify that CORS is disabled by default and document how to enable it via `liveServer.settings.cors` ([#3257](https://github.com/ritwickdey/vscode-live-server/issues/3257))
- fix: document recommended usage of `liveServer.settings.headers` for fine-grained header and CORS control
- fix: update `.gitignore` / ignore settings to exclude `node_modules` and common virtual environment directories
- feat: add `liveServer.settings.headers` to configure additional response headers ([#3198](https://github.com/ritwickdey/vscode-live-server/issues/3198))

Reviewed by Panto AI