chore(deps): ⬆️ update nx monorepo to v19.0.7

[peterjokumsen]

This PR contains the following updates:

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

---

Release Notes

nrwl/nx (@​nx/angular)

v19.0.7

Compare Source

19.0.7 (2024-05-23)

🚀 Features

• nx-dev: Add more blogs (#​25939)

🩹 Fixes

• core: more helpful output for format:check --verbose (#​23503)
• core: fix buildTargetFromScript takes a long time (#​25209)
• js: export setup verdaccio generator (#​24008)
• linter: only set flat config env for eslint v9+ (#​25189)
• linter: only depend on eslint v8 (#​25938)
• misc: adjust npm keywords (#​24743)
• release: npm publish error when file path contains spaces (#​24750)

❤️ Thank You

• dmcweeney
• Emily Xiong @​xiongemi
• James Henry @​JamesHenry
• Jason Jean @​FrozenPandaz
• Nicholas Cunningham @​ndcunningham

---

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