chore(deps): ⬆️ update nx monorepo to v17.2.7

[peterjokumsen]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nx/angular (source)	17.2.6 -> 17.2.7
@nx/eslint (source)	17.2.6 -> 17.2.7
@nx/eslint-plugin (source)	17.2.6 -> 17.2.7
@nx/jest (source)	17.2.6 -> 17.2.7
@nx/js (source)	17.2.6 -> 17.2.7
@nx/workspace (source)	17.2.6 -> 17.2.7
nx (source)	17.2.6 -> 17.2.7

---

Release Notes

nrwl/nx (@​nx/angular)

v17.2.7

Compare Source

17.2.7

🩹 Fixes

• angular: fix standalone eslint config generation
• bundling: added back code to handle skipTypeField option of rollup executor options + tests
• linter: ensure angular entry point checks are correct
• nextjs: enhance page generator to work when --project is not supplied
• nextjs: remove temporary patch for next eslint rules
• nextjs: correct inferred outputs for root Next.js projects
• node: E2E test port conflicts
• release: add overall nx release command
• release: publish error handling, dry-run in dependsOn
• release: capture all release titles during parse
• testing: run playwright with the correct project option for multiple values
• testing: safely handle circular deps in component testing plugin
• testing: set correct type for ignoreTestFiles option in cypress executor
• vite: vitest migration add reporters
• vite: more properly resolve arguments from configurations
• vite: dist and coverage paths for root projects

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[peterjokumsen]

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands