Repository navigation
chore(deps): pyasn1 0.6.5 e pypdf 6.21.4 (OSV vermelho na main) - #2151
Merged
Merged
Conversation
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
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.
O OSV dependency scan ficou vermelho na main apos o merge da #2147 (run 41144330397): 8 advisories High, cada uma em uv.lock e pylock.toml. pyasn1 0.6.4 (corrigido em 0.6.5) e pypdf 6.21.2 (corrigido em 6.21.3).
Mudanca: so pyasn1 -> 0.6.5 e pypdf -> 6.21.4 (o resolvedor pegou o patch mais novo, que inclui a correcao de 6.21.3), com uv.lock, requirements.txt e pylock.toml regenerados com uv 0.11.2. 3 arquivos, 12 linhas cada, so versoes e hashes. Nao toca em arquivo de gate.
Refs #2123