Skip to content

created initial model registry tool#1151

Merged
jlarson4 merged 13 commits intodev-3.x-canaryfrom
automatic-model-compat-reporting
Feb 23, 2026
Merged

created initial model registry tool#1151
jlarson4 merged 13 commits intodev-3.x-canaryfrom
automatic-model-compat-reporting

Conversation

@bryce13950
Copy link
Collaborator

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Screenshots

Please attach before and after screenshots of the change if applicable.

Checklist:

  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have not rewritten tests relating to key interfaces which would affect backward compatibility

@jlarson4 jlarson4 added this to the 3.0 milestone Jan 20, 2026
@jlarson4 jlarson4 mentioned this pull request Feb 11, 2026
7 tasks
… compatibility reporting

- Added batch verification system (verify_models.py) with status codes (0=unverified, 1=verified, 2=skipped, 3=failed)
- HF scraper with min_downloads=500 threshold (4,846 models across 20 architectures)
- 58 models verified, HF token sanitization in verification notes
- Registry data stored in single supported_models.json and verification_history.json files
- API, validation, and benchmark tooling updated for new registry format
@jlarson4 jlarson4 force-pushed the automatic-model-compat-reporting branch from 8811e51 to 7026749 Compare February 13, 2026 21:25
@jlarson4 jlarson4 changed the base branch from dev-3.x to dev-3.x-canary February 19, 2026 21:20
@jlarson4 jlarson4 merged commit fa5df3f into dev-3.x-canary Feb 23, 2026
42 of 45 checks passed
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.

2 participants