Remove future from dependencies#349
Merged
erocarrera merged 1 commit intoerocarrera:masterfrom Aug 21, 2022
Merged
Conversation
|
@erocarrera could you please produce a release with this change in? There is a High Severity CVE reported against the |
Owner
|
This is now out as release 2023.2.7 |
|
Thank you |
thinrope
added a commit
to thinrope/plaso
that referenced
this pull request
Apr 9, 2024
This was comitted to pefile via erocarrera/pefile#349
thinrope
added a commit
to thinrope/plaso
that referenced
this pull request
Apr 9, 2024
In 2017 this dependency was added via log2timeline#1335 for pefile, but after erocarrera/pefile#349 merged in pefile-2023.2.7 it is not needed anymore. Also bump pefile minimum version.
3 tasks
algitbot
pushed a commit
to alpinelinux/aports
that referenced
this pull request
Mar 4, 2026
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
4 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.
Fix: #348