-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathrelease-notes.txt
More file actions
2 lines (2 loc) · 1.68 KB
/
release-notes.txt
File metadata and controls
2 lines (2 loc) · 1.68 KB
1
2
- Dropped Support for VI Tester. I had to do that because I moved my build system into a Linux Docker container running LV26Q1. VITester does not support Linux. If you are still using VI Tester and want to use Approvals and need the latest version I have 3 potential solutions: 1. Move everything to LUnit. It should be fairly straightforward. They have similar structure. You could probably script the migration. VI Tester hasn't been supported by JKI for a long time, so probably the best solution. 2. A second solution would be to grab the source for the previous release of Approvals from GitHub, pull out the VI Tester Extensions and maintain it yourself as an additional addon package. That's probably something I could have done from the beginning, but I wanted it to just be one comprehensive package. 3. You could also call the lowlevel functions directly. All the extension really is, is just a wrapper for convenience. Yes I do realize that would mean editing a bunch of old tests.
- Moved to LV2026Q1. Newer versions will only be available in LV26Q1 and later. This is mostly for Docker support in my build pipeline. The code should still be compatible with older versions. Maybe someday JKI will figure how to build packages for previous versions of LV, but until then, if you have an older project to support, you have 2 choices: 1. Fork this entire project and build the package yourself in whatever version you like (should go back to 2020 - It does use interfaces so can't go back further easily). 2. Move to 2026Q1 or later IDE and use the Save For Previous functionality. That should allow you to use the latest version of Approvals while keeping your source code in a previous version of LabVIEW.