ci: set up CI/CD pipeline with lint/test/build/release workflows #11

Merged
scheerenkevin merged 1 commit from feature/ci-cd-setup into develop 2026-08-03 04:16:08 +00:00
scheerenkevin commented 2026-08-03 04:15:23 +00:00 (Migrated from github.com)

Summary

  • Hatch-based pyproject.toml (hatchling backend), Python 3.12+
  • Minimal package skeleton (src/alchemy_wallet_client) + version smoke test so CI has something to lint/format/test
  • .github/workflows/ci.yml: lint + format-check + test on every PR into main/develop
  • .github/workflows/dev-build.yml: package build validation on merge to develop
  • .github/workflows/release.yml + scripts/release.py: on merge to main, computes next SemVer bump from Conventional Commits since last tag, updates CHANGELOG.md, tags, builds, publishes a GitHub Release
  • CHANGELOG.md scaffold (Keep a Changelog format)

Verified locally: hatch run lint, hatch run format-check, hatch run test, and hatch build all pass.

Closes #1

Note: this PR merges into develop (not the default branch main), so GitHub's auto-close on "Closes #1" will not fire on merge — the issue will be closed manually with a comment referencing this PR, per repo process.

## Summary - Hatch-based `pyproject.toml` (hatchling backend), Python 3.12+ - Minimal package skeleton (`src/alchemy_wallet_client`) + version smoke test so CI has something to lint/format/test - `.github/workflows/ci.yml`: lint + format-check + test on every PR into `main`/`develop` - `.github/workflows/dev-build.yml`: package build validation on merge to `develop` - `.github/workflows/release.yml` + `scripts/release.py`: on merge to `main`, computes next SemVer bump from Conventional Commits since last tag, updates `CHANGELOG.md`, tags, builds, publishes a GitHub Release - `CHANGELOG.md` scaffold (Keep a Changelog format) Verified locally: `hatch run lint`, `hatch run format-check`, `hatch run test`, and `hatch build` all pass. ## Related Closes #1 Note: this PR merges into `develop` (not the default branch `main`), so GitHub's auto-close on "Closes #1" will not fire on merge — the issue will be closed manually with a comment referencing this PR, per repo process.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kevin/alchemy-wallet-client!11
No description provided.