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

feat(ecosystems): add support for Mageia ecosystem #3101

Merged
merged 13 commits into from
Feb 11, 2025

Conversation

andrewpollock
Copy link
Contributor

This commit duplicates the RedHat ecosystem class, as I believe Mageia is distantly based off Red Hat and follows RPM version conventions.

This commit duplicates the RedHat ecosystem class, as I believe Mageia
is distantly based off Red Hat and follows RPM version conventions.
@andrewpollock
Copy link
Contributor Author

/cc @dfandrich

Copy link

@dfandrich dfandrich left a comment

Choose a reason for hiding this comment

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

As far as I'm familiar with what this is about, it looks fine to me.

osv/ecosystems/_ecosystems.py Outdated Show resolved Hide resolved
osv/ecosystems/mageia_test.py Show resolved Hide resolved
osv/ecosystems/mageia.py Show resolved Hide resolved
andrewpollock and others added 7 commits February 5, 2025 13:22
This commit duplicates the RedHat ecosystem class, as I believe Mageia
is distantly based off Red Hat and follows RPM version conventions.
This commit updates the submodule to incorporate
ossf/osv-schema#331 so that ecosystem tests work
correctly.

It also fixes the ecosystem internal referential test to  reflect the
name change in JSON schema definition from
ossf/osv-schema#296
Copy link
Contributor

@another-rex another-rex left a comment

Choose a reason for hiding this comment

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

LGTM, just double checking is the osv-schema update intentional here?

@andrewpollock andrewpollock merged commit c2e9e5f into google:master Feb 11, 2025
11 checks passed
@andrewpollock
Copy link
Contributor Author

LGTM, just double checking is the osv-schema update intentional here?

Yes, see 096b0e8

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.

5 participants