⬆️(deps-dev): Bump @moonrepo/cli from 1.38.3 to 1.39.3

[dependabot]

Bumps @moonrepo/cli from 1.38.3 to 1.39.3.

Release notes

Sourced from @​moonrepo/cli's releases.

v1.39.3

🐞 Fixes

• Fixed a regression where an unknown/unconfigured layer would trigger a violation error.

v1.39.2

🐞 Fixes

• Fixed a glob input parsing issue when the pattern contained a ? and wasn't in URI format.
• Fixed JSON schemas not including property aliases (project type for layer, etc).

⚙️ Internal

• Updated dependencies.

v1.39.1

🐞 Fixes

• Fixed a path error for @moonrepo/cli package.

v1.39.0

🚀 Updates

• The automatic proto install has moved into a new SetupProto action, which is now part of the action graph, and does not run on every command. It's also a bit smarter and will only install when a toolchain requires it.
• Added support for new task input formats based on the RFC: moonrepo/moon#1985
  • Added URI support for files (file://) and globs (glob://).
  • Added object support for files and globs.
• Updated task input files:
  • Added a optional param, which allows the file to be optional (missing) during hashing. Defaults to true.
  • Added a content param, which will match against the file's contents to determine affected state.
• Updated task input globs:
  • Added a cache param, which controls whether the glob results should be cached or not.
• Updated the @moonrepo/cli npm package to no longer rely on postinstall scripts.
• Improved argument quoting for commands and scripts.
• Renamed project type to layer, as it better reflects what it does, a layer of access within the project stack. For backwards compatibility, the type name will still be supported until v2. The following changes have been made:
  • type -> layer in moon.yml
  • --type -> --layer in moon query projects
  • projectType -> projectLayer for MQL
  • $projectType -> $projectLayer for task tokens
  • enforceProjectTypeRelationships -> enforceLayerRelationships in .moon/workspace.yml

🐞 Fixes

• Fixed moon query touched-files --defaultBranch requiring a "true" or "false" explicit value.

... (truncated)

Changelog

Sourced from @​moonrepo/cli's changelog.

1.39.3

🐞 Fixes

• Fixed a regression where an unknown/unconfigured layer would trigger a violation error.

1.39.2

🐞 Fixes

• Fixed a glob input parsing issue when the pattern contained a ? and wasn't in URI format.
• Fixed JSON schemas not including property aliases (project type for layer, etc).

⚙️ Internal

• Updated dependencies.

1.39.1

🐞 Fixes

• Fixed a path error for @moonrepo/cli package.

1.39.0

🚀 Updates

• The automatic proto install has moved into a new SetupProto action, which is now part of the action graph, and does not run on every command. It's also a bit smarter and will only install when a toolchain requires it.
• Added support for new task input formats based on the RFC: moonrepo/moon#1985
  • Added URI support for files (file://) and globs (glob://).
  • Added object support for files and globs.
• Updated task input files:
  • Added a optional param, which allows the file to be optional (missing) during hashing. Defaults to true.
  • Added a content param, which will match against the file's contents to determine affected state.
• Updated task input globs:
  • Added a cache param, which controls whether the glob results should be cached or not.
• Updated the @moonrepo/cli npm package to no longer rely on postinstall scripts.
• Improved argument quoting for commands and scripts.
• Renamed project type to layer, as it better reflects what it does, a layer of access within the project stack. For backwards compatibility, the type name will still be supported until v2. The following changes have been made:
  • type -> layer in moon.yml
  • --type -> --layer in moon query projects
  • projectType -> projectLayer for MQL
  • $projectType -> $projectLayer for task tokens

... (truncated)

Commits

• ab85f3f Release
• e54482b Release
• a805d8b Release
• 1d6a2a9 fix: Fix path error.
• 2589d6e Release
• 1fb09fc deps(proto): Update to v0.51. (#2059)
• 0ff64aa Release
• d6d281c Release
• c842acd Release
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Reviewers

The following users could not be added as reviewers: @dependabot. Either the username does not exist or it does not have the correct permissions to be added as a reviewer.

Please fix the above issues or remove invalid values from dependabot.yml.

[dependabot]

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

[changeset-bot]

⚠️ No Changeset found

Latest commit: efd1468

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Superseded by #64.