Skip to content

I3.6 · Package registry plugin #20

Closed as not planned
Closed as not planned

Description

@adssib

Part of #4

Story

As the team, we want to know when a tracked package ships a new major, is deprecated or yanked.

Subtasks

  • PyPI and npm metadata
  • Triggers the changelog plugin for details
  • Add the format to docs/plugins.md (Format plugin column) and a row for each plugin built on it

Acceptance criteria

  • A new major on a test package produces a trigger

Activity

  1. adssib commented on Nov 21, 2026

    @adssib
    ContributorAuthor

    Closing as not planned: superseded by I19.8 (#179). Package registries are no longer a separate trigger plugin. Every source lists its own versions from the registry (core/versions: PyPIReleases, PyPIReleasesWithYanked, NPMReleases, GitHubReleases), and every consecutive pair is read and diffed, so a new major is picked up by the source that reads that package (its changelog, migration guide or apisurface) without a trigger in between. See docs/how-it-works.md.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions