Skip to content

Section 11 does not name the gomod ecosystem that btclib PR 2622 adds #1700

Closed

Description

@fametrano

What is wrong

btclib PR 2622 adds a Go module, fuzz/btcd_decode, and a Dependabot entry for it in .github/dependabot.yml:

  - package-ecosystem: gomod
    directory: /fuzz/btcd_decode

Section 11, Dependabot and pre-commit.ci, names github-actions, uv, bundler, gitsubmodule and docker, and no other. tests/dependabot_test.py holds every tree to that list (NAMED), so once the pull request lands, test_dependabot_watches_only_the_ecosystems_section_11_names[btclib] fails and the alignment run goes red.

How it is known

The alignment suite at 1b74ad50, run with the btclib tree at the branch's local tip c58fd81ee and at its base b71525a8a:

FAILED tests/dependabot_test.py::test_dependabot_watches_only_the_ecosystems_section_11_names[btclib]
AssertionError: ecosystems section 11 does not name: ['gomod']

It passes at the base. By hand, in a checkout of the branch:

sed -n 's/^ *- *package-ecosystem: *//p' .github/dependabot.yml

Why it matters

Without the entry, nothing offers a newer btcd release, and the module's go.mod stays where it was pinned. With it and no change here, every alignment run is red.

Fix

Name gomod in section 11 as a conditional ecosystem, owed where the tree tracks a go.mod. In tests/dependabot_test.py, add "gomod": ("go.mod", "*/go.mod") to WATCHED. This lands before btclib PR 2622.

Assisted-by: my usual tools (LLM, Internet, computer). Mistakes are mine.

Activity

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions