Important model change
example-org/protein-6b
- Weights changed
- Remote code changed
- Recorded revision
mainFloating- Exposure
- Potentially affected
Alerts & Notifications
Know when an important model change needs your attention.
PinDiff turns upstream changes into relevant alerts using the models and revisions your team depends on, with your exposure beside each one.
Not every change needs your attention
Model repositories can change several times a week. PinDiff surfaces material changes — critical, high and medium significance — for the models you watch. Low-significance edits, and weight re-uploads in adapter, LoRA, GGUF and test repositories, stay in each model’s history without raising an alert.
- Model weights
- Licence
- Remote code / configuration
- Access / gating
- Model card
- Repository status
Dependency-aware alerts
The same kind of upstream change reads differently depending on the revision you recorded.
Upstream change
example-org/chat-7b
- Weights changed
- Recorded revision
3f9a2c1Pinned- Exposure
- Recorded revision does not automatically move.
How exposure is decided is explained in Revision Tracking.
How an alert is produced
- Dependency
- Upstream change detected
- Change classified
- Revision context checked
- Relevance determined
- Alert surfaced
Where alerts appear
-
Your workspace Available
An alert for each dependency an upstream change is relevant to, with its attention level, recorded revision, exposure and the reason it matters.
Open alerts -
Email Available
Notifications after PinDiff detects a relevant upstream change, immediately or in a daily or weekly digest, depending on your plan and notification settings.
-
GitHub pull requests Available
The PinDiff Action lists model dependencies and upstream changes in the job summary. It is informational and never fails a build.
GitHub integration -
Webhooks Not available yet
-
Slack Not available yet