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

chore(deps): update typescript-eslint monorepo to v5.48.1 #590

Merged
merged 1 commit into from
Jan 15, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 29, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin 5.47.0 -> 5.48.1 age adoption passing confidence
@typescript-eslint/parser 5.47.0 -> 5.48.1 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.48.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.48.0

Compare Source

Features
  • eslint-plugin: specify which method is unbound and added test case (#​6281) (cf3ffdd)

5.47.1 (2022-12-26)

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

v5.47.1

Compare Source

Bug Fixes
  • ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
  • eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.48.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.48.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

v5.47.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the type: dependencies Pull requests that update a dependency file label Dec 29, 2022
@vercel
Copy link

vercel bot commented Dec 29, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
typescript-nextjs-starter ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Jan 15, 2023 at 8:19PM (UTC)

@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 97d8d62 to d9edb9e Compare January 5, 2023 17:41
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v5.47.1 chore(deps): update typescript-eslint monorepo to v5.48.0 Jan 5, 2023
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from d9edb9e to aded909 Compare January 12, 2023 19:31
@renovate renovate bot changed the title chore(deps): update typescript-eslint monorepo to v5.48.0 chore(deps): update typescript-eslint monorepo to v5.48.1 Jan 12, 2023
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from aded909 to 897a346 Compare January 15, 2023 20:15
@renovate renovate bot force-pushed the renovate/typescript-eslint-monorepo branch from 897a346 to 087fcc6 Compare January 15, 2023 20:19
@jpedroschmitz jpedroschmitz merged commit 4ccd08f into main Jan 15, 2023
@jpedroschmitz jpedroschmitz deleted the renovate/typescript-eslint-monorepo branch January 15, 2023 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant