Skip to content

EasyCard Digital Commerce Platform 1.1.0-rc.2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@wisebuilder wisebuilder released this 12 Aug 17:31
v1.1.0-rc.2
2106ff9

EasyCard Digital Commerce Platform 1.1.0-rc.2

Single-binary release packages (no source code). This is a release candidate, not a production-readiness approval.

Downloads

File Description
EasyCard-1.1.0-rc.2-windows-amd64.zip Windows x64 (cardgo.exe)
EasyCard-1.1.0-rc.2-windows-arm64.zip Windows ARM64 (cardgo.exe)
EasyCard-1.1.0-rc.2-linux-amd64.tar.gz Linux x64 (cardgo)
EasyCard-1.1.0-rc.2-linux-arm64.tar.gz Linux ARM64 (cardgo)
EasyCard-1.1.0-rc.2-darwin-amd64.tar.gz macOS Intel (unsigned cross-build, cardgo)
EasyCard-1.1.0-rc.2-darwin-arm64.tar.gz macOS Apple Silicon (unsigned cross-build, cardgo)
SHA256SUMS checksums

Linux install

curl -fsSL https://raw.githubusercontent.com/ecard8/EasyCard/main/install.sh | sudo bash

Pin version: sudo bash install.sh --version 1.1.0-rc.2

Linux updater readiness fix

The updater now uses /health to verify that the process and database started successfully. Operational warnings from /health/ready (for example backup age or channel health) are reported without falsely rolling back a healthy binary. A genuinely unreachable process still triggers the existing automatic binary rollback.

Mandatory storefront upgrade deadline

Customer-facing pages in this release remain available through 2026-12-30 in the configured site timezone. Beginning at 2026-12-31 00:00, the storefront and customer center display an upgrade-required page. The administration console, easycard update, health checks, APIs, static assets, and payment callbacks remain available so operators can upgrade safely without dropping trusted callbacks.

Release boundaries

  • Windows ARM64 and both macOS architectures still require target-device acceptance.
  • macOS archives are unsigned and unnotarized cross-builds; do not bypass Gatekeeper as a normal installation method.
  • Keep payment, notification, object-storage, and store-sharing integrations disabled until each one passes live acceptance with the deployment owner's real credentials.
  • Complete production-host, public HTTPS, backup/restore, policy, and compliance approval before commercial launch.

See repository README and the bilingual documents inside each archive for full installation, operations, and acceptance instructions.

Assets 9
Loading