chore(deps-dev): bump eslint-plugin-boundaries from 6.0.2 to 7.2.0

[dependabot]

Bumps eslint-plugin-boundaries from 6.0.2 to 7.2.0.

Release notes

Sourced from eslint-plugin-boundaries's releases.

Improve deprecation warnings

eslint-plugin v7.2.0

Added

• feat(#477): boundaries/dependencies and boundaries/element-types now warn when an allow/disallow entry omits the from/to wrapper (e.g. allow: [{ element: { type: "helper" } }] instead of allow: [{ to: { element: { type: "helper" } } }]). The bare form keeps working; the warning is suppressible via boundaries/legacy-warnings: false. Note that v5-style configs using a legacy allow/disallow selector (e.g. allow: ["helper"]) now emit this warning in addition to the legacy-selector warning they already emitted.

Changed

• refactor(#477): Legacy selector deprecation warnings are now reported per detected syntax form — legacy string selectors, legacy tuple selectors, and element selectors used directly as entity selectors each get their own message with a concrete before/after example. Warnings also say "policy"/"policies" instead of "rule(s)", matching v7 terminology.
• refactor(#477): The "unrecognized selector shape" warning now names only the specific properties (from, to, dependency, allow, disallow) that failed validation, instead of always listing all five.

Fixed

• fix(#479): Upgrade @boundaries/elements. A boundaries/files descriptor without capture no longer resets file.captured when it matches after a capturing descriptor. Captured values are now merged from every matching file descriptor regardless of declaration order, matching the boundaries/elements descriptor behavior. exclusive descriptors still reset captured values.
• fix(#477): Legacy selector deprecation warnings now link to the migration guide that actually deprecated the detected syntax. Element selectors used directly as entity selectors (e.g. { type: "component" }) link to the v6-to-v7 entity selectors section instead of the v5-to-v6 guide. The mode deprecation warning links to its own section of the v6-to-v7 guide.
• fix: boundaries/dependencies/boundaries/element-types policies with a bare (unwrapped) allow/disallow entry and neither from nor to at the policy level (e.g. { allow: { element: { type: "helper" } } }) no longer invert the policy's meaning or crash the linter on every matched dependency. The bare entry now consistently fills to, matching the documented allow/disallow semantics.

elements v3.1.1

Fixed

• fix(#479): A matching file descriptor without capture no longer resets file.captured. Captured values are now merged from every matching file descriptor regardless of declaration order, matching the element descriptor behavior. exclusive descriptors still reset captured values.

chore

Added

• chore: Add review-pr agents skill

Changed

• chore: Improve agents docs
• chore: Upgrade nx version to v22.7.7
• chore: Pin dependencies in github workflows

Descriptors accumulation options

eslint-plugin v7.1.0

Added

• feat(#466): Add per-descriptor stopMatching and exclusive options, available on both boundaries/elements and boundaries/files descriptors. When a stopMatching descriptor matches, previously accumulated types/categories at that path level are kept and no further descriptors are evaluated for that level. exclusive additionally discards any previously accumulated matches at that level, keeping only its own match, and takes precedence over stopMatching when both are set on the same descriptor. Both options apply independently at each path level, so for elements they affect parent elements the same way they affect the main element.
• feat(#466): Add boundaries/files-single-match setting. When true, only the first matching boundaries/files descriptor's category is used and matching stops; default false preserves the current accumulation behavior.
• feat(#466): Add boundaries/elements-single-match setting, sharing vocabulary with the new boundaries/files-single-match. It is the canonical replacement for boundaries/elements-single-type and takes precedence over it when both are set.

Changed

• refactor(#466): boundaries/elements-single-type is now deprecated in favor of boundaries/elements-single-match. It is kept as a backward-compatible alias, with a deprecation warning, and no behavior change.

Fixed

... (truncated)

Commits

• 50f2d31 Release v7.2.0 (#485)
• cc66c04 Merge branch 'master' into release
• 23b2278 chore(release): Release eslint-plugin v7.2.0 and elements v3.1.1 (#484)
• 4c39dd4 chore: Add review-pr skill (#483)
• 5c48549 fix: Point legacy selector warnings to the correct migration guide, with clea...
• 1bd202f chore(deps): update dependency nx to v22.7.7 [security] (#478)
• 704358c fix: Do not reset file captured values when a matching descriptor has no capt...
• 8f195dd docs: Improve agents docs (#480)
• 13795eb chore(deps): pin dependencies (#474)
• 9484b4d Release v7.1.0 (#437)
• Additional commits viewable in compare view

[github-actions]

📊 Bilingual Coverage Impact

PR Changes

• Paired EN/ES files modified: 0
• New EN files needing ES translation: 0

Repository Coverage

Metric	Value
Total EN files	525
Total ES files	495
Paired files	0
Coverage	0%

✅ Good: All EN changes have ES counterparts.

---

Generated by GitHub Actions