Skip to content

fix: explain updates that keep the same version number - #24

Merged
NeyorDEV merged 3 commits into
mainfrom
fix/same-version-rebuild
Oct 21, 2026
Merged

NeyorDEV merged 3 commits into
mainfrom
fix/same-version-rebuild

Conversation

@NeyorDEV

Copy link
Copy Markdown
Owner

Found in a real run on a CurseForge pack (SkyBlock Enhanced 5.4.1, Fabric 26.2 → 26.3).

Problem

Packet Fixer, Entity Culling, 3D Skin Layers, Stella, SkyOcean, Custom Scoreboard and others showed up as "update found" with 3.3.6 → 3.3.6. This is correct: their authors publish a separate file per Minecraft version under the same version number. But without an explanation it looks like a mistake.

Fix

When the target file is different but the version number is the same, the reason now reads: "Same version number, file built for Minecraft 26.3." It appears in the Notes column and in every report.

A test reproduces the case, and the CHANGELOG is updated.

Checks

lint, typecheck and 441 tests pass. Formatting on the base branch fails because of the README; that is fixed in the PR "docs: format the README install section".


Generated by Claude Code

Real packs showed "3.3.6 -> 3.3.6" as an update for Packet Fixer, Stella,
SkyOcean and others: their authors publish a separate file per Minecraft
version under the same version number. The reason now says so, instead
of looking like an error.
The README edit on main left a trailing space (Prettier check fails) and
the generated installation page out of date (docs:pages check fails),
so CI on main was red.
@NeyorDEV
NeyorDEV merged commit 5a38817 into main Oct 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant