Skip to content

Hazakura Editor v0.20.0 Developer / GitHub Preview

Pre-release
Pre-release

Choose a tag to compare

@lero003 lero003 released this 18 Jun 10:34
· 64 commits to main since this release

Hazakura Editor 0.20.0 Warning-expected DMG Preview

Developer / GitHub full preview after App Store approval

Status: Published as a warning-expected GitHub prerelease on
2026-06-18. Local and remote asset verification passed.

v0.20.0 is the Developer / GitHub lane checkpoint after the initial
0.19.0 Mac App Store approval. It collects the post-approval docs
closeout, v0.20 Sakura workspace ergonomics polish, and Developer /
GitHub DMG signing-lane cleanup into one warning-expected downloadable
preview.

The release boundary stays unchanged: Markdown source remains canonical,
Safe Editor remains primary, and Agent Workbench remains a separate
Developer / GitHub-lane trust boundary. The App Store lane remains
helper-free and omits Agent Workbench, CLI Agent launch, Apple Local
Assist helper, external AI/API calls, and arbitrary command execution
surfaces.

This is a warning-expected macOS DMG preview. The GitHub DMG app is
Developer ID Application signed, but it is not notarized or stapled, so
macOS security warnings may still appear.

This is not an App Store, TestFlight, notarized, stapled, updater, or
production-ready distribution.

Download

The Apple Silicon preview asset is:

hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg

It packages the Developer / GitHub lane bundle:

Hazakura Editor Dev.app

The Developer / GitHub lane keeps Agent Workbench and Apple Local Assist
helper behavior available under their existing explicit boundaries and
uses bundle identifier lab.hazakura.note.dev. The App Store lane
remains the separate helper-free published lane.

What Changed Since 0.19.0

App Store Approval Closeout

  • Records that 0.19.0 passed App Review and is published on the Mac
    App Store.
  • Moves the tracked current queue away from App Store submission-prep
    wording and toward post-approval cleanup plus v0.21 e-book Mode PoC
    preparation.
  • Keeps App Store-specific account notes, reviewer material, signing
    details, and screenshots out of tracked public docs.

v0.20 Sakura Workspace Ergonomics

  • Makes the normal Safe Editor workspace sidebar collapse / restore
    control easier to reach from the main chrome.
  • Keeps active file path context in a thin bottom full-path copy bar in
    the central editor pane, clipped safely for long paths.
  • Strengthens Markdown preview hierarchy with a card-like reading
    surface for headings, quote/readout areas, and code.
  • Uses Sakura accenting to make the selected workspace file clearer.
  • Keeps New File on existing menu, shortcut, command-palette, and
    workspace-file paths rather than reintroducing a tab-row +
    affordance.

Developer / GitHub Preview Lane

  • Updates the warning-expected DMG preview lane so GitHub release DMGs
    require Developer ID Application signing.
  • Keeps Developer ID signing separate from notarization; the release is
    still warning-expected until notarization and stapling are completed
    in a future lane.
  • Clarifies that App Store submit packages, GitHub DMG previews, local
    smoke apps, and Developer / GitHub builds remain separate artifacts.

Future Planning

  • Reconstructs the next product arc around:
    AIが書いたMarkdownを、本として読み、差分で直す。
  • Adds or updates planning notes for e-book Mode / EPUB export, L Mode
    relationship, AI Markdown proposal ingest, native-feeling macOS UI,
    and speculative local AI boundaries.

Release Boundary

v0.20.0 does not add:

  • New App Store submission or TestFlight upload.
  • Notarization, stapling, updater, or installer-grade distribution.
  • New Agent Workbench capability, provider-add UI, general terminal,
    LSP, Git integration, arbitrary command input, project-wide indexing,
    auto-apply, or auto-commit behavior.
  • Preview DOM editing, contenteditable, HTML as the saved canonical
    model, hidden save-time rewriting, network fallback, tool calling,
    auto-save, or automatic AI application.
  • e-book Mode implementation; this release only prepares the docs and
    roadmap for the v0.21 PoC.

Known Limitations

  • The DMG is Apple Silicon / aarch64 only.
  • The DMG app is Developer ID signed but not notarized or stapled.
    Gatekeeper may still warn or require explicit user approval.
  • Apple Local Assist remains alpha / experimental and depends on macOS
    26+ Apple Foundation Models availability, local Apple Intelligence
    state, and supported language / locale.
  • Agent Workbench remains outside the App Store lane and depends on the
    selected allowlisted provider's own behavior.
  • The production bundle still carries the known Vite chunk-size warning
    from editor / preview dependencies.
  • Broader native macOS appearance work is intentionally deferred until a
    focused audit picks one surface.
  • npm audit reports one low-severity DOMPurify advisory
    (GHSA-vxr8-fq34-vvx9). The current Markdown preview sanitization
    path does not use RETURN_TRUSTED_TYPE, trustedTypes, or
    clearConfig; this is tracked as a dependency-update follow-up rather
    than a v0.20 release blocker.

Local Verification Before Publication

Required gates for this warning-expected DMG preview:

npm ci
npm run test
npm run build:vite
cargo fmt --manifest-path src-tauri/Cargo.toml -- --check
cargo test --manifest-path src-tauri/Cargo.toml
npm run build:apple-assist-helper:live
npm run build:dmg-preview
git diff --check
npm audit
cargo audit --file src-tauri/Cargo.lock

Review-only dependency checks:

npm outdated
cargo update --manifest-path src-tauri/Cargo.toml --dry-run

Local Verification Result

Passed on 2026-06-18.

  • npm ci passed. It reported one low-severity DOMPurify advisory; no
    high or critical npm advisory was reported.
  • npm run test passed: 99 files / 804 tests.
  • npm run build:vite passed with the existing chunk-size warnings.
  • cargo fmt --manifest-path src-tauri/Cargo.toml -- --check passed.
  • cargo test --manifest-path src-tauri/Cargo.toml passed: 283 tests.
  • npm run build:apple-assist-helper:live passed; the live helper build
    completed and the availability probe returned available.
  • npm run build:dmg-preview passed. It built the Developer / GitHub
    lane, re-signed Hazakura Editor Dev.app with Developer ID
    Application, built the helper-free App Store preview bundle, generated
    the DMG, ran hdiutil verify, and verified the checksum file.
  • Developer / GitHub app metadata matched: version 0.20.0, bundle
    identifier lab.hazakura.note.dev.
  • Developer / GitHub app passed
    codesign --verify --deep --strict --verbose=2.
  • spctl --assess --type execute rejected the Developer / GitHub app
    with source=Unnotarized Developer ID, which is expected for this
    warning-expected, not-notarized release lane.
  • Mounted DMG app metadata matched version 0.20.0 and bundle
    identifier lab.hazakura.note.dev, passed codesign verification, and
    launched successfully; a new hazakura-editor process was observed
    and then stopped.
  • npm run probe:macos-distribution -- "src-tauri/target/release/bundle/macos/Hazakura Editor.app"
    passed for the helper-free App Store preview bundle: bundled notices
    were present, the Apple Local Assist helper was absent, broad network
    server / Apple-events entitlements were absent, and the local
    entitlement gate was skipped as expected for the launchable preview.
  • cargo audit --file src-tauri/Cargo.lock exited 0 with 17 allowed
    warnings, primarily existing Tauri / GTK stack warnings,
    proc-macro-error, unic-*, and glib unsoundness warnings.
  • npm outdated reported newer @tauri-apps/api, @types/react,
    dompurify, and vitest versions. These are freshness signals only
    and were not folded into this release.
  • cargo update --manifest-path src-tauri/Cargo.toml --dry-run
    reported compatible update candidates and did not update the lockfile.
  • git diff --check passed.
  • Release pre-check grep hits were reviewed. Local-path hits were test
    fixtures or existing historical release-precheck wording, GitHub /
    TODO hits were public repository links or "TODO not needed" wording,
    and security-word hits in source were diagnostics / sanitizer wording
    or tests rather than credentials. Diff-scoped secret grep returned no
    hits.

Local artifact:

src-tauri/target/release/bundle/dmg/hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg

SHA-256:

eaa5f576d4ec9aeb69429102d527778264f4d2776b03ba800c34911514fd92d9

Publication State

  • Tag: v0.20.0.
  • GitHub Release:
    https://github.com/lero003/hazakura-editor/releases/tag/v0.20.0.
  • DMG asset:
    hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg.
  • Checksum asset:
    hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg.sha256.

Older public tags and releases remain immutable.

Remote Verification Result

Passed on 2026-06-18.

  • GitHub Release:
    https://github.com/lero003/hazakura-editor/releases/tag/v0.20.0.
  • The release is a prerelease, not a draft.
  • Uploaded assets:
    hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg and
    hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg.sha256.
  • The downloaded checksum file verified the downloaded DMG:
    hazakura-editor-dev_0.20.0_aarch64-warning-expected.dmg: OK.
  • hdiutil verify passed on the downloaded DMG.
  • Mounted downloaded DMG app metadata matched version 0.20.0 and
    bundle identifier lab.hazakura.note.dev.
  • Mounted downloaded DMG app passed
    codesign --verify --deep --strict --verbose=2.
  • Mounted downloaded DMG app launched successfully; a new
    hazakura-editor process was observed and then stopped.