chore: update changelog for v1.0.17

[github-actions]

This PR updates the changelog for release v1.0.17.

Summary by Sourcery

Publish the v1.0.17 changelog with dependency updates, vulnerability fixes, and Dockerfile cleanup improvements.

Bug Fixes:

• Document Dockerfile cleanup fixes and dependency and image vulnerability remediation included in v1.0.17.
• Record security-related dependency upgrades for ESLint and Vue TypeScript configuration packages.

Enhancements:

• Add the v1.0.17 release entry and summarize its dependency, documentation, and maintenance changes.

Documentation:

• Update the changelog with the v1.0.17 release notes.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates CHANGELOG.md to document the v1.0.17 release dated 2026-09-02, separating dependency/documentation changes from security and maintenance fixes while preserving traceability to the related commits.

File-Level Changes

Change	Details	Files
Adds the v1.0.17 release section to the changelog with its release date and categorized change history.	Records the nginx dependency upgrade and v1.0.16 changelog update. Records Dockerfile cleanup, dependency, Docker image, and ESLint-related vulnerability fixes. Includes contributor, automation, and commit references for each entry.	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[kburger]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="10" />
<code_context>

 ## [Unreleased]

+## [v1.0.17] - 2026-09-02
+
+### Changed
</code_context>
<issue_to_address>
**nitpick:** The new `## [v1.0.17]` heading has no matching `[v1.0.17]` reference definition at the bottom of the file, so Markdown renders it as plain text instead of a link. The existing `[1.17.0]` definition also has a different label and points to the unrelated `v1.17.0` tag.

**Suggested fix:** Add a matching reference such as `[v1.0.17]: /../../tree/v1.0.17` (or the intended release URL), and correct the mismatched existing reference if necessary.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

nitpick: The new ## [v1.0.17] heading has no matching [v1.0.17] reference definition at the bottom of the file, so Markdown renders it as plain text instead of a link. The existing [1.17.0] definition also has a different label and points to the unrelated v1.17.0 tag.

Suggested fix: Add a matching reference such as [v1.0.17]: /../../tree/v1.0.17 (or the intended release URL), and correct the mismatched existing reference if necessary.