283 update lightning to fix critical alert #284
Merged
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.
Closes #283
The main goal here was to update
lightning
to include the security fix, but I also updated the requirements script to better deal with updating python packages (I would otherwise have to delete the files and recreate them every time).I also added an extra bit to the version string for
~=
dependencies to freeze them at the minor version level; I had misunderstood the syntax to freeze at the given level, but it actually does the level above. A~=
1.1string will allow updates to version
1.1.x,
1.2.xor generally
1.y.x, but if we specify
~=1.1.1, it will only update to
1.1.x`, which is what we likely want.The package changes seem to be mostly low-level; I don't expect significant effects, but we will want to test these at least in part before a new release of
scpcaTools
and incorporation intoscpca-nf
.