What's the status of version 2.1.42 and version 2.1.44?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hi!
Thanks for providing this library. We use it all the time.
I saw that you unlisted version 2.1.37 and that the latest stable release is in NuGet is 2.1.35 (
). From the release notes 2.1.42 reverts a broken feature in 2.1.37 and 2.1.44 only updates the README, so in some sense 2.1.44 is functionally equivalent to 2.1.35. I guess it is up to you to define what is a release and what isn't.
However, releasing these versions in GitHub, but not on NuGet, seems to confuse our dependency version checker. This in turn confuses us.🙃 Would it be possible to either release these version on NuGet or label them as pre-releases similar to this https://github.com/microsoft/vstest/releases? It could be argued that the dependency checker should be based on NuGet, but this isn't the case at the moment.
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
Review the GitHub release entries for 2.1.42 and 2.1.44 alongside the Dapper NuGet package history and the linked issue about 2.1.37. Done means establishing a consistent release or prerelease status so dependency version checkers no longer treat unpublished GitHub versions as stable releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100