release Skill
Cut a new transformers-mlinter release. Bumps the version across all pinned locations, updates the CHANGELOG, runs local checks and a packaged smoke test, then drives the tag-based GitHub Actions publish to PyPI. Use when asked to release, cut a version, or ship X.Y.Z. Published by huggingface in transformers-mlinter.
What is release Skill?
Cut a new transformers-mlinter release. Bumps the version across all pinned locations, updates the CHANGELOG, runs local checks and a packaged smoke test, then drives the tag-based GitHub Actions publish to PyPI. Use when asked to release, cut a version, or ship X.Y.Z. Published by huggingface in transformers-mlinter. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Testing use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use release Skill
- Use it for testing.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: huggingface
- Repository: huggingface/transformers-mlinter
- Skill file: .ai/skills/release/SKILL.md
What it does
Cut a new transformers-mlinter release. Bumps the version across all pinned locations, updates the CHANGELOG, runs local checks and a packaged smoke test, then drives the tag-based GitHub Actions publish to PyPI. Use when asked to release, cut a version, or ship X.Y.Z.
Skill instructions
Release transformers-mlinter Cuts a versioned release. The canonical prose reference is docs/release.md; this skill is the operational checklist. Publishing itself is done by CI — pushing the vX.Y.Z tag triggers .github/workflows/release.yml, which builds, tests, and publishes to PyPI via OIDC trusted publishing (no local upload). Input - <version: the target release version X.Y.Z (e.g. 0.1.2). A pre-release uses X.Y.ZrcN. Constraints - Semantic versioning. Patch releases (Z bumps) reuse the existing vX.Y-release branch; a new minor/major starts a fresh vX.Y-release branch. - Work from a clean checkout on main. Never publish uncommitted changes. - Do NOT run twine upload locally — publishing is CI-only via the pushed tag. - Always confirm with the user before pushing the tag (the tag push is the irreversible, publish-triggering step). The version lives in one place pyproject.toml [project].version is the single source of truth. At runtime mlinter/version.py reads the version from the i
Explore related resources
Frequently asked questions
What is release?
release is a open-source AI agent skill with Copy skill directory. Cut a new transformers-mlinter release. Bumps the version across all pinned locations, updates the CHANGELOG, runs local checks and a packaged smoke test, then drives the tag-based GitHub Actions publish to.
Who is release best for?
release is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.
How do I install release?
Install or run release using Copy skill directory. Check release for the latest setup command.
Is release actively maintained?
release may need a closer maintenance check before production use.
Auto-fetched from GitHub.
