onepub-dev / onepub-dev/pub_release
2nd entry of custom version is being ignored.
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
If you choose to enter a custom version and get it wrong you can re-enter the custom version no.
The problem is that it then reports that the 'The accepted version is:' and reports the version no. that was entered on the first attempt.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the CLI flow by entering an incorrect custom version, then entering a second version. Trace where the accepted version is retained and reported, and verify that the message uses the second entry after the correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100