Question: Is another official release planned after 1.13.1? It's been ~2 yrs
The last official release was 1.13.1 from 3/16/2023 (commit 4ee230b)
There have been about 23 commits to master since then but no official releases. Those include at least one bug fix that we would like to incorporate.
There is also a 1.13.2-alpha1 pre-release version in nuget from 2/26/2024.
What are others currently using in production?
- The last official release 1.13.1 ?
- The last pre-release version 1.13.2-alpha1 ?
- Doing your own repodb builds?
Not official, but I started creating my own releases on the https://github.com/ampscm/repodb repository with quite a few fixes on top of current trunk.
The packages are in NuGet below AmpScm.RepoDb.* (and used at my employer).
As part of getting this to work I implemented continuous integration via GitHub actions, so we can at least verify new PRs don't break old behavior. (Quite a few of the recent PRs on master in this repository had unwanted side effects... Most were never released from here though)
Thanks @rhuijben, I saw that on Nuget but since all the versions are listed as pre-release, I was concerned about stability.
I'm still hoping we can revive the original project. But it is probably time to release a non preview release.
I agree…maybe we can somehow get a small coalition for collaboration on the project to keep it prosperous….as it’s quite nice and we’ve fully migrated from Dapper on over…. Maybe spinning off into a new officially shared repo, etc.
@rhuijben I saw your recent comments and appreciate you taking strides to help minimize risk of regression bugs & breaking compatibility 🚀 with ci tests…
Hi,
Any news on this ? some commits from 2024 are still waiting for a release.
@FynZ what was on master here is released in AmpScm.RepoDb current, together with some more work. See https://github.com/ampscm/repodb
At my dayjob we needed some of these fixes to completely migrate from Dapper to RepoDB.
Thanks @rhuijben for your work!
@rhuijben thank you for your work, I'm currently in the process of switching to your source. As the readme over your fork is mostly the same as the original one, is there a community space somwhere ? I'd like to contribute so we don't end up in the same situation.
I placed the fork under the AmpScm umbrella, where we have more community projects. No real space but multiple maintainers at the org level to reduce the bus factor.
Input and co-maintainers very welcome 😁