sat-solvers 0.1.1

# Release Checklist

Follow these steps to create a new release:

## Pre-release

- [ ] Ensure all tests pass: `cargo test --all-features`
- [ ] Ensure clippy is clean: `cargo clippy --all-features -- -D warnings`
- [ ] Ensure formatting is correct: `cargo fmt --check`
- [ ] Update version in `Cargo.toml`
- [ ] Update `CHANGELOG.md`:
  - Move items from `[Unreleased]` to new version section
  - Add release date
  - Add any missing changes

## Release

```bash
# Commit the version bump
git add Cargo.toml Cargo.lock CHANGELOG.md
git commit -m "Release v0.x.x"

# Create and push the tag
git tag v0.x.x
git push origin main
git push origin v0.x.x
```

## Post-release

The GitHub Actions workflow will automatically:

1. Validate that the tag version matches `Cargo.toml`
2. Run the full test suite
3. Create a GitHub Release with auto-generated release notes
4. Publish the crate to crates.io

## Troubleshooting

### Release workflow failed

- Check the Actions tab for error details
- Common issues:
  - Version mismatch between tag and `Cargo.toml`
  - Missing `CARGO_REGISTRY_TOKEN` secret
  - Test failures

### Need to yank a release

```bash
cargo yank --version 0.x.x
```

### Prerelease versions

For alpha/beta/RC releases, use tags like:
- `v0.2.0-alpha.1`
- `v0.2.0-beta.1`
- `v0.2.0-rc.1`

These will be marked as prereleases on GitHub automatically.