Bump @typescript-eslint/parser from 7.7.0 to 7.8.0 in /angular

[dependabot[bot]]

Bumps @typescript-eslint/parser from 7.7.0 to 7.8.0.

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.8.0

7.8.0 (2024-04-29)

🚀 Features

• rule-tester: assert suggestion messages are unique (#8995)
• typescript-estree: add maximumDefaultProjectFileMatchCount and wide allowDefaultProjectForFiles glob restrictions (#8925)

🩹 Fixes

• eslint-plugin: [no-unsafe-argument] handle tagged templates (#8746)
• eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check (#8717)
• eslint-plugin: [consistent-type-assertions] handle tagged templates (#8993)
• eslint-plugin: [no-unsafe-return] handle union types (#9001)
• eslint-plugin: [no-unused-vars] clear error report range (#8640)
• utils: export ESLint backwards-compat functions (#8976)

❤️ Thank You

• auvred @​auvred
• Josh Goldberg ✨
• jsfm01 @​jsfm01
• Kim Sang Du @​developer-bandi
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

v7.7.1

7.7.1 (2024-04-22)

🩹 Fixes

• eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment (#8800)
• eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type (#8809)
• eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish (#8559)
• eslint-plugin: [no-for-in-array] refine report location (#8874)
• eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type (#8912)

❤️ Thank You

• Abraham Guo
• Kirk Waiblinger @​kirkwaiblinger
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.8.0 (2024-04-29)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.7.1 (2024-04-22)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• ee677f6 chore(release): publish 7.8.0
• 3e19436 chore(release): publish 7.7.1
• See full diff in compare view

You can trigger a rebase of this PR 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 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)

[tillkuhn]

superseded

[dependabot[bot]]

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.