Universal dependency update tool that fits into your workflows.


Compare GitHub changelogs across multiple releases in a single view.


Taking your first steps with Git? Grow from gosling to goose with this Git guide. The guide is easy to follow, you'll learn by doing, and you'll get smart with Git.


Vale linter code for the Plain Language guidelines.



issue comment
Update doc for ecr and codeartifact

I don't know enough about this to help you.

Created at 19 hours ago

Replace full with default image in most places

Created at 19 hours ago
delete branch
HonkingGoose delete branch docs/automerge-key-concept-add-package-group-example
Created at 1 day ago
issue comment
Mistaken processing or onboarding of forked repos in hosted Renovate app

Are you still seeing this same behavior since ~5 days ago?

I'm not seeing this on my fork of the renovatebot/renovate repository anymore. 😄

Created at 1 day ago
HonkingGoose delete branch chore/vm-to-glossary
Created at 1 day ago
issue comment
Renovate has implicitly started processing forked repositories

I got a PR from Renovate bot on my fork of renovatebot/renovate 5 days ago:

  • https://github.com/HonkingGoose/renovate/pull/6

I'm also allowing Renovate to run on all repositories, and am also using the Mend Renovate hosted app on github.com

I think we have a valid bug report here, and I'm labeling it high priority.

Created at 2 days ago
issue comment
Create `config:best-practice` preset

I'm also wondering since this is a new preset why the link to v36, a new preset does not introduce a breaking change right? So a highlight in the v36 release might be wanted but should not stop adding it to v35 already?

You're right, the new preset config:best-practice(s) is not a breaking change. But I think we still want to bundle it with v36.

My idea is to "launch" the config:best-practice(s) preset, with the v36 release. We're also intending to rename config:base to config:recommended in v36, I think.

config:base is not a neutral config, we put some "light" best practices into that preset. So calling it config:recommended makes it clear that it's more than just a basic preset.

Having both config:best-practice(s) and config:recommended in the same major release makes it easy for me to write our release blog, and explain why we're changing the names. 😄

Created at 2 days ago
issue comment
feat(presets)!: rename `config:base` to `config:recommended`

This PR targets the main branch. Should this PR target v36 branch instead?

We probably don't want to accidentally release a v36 just for the rename from config:base to config:recommended. 🙈

Created at 2 days ago

Update docs/usage/key-concepts/automerge.md

Co-authored-by: Rhys Arkins rhys@arkins.net

Created at 2 days ago
delete branch
HonkingGoose delete branch renovate/yarn-monorepo
Created at 2 days ago
pull request closed
build(deps): update dependency @yarnpkg/core to v3.5.0

Mend Renovate

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | @yarnpkg/core | 3.4.0 -> 3.5.0 | age | adoption | passing | confidence |

Release Notes


Compare Source


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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

Created at 2 days ago
pull request opened
docs(automerge): add example grouped package automerge


  • Add example about automerging patch and minor updates from the group:ionic-nativeMonorepo preset


I'm adding this because a user said we don't have any example for this in the docs. 😄 See:

  • #21209

I copy/pasted the config from a comment by @rarkins.

Documentation (please check one with an [x])

  • [x] I have updated the documentation, or
  • [ ] No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • [x] Code inspection only, or
  • [ ] Newly added/modified unit tests, or
  • [ ] No unit tests but ran on a real repository, or
  • [ ] Both unit tests + ran on a real repository
Created at 2 days ago
create branch
HonkingGoose create branch docs/automerge-key-concept-add-package-group-example
Created at 2 days ago
delete branch
HonkingGoose delete branch patch-1
Created at 2 days ago

feat(manager/bitbucket-pipelines): support docker image object (#21102)

Created at 2 days ago