This file records published OpenCashier releases only.
It follows a lightweight Keep a Changelog structure and focuses on externally visible changes instead of mirroring commit history.
History that predates changelog adoption is backfilled at the public tag level. Work before the first public tag is summarized through that first tagged release instead of being reconstructed commit by commit.
Chinese version: CHANGELOG.zh-CN.md
v0.2.0-beta.3 - 2026-03-25
- Prepared
@opencashier/sdkfor direct npm distribution with publish metadata, a package README and LICENSE, a packaged-consumer smoke test, and a manual GitHub workflow that uses npm OIDC trusted publishing instead of a long-lived write token.
- Updated the repo and public SDK docs to use npm installation as the default external developer path instead of requiring developers to build the SDK tarball from the monorepo first.
- Fixed the release pipeline so each published tag now creates the GitHub Release and pushes the matching GHCR
opencashier-apiandopencashier-webimages in one flow, avoiding release and image tag mismatches.
v0.2.0-beta.1 - 2026-03-19
- Added admin login and session APIs plus a sign-in flow in
apps/web, with configurable local development credentials. - Added
examples/merchant-quickstart, a runnable merchant integration sample that provisions app-scoped provider config, redirects tocashierUrl, verifies notifications, and rechecks order status on the result page. - Added the workspace package
@opencashier/sdkfor Node and TypeScript merchant integrations, covering HMAC request signing, order and refund resources, provider config bootstrap, and notification verification.
- Merchant provider configuration can now be managed per app, which removes the need to start
apps/webfor the defaultalipay_pagequickstart path. - The default deployment stack now uses the internal PostgreSQL alias
opencashier-postgreswhen the bundled database service is enabled. - Repository README files now point deployment and merchant integration guides to the public documentation site instead of keeping long copies in the main repo.
v0.1.0-beta.4 - 2026-03-17
- Added
OPENCASHIER_API_NETWORK_ALIASsupport to the reverse-proxy deployment overlay so upstream gateways can route directly to the API container when needed.
- Expanded reverse-proxy deployment guidance to cover both web and API container aliases, making split routing setups easier to wire into an existing gateway network.
v0.1.0-beta.3 - 2026-03-17
- Added optional mirror registry publishing for image releases, including documented environment variable examples for teams that need a mainland China registry path.
- Consolidated API and web image publishing into one release workflow so public tags produce consistent version,
sha-*, andlatesttags across both images. - Removed the default
pull_policy: alwaysfrom the deployment compose file so mirrored and private registries can control pull behavior explicitly.
v0.1.0-beta.2 - 2026-03-17
- Added
docker-compose.deploy.reverse-proxy.ymlas an optional overlay for deployments that sit behind an existing Dockerized reverse proxy such as Nginx, Caddy, or Traefik.
- Added
WEB_PUBLISHED_BINDso direct-exposure deployments can bind the web container to a specific host address instead of always exposing0.0.0.0. - Switched the production API image to a deploy-oriented runtime layout and in-image Prisma schema sync path, reducing reliance on the full workspace layout at container startup.
- Updated the deployment examples to use explicit version tags as the default image reference for public deployments.
v0.1.0-beta.1 - 2026-03-16
- Published the first public OpenCashier beta with a hosted cashier flow, merchant order and refund APIs, merchant notification forwarding with retries, and initial admin-side provider configuration management.
- Added the first image-based deployment baseline, including Dockerfiles,
docker-compose.deploy.yml,.env.deploy.example, and tag-triggered image publishing to GHCR. - Added the first public merchant integration and deployment guides, smoke-test scripts, and community health files for external adopters.
- Switched the web app to runtime API base URL injection so image deployments can change API endpoints without rebuilding frontend assets.
- Documented the initial channel availability baseline: Alipay and Stripe available, WeChat Pay in testing, and PayPal reserved but not yet open.