Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issues with Nx v16.7.2 #193

Closed
github-actions bot opened this issue Aug 19, 2023 · 2 comments
Closed

Compatibility issues with Nx v16.7.2 #193

github-actions bot opened this issue Aug 19, 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

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

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

Release Notes

nrwl/nx v16.7.2

v16.7.2

16.7.2 (2023-08-18)

Bug Fixes

  • core: fix ghost alias when parsing yarn lockfile (#18646) (f6a7f18)
  • core: fix schema links (#18395) (83011f7)
  • core: name collisions during project inference should not error out if corrected by a project.json's name (#18665) (a459528)
  • core: nx should not break if packages were not installed (#18687) (95099ae)
  • core: use existing version when calling "yarn set version" (#18669) (76c96fa)
  • devkit: convert-nx-executor should read projectNodes (#18684) (1857e8f)
  • js: expose schematic using the generator function with a default for the project name and root format (#18681) (7578e4b)
  • linter: Normalize paths when in getSourceFilePath (#18601) (da3ca76)
  • nextjs: make next build package manager agnostic (#18661) (bcaecfd)

Compare v16.7.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 Aug 19, 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 Oct 19, 2023
@github-actions
Copy link
Contributor Author

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 Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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