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

chore(deps): ⬆️ update nx monorepo to v17.2.8 #110

Merged
merged 1 commit into from
Dec 31, 2023

Conversation

peterjokumsen
Copy link
Member

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nx/angular (source) 17.2.7 -> 17.2.8 age adoption passing confidence
@nx/eslint (source) 17.2.7 -> 17.2.8 age adoption passing confidence
@nx/eslint-plugin (source) 17.2.7 -> 17.2.8 age adoption passing confidence
@nx/jest (source) 17.2.7 -> 17.2.8 age adoption passing confidence
@nx/js (source) 17.2.7 -> 17.2.8 age adoption passing confidence
@nx/workspace (source) 17.2.7 -> 17.2.8 age adoption passing confidence
nx (source) 17.2.7 -> 17.2.8 age adoption passing confidence

Release Notes

nrwl/nx (@​nx/angular)

v17.2.8

Compare Source

17.2.8
🚀 Features
  • remix: add remix
🩹 Fixes
  • linter: flat config should always set path to config when using API
  • nextjs: update migration to handle projects without eslintrc

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
Copy link
Member Author

⚠ 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

@peterjokumsen peterjokumsen merged commit c87776e into main Dec 31, 2023
13 of 14 checks passed
@peterjokumsen peterjokumsen deleted the renovate-github/nx-monorepo branch December 31, 2023 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants