build(deps-dev): bump vite from 7.0.5 to 7.0.7 in /examples/protocols/http_server/restful_server/front/web-demo (IDFGH-16427)

[dependabot]

Bumps vite from 7.0.5 to 7.0.7.

Release notes

Sourced from vite's releases.

v7.0.7

Please refer to CHANGELOG.md for details.

v7.0.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

7.0.7 (2025-09-08)

Bug Fixes

• apply fs.strict check to HTML files (#20736) (6f01ff4)
• upgrade sirv to 3.0.2 (#20735) (63e2a5d)

Tests

• detect ts support via process.features (#20544) (45fdb16)

7.0.6 (2025-07-24)

Bug Fixes

• deps: update all non-major dependencies (#20442) (e49f505)
• dev: incorrect sourcemap when optimized CJS is imported (#20458) (ead2dec)
• module-runner: normalize file:// on windows (#20449) (1c9cb49)
• respond with correct headers and status code for HEAD requests (#20421) (23d04fc)

Miscellaneous Chores

• deps: update rolldown-related dependencies (#20441) (f689d61)
• remove some files from prettier ignore (#20459) (8403f69)

Code Refactoring

• use environment transform request (#20430) (24e6a0c)

Commits

• f88a1c0 release: v7.0.7
• 45fdb16 test: detect ts support via process.features (#20544)
• 63e2a5d fix: upgrade sirv to 3.0.2 (#20735)
• 6f01ff4 fix: apply fs.strict check to HTML files (#20736)
• bdde0f9 release: v7.0.6
• 23d04fc fix: respond with correct headers and status code for HEAD requests (#20421)
• ead2dec fix(dev): incorrect sourcemap when optimized CJS is imported (#20458)
• e49f505 fix(deps): update all non-major dependencies (#20442)
• f689d61 chore(deps): update rolldown-related dependencies (#20441)
• 8403f69 chore: remove some files from prettier ignore (#20459)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "build(deps-dev): bump vite": summary looks too short type/action should be one of [change, ci, docs, feat, fix, refactor, remove, revert, test] Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	The source branch "dependabot/npm_and_yarn/examples/protocols/http_server/restful_server/front/web-demo/vite-7.0.7" incorrect format: contains more than one slash (/). This can cause troubles with git sync. Please rename your branch.

👋 Hello dependabot[bot], we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against d46330d

[dependabot]

Superseded by #17754.