docs(changelog): update changelog for v1.10.0 release

[z0ffy]

Summary by Sourcery

Documentation:

• Document the v1.10.0 release, including new worker support, related fixes, and refactoring in the changelog.

[sourcery-ai]

Reviewer's Guide

Updates the changelog for the v1.10.0 release, including adjusting the Unreleased comparison range and documenting new worker support, fixes, and refactors.

File-Level Changes

Change	Details	Files
Update Unreleased section to compare from v1.10.0 instead of v1.9.0.	Change Unreleased GitHub compare link base tag from v1.9.0 to v1.10.0. Ensure Unreleased section now reflects changes after the v1.10.0 release.	CHANGELOG.md
Add a new v1.10.0 release section documenting features, fixes, and refactors.	Introduce v1.10.0 heading with compare link and release date. List high-level release notes for version bump, worker support, improved Nuxt detection, and changelog/workflow updates. Add 'New Features' subsection describing Web Worker obfuscation support and options. Add 'Fixes' subsection noting handling of worker.plugins for obfuscation. Add 'Refactoring and Updates' subsection detailing renamed worker-related options.	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.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:8` </location>
<code_context>
+### [v1.10.0](https://github.com/z0ffy/vite-plugin-bundle-obfuscator/compare/v1.9.0...v1.10.0) -  17 December 2025 
+
+- chore(release): bump version to 1.10.0
+- feat: support worker
+- refactor(utils): enhance `isNuxtProject` checks with directory traversal and plugin validation
+- docs(changelog): update for v1.9.0 release and recent workflow changes
</code_context>

<issue_to_address>
**suggestion (typo):** Consider slightly adjusting the phrasing to improve grammatical clarity.

If this isn’t a specific singular term in your domain, consider pluralizing to `support workers` or clarifying as `support Web Workers` for more natural phrasing.

```suggestion
- feat: support Web Workers
```
</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]

suggestion (typo): Consider slightly adjusting the phrasing to improve grammatical clarity.

If this isn’t a specific singular term in your domain, consider pluralizing to support workers or clarifying as support Web Workers for more natural phrasing.

Suggested change

	- feat: support worker
	- feat: support Web Workers