Skip to content

Releases: bitaxeorg/legitlist

v1.1.0

12 Mar 19:03

Choose a tag to compare

legitlist v1.1.0

This release stabilizes legitlist for public end-to-end testing and hardens the vendor review/sync pipeline.

Highlights

  • Switched Framer sync to soft-sync mode (no automatic stale-item deletion)
  • Visibility model standardized around vendor active status
  • Vendor filename guardrails strengthened in local + CI validation
  • HTTPS-only validation enforced for website and social URLs
  • Workflow hardening with read-only token permissions and updated Actions runtime
  • Mock data reset to 15 vendors covering all supported regions
  • Mock logos updated to distinct monochrome assets for better visual QA
  • Logo CDN URLs pinned to commit SHA to avoid stale cache artifacts

Current status

  • Validation checks are green
  • Sync workflow is stable across repeated runs
  • Ready for full public-flow E2E testing

v1.0.0

12 Mar 15:10

Choose a tag to compare

legitlist v1.0.0

legitlist is the community-verified list of trusted Bitaxe vendors.

Open-source hardware needs open-source trust. This release defines the public process for getting listed, reviewing vendors in the open, and keeping the directory transparent, auditable, and community-driven.

What legitlist is

  • a public registry of trusted Bitaxe sellers
  • a transparent review process run through GitHub
  • a structured vendor data system with automatic validation
  • an automated sync from approved listings to Framer CMS

What ships in v1.0.0

Public vendor listing workflow

  • step-by-step vendor onboarding guide for non-technical users
  • browser-only submission flow
  • structured pull request form for vendor details and community context

Validation and data integrity

  • standard vendor listing format in vendors/{slug}.json
  • vendor logo support in logos/{slug}.{ext}
  • automatic validation for required fields, naming consistency, and logo size
  • matching local and CI validation

Sync and publishing automation

  • automatic sync to Framer CMS after merge to main
  • managed collection upsert by vendor slug
  • publish/deploy flow with retries and diagnostics
  • changed-path detection to avoid unnecessary publishes
  • workflow concurrency protection

Open review and accountability

  • public discussion on every listing through pull requests
  • community reporting flow for concerns
  • support for listing updates, deactivation, and removal in the open