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 @smartive/eslint-config to v5 #118

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@smartive/eslint-config 3.3.0 -> 5.1.0 age adoption passing confidence

Release Notes

smartive/eslint-config (@​smartive/eslint-config)

v5.1.0

Compare Source

Features

v5.0.0

Compare Source

Bug Fixes
Features
  • add new ESLint rules (e2c9855)
  • use type checked recommended rules (2a993ba)
BREAKING CHANGES

v4.0.1

Compare Source

Bug Fixes

v4.0.0

Compare Source

Bug Fixes
  • check if husky is installed (#​18) (8889b95)
  • fix the check that checks if Husky is installed (5f5c469)
  • only run husky in development environment (#​17) (702fb42)
chore
Features
BREAKING CHANGES

Configuration

📅 Schedule: Branch creation - "after 9pm,before 6am" in timezone Europe/Zurich, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/smartive-eslint-config-5.x branch from 69cc36a to 55de350 Compare December 11, 2023 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants