Release/v3.1.0#180
Merged
rreichenbach merged 5 commits intoJun 18, 2026
Merged
Conversation
sastraxi
reviewed
Jun 18, 2026
sastraxi
reviewed
Jun 18, 2026
sastraxi
reviewed
Jun 18, 2026
Co-authored-by: Cameron Gorrie <sastraxi@gmail.com>
Co-authored-by: Cameron Gorrie <sastraxi@gmail.com>
Co-authored-by: Cameron Gorrie <sastraxi@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CHANGELOG.md updated with main v3.1.0 changes
THIRD_PARTY_LICENSES.md added to list all (within reason) included third party software. Much of this data was obtained using scripts using, grep, pip-licenses and LILV on a running system. Ideally, these scripts could just be re-run with each release, but in reality, there were a ton of manual edits required. Especially for the LV2 plugins: author info and licensing info in the TTL files was often missing, so I had to do manual cross referencing using whatever links I could find, many of those were dead, or plenty of the content there was incomplete.
Bottom line - re-running the scripts would result in loss of the manually entered data.
I believe the best solution moving forward would be just to update the file manually as new libs and plugins are added. It should be fairly rare.
If need be, we could have a script that simply scans and warns when a plugin is found in LILV world that's not listed in the file.