chore: upgrade nx to 14.8.4

[cogwirrel]

For GHSA-cph5-m8f7-6c5x via nrwl/nx#12437

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c54f0ee. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 2 targets

• nx run-many --target=build --all --parallel=4 --output-style stream
• nx run-many --target install-py --projects pipeline-sample-py --parallel=1

---

Sent with 💌 from NxCloud.

[mteichtahl]

nice quick and simple ver bump.

[martenpayne]

👍 looks good

[JeremyJonas]

@cogwirrel Given these files are managed by projen, shouldn't this be defined in PDKMonorepoProject project file?

Either via devDeps or resolveDependencies...

1. PDKMonorepoProject devDeps
2. PDKMonorepoProject resolveDependendencies

[cogwirrel]

@cogwirrel Given these files are managed by projen, shouldn't this be defined in PDKMonorepoProject project file?

Either via devDeps or resolveDependencies...

1. PDKMonorepoProject devDeps
2. PDKMonorepoProject resolveDependendencies

The specific versions don't need to be hardcoded in the .projenrc :) https://projen.io/node.html#dependencies

Any dependencies without specific version ranges set (such as react or react@*) will given a version range in package.json so that future package upgrades and changes to the generated lockfiles such as package-lock.json or yarn.lock will follow semver.

Basically if you don't hardcode a version in projenrc you're then free to use other tooling like dependabot or npm-check-updates etc for managing your dependency versions via the package.json :)

I actually used some of the steps from the built in upgrade-deps task from the monorepo project to upgrade these dependencies (npx projen upgrade-deps). Though in this case I just wanted to target the nx deps specifically so ran npx npm-check-updates --deep --rejectVersion 0.0.0 -u "@nrwl/*" "nx" :)