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

Bump @angular-eslint/eslint-plugin-template from 14.1.1 to 19.0.1 #719

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 6, 2024

Bumps @angular-eslint/eslint-plugin-template from 14.1.1 to 19.0.1.

Release notes

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

v19.0.1

19.0.1 (2024-12-06)

🩹 Fixes

  • update dependency @​angular/compiler to v19.0.3 (#2159)
  • update dependency eslint to v9.16.0 (#2148)
  • update typescript-eslint packages to v8.17.0 (#2153)
  • eslint-plugin: add prefer-signals rule to exported config (#2150)
  • eslint-plugin-template: prevent the slot tag from being self-closing (#2088)

❤️ Thank You

v19.0.0

19.0.0 (2024-11-29)

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.

However, please note that the angular-eslint package itself now supports being referenced as the schematics collection, so...

IF YOU ARE ALREADY USING angular-eslint and ESLint v9 and flat config you can now do the following:

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

(Note: If you encounter any issues with this, you may need to update to the latest v18 release of angular-eslint first)

IF YOU ARE STILL USING @angular-eslint/schematics and ESLint v8 and .eslintrc.json configs you can still do the following:

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

NOTE: There will not be any migration of your setup to ESLint v9 or flat configs for existing ESLint v8 workspaces while migrating to angular-eslint v19.

We will explore landing an opt in migration schematic in a minor release after 19.0.0.

🚀 Features

  • update angular packages to the stable v19 (#2120)
  • allow referencing angular-eslint as the schematics collection (2be3107b)
  • ⚠️ eslint-plugin: remove deprecated prefer-standalone-component rule (#2112)
  • ⚠️ eslint-plugin: prefer-standalone recognizes that standalone is the default (#2096)
  • ⚠️ eslint-plugin: remove deprecated sort-ngmodule-metadata-arrays rule (#2114)
  • ⚠️ eslint-plugin: remove deprecated no-host-metadata-property rule (#2113)
  • eslint-plugin: new rule prefer-signals (#1872)

... (truncated)

Changelog

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

19.0.1 (2024-12-06)

🩹 Fixes

  • eslint-plugin-template: prevent the slot tag from being self-closing (#2088)

❤️ Thank You

19.0.0 (2024-11-29)

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

18.4.3 (2024-11-29)

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

18.4.2 (2024-11-23)

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

18.4.1 (2024-11-18)

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

18.4.0 (2024-10-21)

🩹 Fixes

  • update typescript-eslint packages to v8.10.0 (#2046)
  • update dependency aria-query to v5.3.2 (#2053)
  • update dependency aria-query to v5.3.1 (#2043)

18.3.1 (2024-09-11)

🩹 Fixes

  • template-parser: visit receiver of Call expression

  • template-parser: visit receiver of Call expression"

  • template-parser: visit receiver of Call expression

❤️ Thank You

  • James Henry
  • Paweł Maniecki

18.3.0 (2024-08-13)

... (truncated)

Commits
  • 34e28ef chore(release): publish 19.0.1
  • e264546 fix(eslint-plugin-template): prevent the slot tag from being self-closing (#2...
  • af53867 chore(release): publish 19.0.0
  • a40e339 chore: bundle the compiler using esbuild (#2126)
  • 5c46a94 chore(release): publish 18.4.3
  • e694232 chore: migrate the repo to eslint flat config (#2145)
  • 8d0c6f3 chore(release): publish 18.4.2
  • 3e05a84 chore(release): publish 18.4.1
  • 1796bd7 chore(release): publish 18.4.0
  • fc3a77b fix: update typescript-eslint packages to v8.10.0 (#2046)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [@angular-eslint/eslint-plugin-template](https://github.com/angular-eslint/angular-eslint/tree/HEAD/packages/eslint-plugin-template) from 14.1.1 to 19.0.1.
- [Release notes](https://github.com/angular-eslint/angular-eslint/releases)
- [Changelog](https://github.com/angular-eslint/angular-eslint/blob/main/packages/eslint-plugin-template/CHANGELOG.md)
- [Commits](https://github.com/angular-eslint/angular-eslint/commits/v19.0.1/packages/eslint-plugin-template)

---
updated-dependencies:
- dependency-name: "@angular-eslint/eslint-plugin-template"
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. labels Dec 6, 2024
@k8s-ci-robot
Copy link
Contributor

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

  • dab3437 Bump @angular-eslint/eslint-plugin-template from 14.1.1 to 19.0.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Dec 6, 2024
@k8s-ci-robot
Copy link
Contributor

Keywords which can automatically close issues and at(@) mentions are not allowed in the title of a Pull Request.

You can edit the title by writing /retitle in a comment.

When GitHub merges a Pull Request, the title is included in the merge commit. To avoid invalid keywords in the merge commit, please edit the title of the PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Dec 6, 2024
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 6, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign puerco for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dependabot dependabot bot requested review from cici37 and jrsapi December 6, 2024 12:32
@k8s-ci-robot
Copy link
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Dec 6, 2024
Copy link

netlify bot commented Dec 6, 2024

Deploy Preview for kubernetes-sigs-release-notes ready!

Name Link
🔨 Latest commit dab3437
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-release-notes/deploys/6752eedb6ffbc80008333eb9
😎 Deploy Preview https://deploy-preview-719--kubernetes-sigs-release-notes.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@k8s-ci-robot
Copy link
Contributor

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-release-notes-e2e dab3437 link true /test pull-release-notes-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 10, 2024

Superseded by #724.

@dependabot dependabot bot closed this Dec 10, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/angular-eslint/eslint-plugin-template-19.0.1 branch December 10, 2024 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants