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 dependency eslint-config-standard-with-typescript to v36.0.1 #497

Merged
merged 1 commit into from
Jul 14, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 14, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-standard-with-typescript 36.0.0 -> 36.0.1 age adoption passing confidence

Release Notes

standard/eslint-config-standard-with-typescript (eslint-config-standard-with-typescript)

v36.0.1

Compare Source

Bug fixes
  • retrieval of active node versions in ci (5ccd9a6)

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 this update 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 requested a review from a team as a code owner July 14, 2023 10:10
@renovate renovate bot force-pushed the renovate/eslint-config-standard-with-typescript-36.x branch from b99c291 to 96b3313 Compare July 14, 2023 18:00
@FabianLars FabianLars merged commit 2ed0fd7 into v1 Jul 14, 2023
@FabianLars FabianLars deleted the renovate/eslint-config-standard-with-typescript-36.x branch July 14, 2023 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant