Skip to content

[Snyk] Security upgrade pyasn1 from 0.5.1 to 0.6.2 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nssuwan186-dev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade pyasn1 from 0.5.1 to 0.6.2 #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions samples/compute/requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
google-api-python-client==2.134.0
google-auth==2.30.0
google-auth-httplib2==0.2.0
pyasn1>=0.6.2 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link

@gemini-code-assist gemini-code-assist bot Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To ensure deterministic builds and prevent unexpected behavior from future releases of this transitive dependency, it's a best practice to pin the version using == instead of >=. This is especially important for application-level requirements.txt files. This change would also make the new line consistent with the other dependencies in this file, which are all pinned to exact versions.

pyasn1==0.6.2 # not directly required, pinned by Snyk to avoid a vulnerability