chore: reconcile testmap release state with published 0.4.0#19
Closed
tylerriccio33 wants to merge 1 commit into
Closed
chore: reconcile testmap release state with published 0.4.0#19tylerriccio33 wants to merge 1 commit into
tylerriccio33 wants to merge 1 commit into
Conversation
testmap 0.4.0 was published to PyPI out-of-band (2026-07-03), bypassing release-please. The published wheel is byte-identical to HEAD, including the [tool.testmap.generate] feature (#17), but the repo's release bookkeeping still said 0.3.0. This left the manifest one release behind, so release-please would try to re-cut 0.4.0 and collide with the existing PyPI version. Bring the repo in line with what's already published: - pyproject.toml -> 0.4.0 - .release-please-manifest.json packages/testmap -> 0.4.0 - CHANGELOG.md: add 0.4.0 entry for the generate feature Tag testmap-v0.4.0 is created separately on e452684 (the commit matching the published wheel). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014GcFNWdzHvsbqU72LZUqo5
Owner
Author
|
Closing as redundant. Investigation was based on a stale local checkout one commit behind origin/main. Release-please already cut testmap 0.4.0 correctly via #18 (commit fab62b1): pyproject, manifest, and CHANGELOG are all at 0.4.0 on main, the testmap-v0.4.0 tag exists, and 0.4.0 is published to PyPI. No reconciliation needed — repo is already in BAU. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
testmap 0.4.0was published to PyPI out-of-band (uploaded 2026-07-03), bypassing release-please. The published wheel is byte-identical to HEAD — including the[tool.testmap.generate]feature (#17) — but the repo's release bookkeeping still said0.3.0:pyproject.toml.release-please-manifest.jsonCHANGELOG.mdBecause the manifest was a release behind, release-please would have tried to re-cut
0.4.0and collided with the existing PyPI version, breaking the publish step.Change
Brings the repo in line with what's already on PyPI so the pipeline returns to BAU — the next
feat:correctly proposes 0.5.0 (orfix:→ 0.4.1).Follow-up (manual)
The tag
testmap-v0.4.0still needs creating one452684(the commit matching the published wheel):pytest-testmapwas already consistent; no change there.🤖 Generated with Claude Code