fix: clarify dynamic versioning 0.0.0 behavior#31
Merged
doughayden merged 1 commit intomainfrom Jun 28, 2025
Merged
Conversation
- Add dedicated section explaining expected version display - Clarify when commands show 0.0.0 vs actual dynamic version - Update troubleshooting to avoid confusion about normal behavior - Add quick reference table for version command outputs 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
What
Add comprehensive documentation explaining when dynamic versioning shows
0.0.0vs actual dynamic versions.Why
User confusion about seeing
0.0.0in routine commands likepoetry versionandpoetry install- this is actually expected behavior but wasn't clearly documented.How
0.0.0is usually not a problemTests
🤖 Generated with Claude Code