nodejs-common icon indicating copy to clipboard operation
nodejs-common copied to clipboard

chore(deps): update dependency @compodoc/compodoc to v1.1.24

Open renovate-bot opened this issue 10 months ago • 3 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@compodoc/compodoc 1.1.23 -> 1.1.24 age adoption passing confidence

Release Notes

compodoc/compodoc (@​compodoc/compodoc)

v1.1.24

Compare Source

Merged
Bug fixes

Configuration

📅 Schedule: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

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

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.

renovate-bot avatar Apr 27 '24 11:04 renovate-bot

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] avatar Apr 27 '24 17:04 gcf-merge-on-green[bot]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] avatar Apr 30 '24 08:04 gcf-merge-on-green[bot]

We should just get rid of this dependency. This has broken us a number of times (as it incorporates breaking changes in patch releases) and its unclear who actually uses it with our libraries.

danielbankhead avatar Apr 30 '24 17:04 danielbankhead

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] avatar May 29 '24 22:05 gcf-merge-on-green[bot]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] avatar Jun 07 '24 18:06 gcf-merge-on-green[bot]