Repository navigation
Release hygiene: no tags, version string unchanged across 937 commits #869
Description
The package version reads 2.12.0 at both commit c7958a3 and main (cf5cac7), 937 commits apart, and the repo has no tags. Consumers must pin a commit. Example: the P9 fix (#681) is on main but not in the commit we had pinned, with no way to see that from the version. Request tags or releases and a version bump per release.
Activity
rng1995 commentedon Oct 19, 2026
The requested versioned release/tag and per-release version bump are available: SkillSpector v2.13.0 was published on October 16, 2026 through merged PR #833.
Verified on 2026-10-19: the public, non-draft release has wheel and source-distribution assets; tag
v2.13.0points to091a509b3d6ba8ff5be528966e1f43c2e68cf214; and the tagged package metadata declares version2.13.0. The repository also exposes earlier version tags, includingv2.12.0.Important distinction: v2.13.0 was assembled on a release branch from selected fixes, not from all of current main. Main still declares
2.12.0, so that version string does not distinguish arbitrary development commits or guarantee that every main-only fix is in v2.13.0. Consumers can pin the published release/tag for a versioned build; use a commit pin when deliberately selecting unreleased main changes.Closing this release/tag request as completed.