Skip to content

HEPHA v0.1.0-alpha.2 — Public Alpha

Pre-release
Pre-release

Choose a tag to compare

View all tags
@aboimpinto aboimpinto released this 05 Sep 23:10
· 19 commits to master since this release
v0.1.0-alpha.2
b13ee00
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

HEPHA v0.1.0-alpha.2

This public-alpha security refresh supersedes v0.1.0-alpha.1. It contains the
same HEPHA product capabilities and public-launch documentation, with patched
versions of dependencies identified by GitHub immediately after publication.

Security refresh

  • Updated Mermaid to the current compatible patched release.
  • Updated DOMPurify and Browserslist to patched runtime dependency versions.
  • Updated shell-quote, undici, PostCSS, and the affected esbuild range used by
    development and test tooling.
  • Enabled GitHub private vulnerability reporting, dependency alerts, and
    automated security updates.
  • Protected master with required pull requests, strict status checks, linear
    history, resolved conversations, and force-push/deletion prevention.

GitHub reported zero open Dependabot alerts on master after the dependency
update merged through the protected pull-request workflow.

Verification

  • Public release audit: passed with zero warnings and zero failures.
  • Type checking: passed.
  • Automated tests: 801 files, 6,160 passed, 1 todo.
  • Production build: passed.
  • Required pull-request checks: passed.

The release tag is created only after the post-merge master checks pass.

Upgrade from alpha.1

No HEPHA workflow or SQLite schema migration is introduced by this release.
Check out v0.1.0-alpha.2 and run:

pnpm install --frozen-lockfile

As with every early-alpha update, back up local .hepha/ state before moving
between versions.

Known limitations

HEPHA remains early-alpha, local-first software. Interfaces and storage
contracts may change before beta. The live supervised clean-clone walkthrough
remains a disclosed follow-up; its automated synthetic-demo verification
passes. See the README and roadmap for the supported environment and current
direction.

Paulo Aboim Pinto

Assets 2
Loading