Replies: 1 comment
-
Hi, thanks for using Kryptor. Yes, a new release really needs to be done. I think the trimming can be resolved quite easily using a trick I found working on another program. Better erasure of secrets can be left for another release, but I need to update a dependency because there's a bug that affects Kryptor after switching to .NET 8 that doesn't appear during unit testing. I've fixed the library but am working on some other features that prevent me creating the package at the moment. What bothers me about this type of program is that I'm manually testing it and not testing it properly cross-platform. Even trivial changes feel rather dangerous given what it's doing. Manual builds/signatures and sorting out packages also isn't very smooth. These things combined with other projects and IRL activities have meant I haven't done much work on this project for a while. Most of the development was done whilst I was at uni during holidays and when I had fewer projects. I'll hopefully get the next version of the library out this weekend. However, Christmas is coming up so I'm not sure I'm going to be able to get Kryptor updated until the new year now. |
Beta Was this translation helpful? Give feedback.
-
As .NET 6 recently hit EOL and this project already being on .NET 8, could you make a new release?
If I understand correctly, the only thing blocking the 4.1.1 release are the trimming issues with CommandLineUtils?
(or it may be already done, I just skimmed over the commits since last release and the roadmap)
Beta Was this translation helpful? Give feedback.
All reactions