Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

Compatibility issues with Nx v16.4.2 #182

Closed
github-actions bot opened this issue Jul 1, 2023 · 2 comments
Closed

Compatibility issues with Nx v16.4.2 #182

github-actions bot opened this issue Jul 1, 2023 · 2 comments
Assignees
Labels
bug Indicates an unexpected problem or unintended behavior enhancement Indicates an enchancement to an existing feature stale Indicates that work won't continue on an issue, pull request, or discussion

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2023

Automated tests failed against Nx v16.4.2.
These errors need to be addressed, before v16.4.2 can be supported.

Package Change
🐋 nrwl/nx v15.9.2 -> v16.4.2

Release Notes

nrwl/nx v16.4.2

v16.4.2

16.4.2 (2023-06-30)

Bug Fixes

  • angular: normalize path in move generator (#17877) (ef05a37)
  • core: fix project file map for root projects (#17894) (515bfda)
  • js: ignore watch errors when a process is already killed on Windows (#17891) (38861fd)
  • js: normalize tsconfig paths used as correlation keys in batch implementation (#17888) (4184ff5)
  • js: skip watcher if --watch=false for node executor (#17887) (60e6c36)
  • linter: create-package-json should omit non-npm and ignored packages (#17883) (f3fc658)
  • nextjs: Running nx build --configuration=development should not throw an error (#17866) (39c4f03)
  • nextjs: set localhost as hostname default (#17856) (20c932d)
  • nx-dev: skip docs for private package (#17843) (d471af7)

Compare v16.4.2 with v15.9.2


Configuration

📅 Schedule: Daily at midnight (UTC).

This issue has been generated by the nx-latest workflow. 🖖

@github-actions github-actions bot added bug Indicates an unexpected problem or unintended behavior enhancement Indicates an enchancement to an existing feature labels Jul 1, 2023
@github-actions
Copy link
Contributor Author

Warning

This issue is stale because it has been open for 60 days with no activity. 💤

Either remove the stale label or leave a comment else this issue will be closed in 7 days.

@github-actions github-actions bot added the stale Indicates that work won't continue on an issue, pull request, or discussion label Aug 31, 2023
@github-actions
Copy link
Contributor Author

github-actions bot commented Sep 7, 2023

This issue was closed because it has been stale for 67 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Indicates an unexpected problem or unintended behavior enhancement Indicates an enchancement to an existing feature stale Indicates that work won't continue on an issue, pull request, or discussion
Projects
None yet
Development

No branches or pull requests

1 participant