Skip to content

Yank gp-sphinx-vite from PyPI (superseded by sphinx-vite-builder) #32

@tony

Description

@tony

Action

Manually yank gp-sphinx-vite from PyPI now that PR #29 has retired
the package and shipped its successor (sphinx-vite-builder) at
parity in v0.0.1a16.dev3 and beyond.

Context

gp-sphinx-vite was the workspace's original Sphinx extension that
auto-spawned pnpm exec vite build --watch under sphinx-autobuild.
PR #29 ported its hooks.py + config.py + bus.py + process.py
into sphinx_vite_builder._internal/, swept all workspace consumers
(gp-sphinx config auto-injection, gp-furo-theme docstring, docs
build), and deleted the packages/gp-sphinx-vite/ directory in
commit 75f63ba. The package no longer exists in this repo and is no
longer republished.

What remains on PyPI: three pre-release dev versions still live and
installable.

Successor:
https://pypi.org/project/sphinx-vite-builder/.

Recommended yank reason

Superseded by sphinx-vite-builder (https://pypi.org/project/sphinx-vite-builder/).
The hooks + config + bus + process modules were ported in
git-pull/gp-sphinx#29; install sphinx-vite-builder instead.

How to yank

uv publish doesn't expose a yank operation, so this needs the PyPI
web UI (or twine) under the trusted-publisher-managed account:

  1. Log into https://pypi.org/manage/project/gp-sphinx-vite/releases/
  2. For each of 0.0.1a16.dev0, dev1, dev2: open the release →
    "Options" → "Yank" → paste the reason above.

A yank is non-destructive: the wheels stay downloadable for anyone
who pinned the exact version (so existing lockfiles don't break),
but pip / uv stop resolving yanked versions for new installs.

Related

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