Skip to content

How should we be using dependabot in this repo? #223

Closed

Description

@mdboom

I noticed a few dependabot PRs in this repo, such as this one that upgrade dependencies of specific benchmarks. While in general, I think this is good practice, for a benchmark suite, I think we'd want to upgrade these dependencies as infrequently as possible to keep benchmarking results comparable with one another (and not have to always rerun baselines). Occasionally we are forced to upgrade, for example to get compatibility with a new version of CPython, but that should be deliberate.

(It's possible there is a security counterargument to be made, but I'm not a security expert and I don't know specifically whether that matters or not).

Would it make sense to update the dependabot config to only look at the top-level dependencies of pyperformance itself rather than the dependencies of specific benchmarks?

Activity

  1. ericsnowcurrently commented on Jul 7, 2022

    @ericsnowcurrently
    Member

    for a benchmark suite, I think we'd want to upgrade these dependencies as infrequently as possible to keep benchmarking results comparable with one another

    +1

    It's possible there is a security counterargument to be made

    I don't consider the benchmarks to be a security concern, though I haven't done a thorough analysis of all the benchmark code. IIRC, none of the benchmarks access anything other than files they already own or temporary network services they start themselves.

    Would it make sense to update the dependabot config to only look at the top-level dependencies of pyperformance itself

    +1

  2. mdboom commented on Jul 7, 2022

    @mdboom
    ContributorAuthor

    It looks like this may not be easily possible: dependabot/dependabot-core#4364

  3. maurycy commented on Sep 4, 2025

    @maurycy
    Contributor

    @mdboom @hugovk

    I believe this can be closed now, since #407 is merged.

  4. AA-Turner commented on Sep 10, 2025

    @AA-Turner
    Member

    Seems this hasn't worked, #412 was just opened. cc @maurycy.

  5. maurycy commented on Sep 10, 2025

    @maurycy
    Contributor

    @AA-Turner

    Thank you for spotting this.

    I reached out to the Dependabot team directly:

    since this seems to be still a very active area of development:

    despite not being marked as so in the docs.

    I worry that even if I clone the repository and figure out a solution, our approach won't be stable because of ongoing changes.

  6. hugovk commented on Sep 10, 2025

    @hugovk
    Member

    Thanks for following up with the Dependabot team. We're not in a rush to get this sorted, so can wait for them to stabilise the feature.

  7. maurycy commented on Sep 14, 2025

    @maurycy
    Contributor

    @hugovk @AA-Turner

    The fix should be deployed:

    Let's see how it goes before closing this issue.

    🤞

  8. maurycy commented on Oct 26, 2025

    @maurycy
    Contributor

    @hugovk @AA-Turner It seems to be that we're good now?

  9. hugovk commented on Oct 27, 2025

    @hugovk
    Member

    I think so, we've not had any PRs for pyperformance/data-files/ since June.

    https://github.com/python/pyperformance/pulls?q=sort%3Aupdated-desc+is%3Apr+author%3Aapp%2Fdependabot+is%3Aclosed

    Thank you!

  10. hugovk commented on Nov 6, 2025

    @hugovk
    Member

    We got a new one: #439

    But this is out-of-schedule to fix a potential security issue, so I expect the config doesn't control this. I'll just close that one.

  11. maurycy commented on Jan 26, 2026

    @maurycy
    Contributor

    @hugovk Does #449 imply this is still a problem? 🫢

  12. hugovk commented on Jan 26, 2026

    @hugovk
    Member

    I think it was a security update and they're are exempt from the Dependabot config, so should be fine.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions