Skip to content
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.

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

ultralytics 8.3.x (multiple) #219

Merged
merged 2 commits into from
Dec 10, 2024
Merged

ultralytics 8.3.x (multiple) #219

merged 2 commits into from
Dec 10, 2024

Conversation

miketheman
Copy link
Member

No description provided.

Signed-off-by: Mike Fiedler <miketheman@gmail.com>
Signed-off-by: Mike Fiedler <miketheman@gmail.com>
Copy link
Member

@woodruffw woodruffw left a comment

Choose a reason for hiding this comment

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

LGTM!

@sethmlarson sethmlarson merged commit 73130eb into pypa:main Dec 10, 2024
1 check passed
@miketheman miketheman deleted the ultralytics branch December 10, 2024 19:19
@miketheman
Copy link
Member Author

Well, that didn't work as expected. See d8d8741 - where additional versions were added.

Paging @oliverchang for further clarification on what's meant to happen here?

@miketheman
Copy link
Member Author

Note to self: once resolved, we need to manually remove release_vulnerability records from warehouse's db, as they have been mistakenly applied to the versions .43 and .44 now report as vulnerable, which isn't great.

self-reference to find the db records: select * from release_vulnerabilities where vulnerability_id = 'PYSEC-2024-154';

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants