ENGINEERING

Block dependency-upgrade PRs when a HuggingFace model license changes

Watches the HuggingFace model cards your repos depend on, and when a model's license changes it fails the open dependency-upgrade pull request and posts the diff so a human can…

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerevent
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDependency-upgrade PR opened or updatedGitHubGitHub
  • ActionRead pinned HuggingFace models from repo manifestGitHubGitHub
  • ActionFetch current license for each model cardHugging FaceHugging Face
  • ActionLook up last-cleared license per modelPostgreSQLPostgres
  • LogicBranch: did any license change?
  • ActionSet PR commit status pass/failGitHubGitHub
  • OutputComment old vs new license on the PRGitHubGitHub

What it does

This workflow keeps your dependency-bump pull requests honest about licensing. It reads the list of HuggingFace models a repo pins, fetches each model card's current license, and compares it to the license recorded the last time the model was cleared. If a license changed (for example Apache-2.0 to a custom non-commercial RAIL license), it marks the upgrade PR's status check as failed and comments the before/after license so nobody merges a now-restricted model by accident.

When to use it

Use it on any repo that ships HuggingFace models in production and runs automated dependency upgrades (Dependabot, Renovate, or a manual bump). It's the guardrail that stops a silent license downgrade from riding in on a routine version bump.

How it works

  1. 1A pull request labeled `deps` opens or updates on GitHub.
  2. 2The workflow reads the repo's model manifest to list every pinned HuggingFace model.
  3. 3It fetches each model card's license field from HuggingFace.
  4. 4A branch compares each license against the last-cleared value stored in Postgres.
  5. 5If any license changed, it sets the PR commit status to failed; otherwise it passes.
  6. 6It posts a GitHub PR comment listing each model and its old vs new license.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.