chore(deps-dev): bump @angular-eslint/eslint-plugin-template from 18.2.0 to 21.0.1 in /edc-policy-playground

[dependabot]

Bumps @angular-eslint/eslint-plugin-template from 18.2.0 to 21.0.1.

Release notes

Sourced from @​angular-eslint/eslint-plugin-template's releases.

v21.0.1

21.0.1 (2025-11-23)

🩹 Fixes

• eslint-plugin-template: [prefer-template-literal] handle chained concatenations correctly (#2801)
• eslint-plugin-template: [prefer-contextual-for-variables] fix overlapping fixes for semicolon-separated let declarations (#2802)

❤️ Thank You

• James Henry @​JamesHenry

v21.0.0

21.0.0 (2025-11-22)

As always we recommend that you update your existing workspaces by using ng update as we provide some helpful schematics to help migrate your workspaces to the latest and greatest. Running the following will update Angular, the Angular CLI and angular-eslint together:

ng update @angular/core @angular/cli angular-eslint

🚀 Features

• ⚠️ update Angular dependencies to v21 (6a6b671e)
• ⚠️ eslint-plugin: formally deprecate [no-conflicting-lifecycle] and remove from "all" config (5d845924)
• ⚠️ eslint-plugin-template: add prefer-control-flow to recommended config (77cd24d3)
• ⚠️ eslint-plugin-template: add textContent to default allowList (f112c169)
• schematics: generate new projects using eslint defineConfig (5aa8171b)

🩹 Fixes

• ⚠️ builder: align formatter invocation with eslint CLI by always passing all files, even if quiet (bceaa80e)
• ⚠️ eslint-plugin: make component-selector and directive-selector configurations strict and clear (938362cb)

⚠️ Breaking Changes

• eslint-plugin: formally deprecate [no-conflicting-lifecycle] and remove from "all" config (5d845924)
• eslint-plugin-template: add textContent to default allowList (f112c169)
• builder: align formatter invocation with eslint CLI by always passing all files, even if quiet (bceaa80e)
• eslint-plugin: make component-selector and directive-selector configurations strict and clear (938362cb) The selector validation logic has been updated to be more strict and predictable: Default Prefix Change:
  • Both component-selector and directive-selector now default to prefix: 'app' to match Angular CLI defaults
  • This means selectors without the 'app' prefix will now fail validation unless a different prefix is explicitly configured Style and Prefix Validation Changes:
  • Single-word selectors (e.g., 'appselector') are now appropriately considered valid for both camelCase and kebab-case styles

... (truncated)

Changelog

Sourced from @​angular-eslint/eslint-plugin-template's changelog.

21.0.1 (2025-11-23)

🩹 Fixes

• eslint-plugin-template: [prefer-contextual-for-variables] fix overlapping fixes for semicolon-separated let declarations (#2802)
• eslint-plugin-template: [prefer-template-literal] handle chained concatenations correctly (#2801)

❤️ Thank You

• James Henry @​JamesHenry

21.0.0 (2025-11-22)

🚀 Features

• ⚠️ eslint-plugin-template: add textContent to default allowList (f112c169)
• ⚠️ eslint-plugin-template: add prefer-control-flow to recommended config (77cd24d3)

🩹 Fixes

• ⚠️ eslint-plugin: make component-selector and directive-selector configurations strict and clear (938362cb)

⚠️ Breaking Changes

• ⚠️ eslint-plugin-template: add textContent to default allowList (f112c169)
• eslint-plugin: make component-selector and directive-selector configurations strict and clear (938362cb) The selector validation logic has been updated to be more strict and predictable: Default Prefix Change:
  • Both component-selector and directive-selector now default to prefix: 'app' to match Angular CLI defaults
  • This means selectors without the 'app' prefix will now fail validation unless a different prefix is explicitly configured Style and Prefix Validation Changes:
  • Single-word selectors (e.g., 'appselector') are now appropriately considered valid for both camelCase and kebab-case styles
  • Style validation is now completely independent from prefix validation
  • When a prefix is defined and found in a selector, the rule now correctly validates whether the prefix is properly separated according to the style:
    • For kebab-case: prefix must be followed by a hyphen (e.g., 'app-selector' ✓, 'appselector' ✗)
    • For camelCase: prefix must be followed by an uppercase letter (e.g., 'appSelector' ✓, 'appselector' ✗) Changes to error reporting:
  • Selectors that have valid style but improper prefix usage now report 'prefixFailure' instead of 'styleAndPrefixFailure'
  • Example: 'sgggg-bar' with prefix 'sg' and style 'kebab-case' now reports 'prefixFailure' (valid kebab-case, but prefix not properly separated) Migration Guide:
  • If you have components/directives without prefixes that were previously passing, either:

... (truncated)

Commits

• b19b1f6 chore(release): publish 21.0.1
• 507266b fix(eslint-plugin-template): [prefer-contextual-for-variables] fix overlappin...
• b9e423f fix(eslint-plugin-template): [prefer-template-literal] handle chained concate...
• 9ae353f chore(release): publish 21.0.0
• f112c16 feat(eslint-plugin-template)!: add textContent to default allowList
• 938362c fix(eslint-plugin)!: make component-selector and directive-selector configura...
• 77cd24d feat(eslint-plugin-template)!: add prefer-control-flow to recommended config
• fdddff9 chore(release): publish 20.7.0
• b928d8c feat(eslint-plugin-template): [prefer-ngsrc] add suggestions (#2772)
• e530160 chore(release): publish 20.6.0
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​angular-eslint/eslint-plugin-template since your current version.

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)

[github-actions]

This pull request is stale because it has been open for 7 days with no activity.

[github-actions]

This pull request was closed because it has been inactive for 7 days since being marked as stale.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.