hackage-upload
Upload Haskell packages to Hackage. Use when the user asks to publish, release, or upload to Hackage.
When & Why to Use This Skill
The Hackage Upload skill automates the end-to-end process of publishing Haskell packages to the Hackage repository. It streamlines the developer workflow by handling version verification from cabal files, generating source distributions, and executing secure uploads, ensuring a consistent and reliable release process for Haskell projects.
Use Cases
- Automated Package Publishing: Streamline the release of new Haskell library versions by automating the 'cabal sdist' and 'cabal upload' sequence.
- Version Consistency Checks: Automatically verify that the package version in the .cabal file is correctly identified before attempting a release.
- Candidate Release Management: Upload packages to Hackage without the --publish flag to create candidates for community testing and validation.
- Release Readiness Enforcement: Integrate with a pre-release checklist to ensure tests pass and changelogs are updated before the final distribution.
| name | hackage-upload |
|---|---|
| description | Upload Haskell packages to Hackage. Use when the user asks to publish, release, or upload to Hackage. |
Hackage Upload
Instructions
When the user asks to publish or upload to Hackage:
Get the current version from
claude.cabal:grep "^version:" claude.cabalCreate the source distribution:
cabal sdistUpload to Hackage (replace X.Y.Z with actual version):
cabal upload --publish dist-newstyle/sdist/claude-X.Y.Z.tar.gz
Pre-release checklist
Before uploading, ensure:
- Version in
claude.cabalhas been bumped CHANGELOG.mdhas an entry for this version- All tests pass (
cabal test) - Code compiles without warnings (
cabal build)
Notes
- The
--publishflag publishes immediately. Without it, the package is uploaded as a candidate. - You must have Hackage credentials configured (typically in
~/.cabal/config). - First-time uploads of a package require manual approval on Hackage.