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-theme-next to v1.2.1 #13

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-theme-next (source) 1.1.4 -> 1.2.1 age adoption passing confidence

Release Notes

theme-next/eslint-config-theme-next

v1.2.1

Compare Source

v1.2.0

Compare Source


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 force-pushed the renovate/eslint-config-theme-next-1.x branch from 5d8bffd to ee98345 Compare August 26, 2020 11:58
@renovate renovate bot changed the title Update dependency eslint-config-theme-next to v1.2.0 Update dependency eslint-config-theme-next to v1.2.1 Aug 26, 2020
@renovate renovate bot changed the title Update dependency eslint-config-theme-next to v1.2.1 chore(deps): update dependency eslint-config-theme-next to v1.2.1 Oct 25, 2020
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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