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

Enable renovate for @ampproject scoped dependencies #24784

Closed
kristoferbaxter opened this issue Sep 27, 2019 · 8 comments
Closed

Enable renovate for @ampproject scoped dependencies #24784

kristoferbaxter opened this issue Sep 27, 2019 · 8 comments

Comments

@kristoferbaxter
Copy link
Contributor

Describe the new feature or change to an existing feature you'd like to see

Enable Renovate updating for dependencies scoped under the @ampproject namespace – these are intended to update AMP when released.

Describe alternatives you've considered

Alternatives:

  1. Build a seperate automatic upgrade system to enable this feature set.
  2. Manually update each @ampproject dependency on each release.

Additional context

We're trying to tighten up the release cycle between WorkerDOM updates and their availability in amp-script.

@dreamofabear
Copy link

IIRC, the impetus behind #23008 was a react/moment upgrade that broke part of amp-date-picker. Maybe we can reinstate the selective ignore? It'd be nice to have auto-upgrades for dompurify too.

@rsimha
Copy link
Contributor

rsimha commented Oct 1, 2019

Good idea, definitely possible.

@rsimha
Copy link
Contributor

rsimha commented Oct 8, 2019

@choumx @kristoferbaxter I started putting together a PR for this, and had a thought: Would it make sense to re-enable renovate upgrades for all dependencies and rely on the new owners bot to alert the right folks to review and validate the upgrades for runtime deps before merging them?

IIRC, the react/moment breaking upgrade was a one off, so I'm wondering where the sweet spot is between risk and freshness.

Your thoughts?

@dreamofabear
Copy link

Would the bot need line-level owners support to do that?

@rsimha
Copy link
Contributor

rsimha commented Oct 8, 2019

Would the bot need line-level owners support to do that?

Yes, it would need line-level support. We've discussed this in ampproject/amp-github-apps#283 and ampproject/amp-github-apps#284.

/cc @rcebulko to comment on if / when the owners bot will be able to auto-assign dependency upgrades to individuals / teams.

@rcebulko
Copy link
Contributor

rcebulko commented Oct 8, 2019

It is indeed in the pipeline, but it's a P3 right now and there are some higher priority issues regarding the deployment process that have been pushed off a bit in favor of getting certain features done in time for the contributor summit. If anyone has strong feelings about escalating the priority of dependency owners, please comment on that thread so the context is there when I can pick it up :)

@rsimha rsimha assigned rcebulko and unassigned rsimha Nov 12, 2019
@rsimha
Copy link
Contributor

rsimha commented May 1, 2020

For the time being, I think we can selectively enable updates for @ampproject* in dependencies. Bumping to P2.

@rcebulko
Copy link
Contributor

These have been enabled, but are not auto-merged because I believe we don't want to give Renovate those permissions at this time. I'm closing this issue for now, but we can re-open down the line if auto-merging becomes necessary/desirable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants