Skip to content

Releases: shruggietech/glitchpad

Glitchpad v0.1.4

Choose a tag to compare

@github-actions github-actions released this 29 Sep 14:56
1d7dcd4

Glitchpad v0.1.4 Brand and Shell Release

Glitchpad v0.1.4 packages the completed BrandBuilder 2.0.3 integration and AppFrame layout work on all four supported platforms. It follows the v0.1.3 corrective release and keeps the stable text-family support matrix.

What changed

  • The application shell uses the governed BrandBuilder AppFrame for safe areas, display cutouts, orientation, text scaling, menu geometry, and on-screen-keyboard insets.
  • The formal Glitchpad brand 1.1.1 kit refreshes Android launcher artwork and supplies separate ordinary and maskable web icons. The approved square identity and existing Windows and macOS icon binaries remain consistent with that kit.
  • The public site and package assets use the pinned kit with exact-copy and conformance checks.
  • Compatible npm, Cargo, and Gradle wrapper updates are included after their platform checks pass.
  • The already merged S039 and S040 image preview, inspection, animation, and selected ICO export code is present in the application. Image formats remain outside the stable support matrix and operating-system associations until the v0.2.0 conformance and activation work in #75 and #76 is complete.

Issue and change traceability

  • #194 and #195 delivered the S039 and S040 image implementation without stable image activation.
  • #197 delivered the AppFrame shell and its desktop and Android geometry evidence.
  • #205 closed #202, #203, and #204 through S042 by importing the formally released BrandBuilder kit and refreshing platform assets.
  • #199 updated the Gradle wrapper, #207 updated the Tauri Rust crates, and #208 updated compatible npm packages after their CI checks passed.
  • #75 and #76 remain open for stable image conformance and activation. #66 remains open for post-release manual and physical-device validation.

Packages and trust states

The release contains eight application packages: an unsigned Windows NSIS installer and portable ZIP, a universal macOS DMG with an ad-hoc signature that is not notarized, Linux AppImage and Debian packages with repository attestations, and Android universal APK, ARM64 APK, and AAB packages signed by the existing project-owned update key. Windows SmartScreen and macOS Gatekeeper may warn because this community release does not use paid platform trust programs.

Each package has SHA-256 checksums, software-bill-of-materials data, provenance, license notices, the source revision, and machine-readable trust evidence. Desktop evidence bundles bind practical-use receipts to final package manifests. The Android matrix retains API 24 and API 36 provider-backed delivery checks.

Supported capabilities and limits

The stable support claim remains local Markdown, Mermaid, plain-text, and recognized source files with view, edit, save, search, inspection, recovery, and compact multi-document behaviors. Image implementations are included for in-app use but are not declared stable or associated with operating-system file openers in this release. PDF, DOCX, and ODT remain planned. The application has no account, telemetry, or file-content network dependency, and remote document resources remain blocked.

Installation and feedback

Download packages from the official GitHub release, verify SHA256SUMS for SHA-256 integrity, and review the platform trust evidence before installation. Report defects through the repository issue tracker. Manual real-world validation remains post-release work tracked by issue #66.

Release boundary

This document is the v0.1.4 release-note authority. Publication uses the exact reviewed release merge commit and its annotated v0.1.4 tag. The published v0.1.3 release and its historical records remain unchanged.

Glitchpad v0.1.3

Choose a tag to compare

@h8rt3rmin8r h8rt3rmin8r released this 13 Sep 04:44
82dda87

Glitchpad v0.1.3 Corrective Release

Glitchpad v0.1.3 is the third corrective release following v0.1.0. It packages the practical-use repairs from S035, the sectioned specification documentation from S036, the post-merge automation from S037, and the exact-package evidence and release reconciliation from S038 without broadening the stable format matrix.

What changed

  • S035 (#171) keeps Markdown usable across every supported opening path, including native file-association delivery, even when preview rendering fails.
  • Markdown results remain scoped to the current session, revision, and render generation, and source recovery remains available without exposing source while a preview is pending.
  • S035 (#172) reserves shell chrome so the compact application menu, document controls, and scrollable content no longer overlap.
  • Desktop candidate workflows record content-free practical-use receipts that bind successful installed or clean-host checks to the exact final package manifest and reviewed source revision. Windows installer and portable lifecycles exercise a real opt-in packaged Markdown failure through source recovery and a successful retry, and record separate shell-geometry results at 100, 125, 150, and 200 percent scaling.
  • Release assembly refuses missing, duplicated, stale, content-bearing, or absent required practical-use passes. The Intel macOS hosted smoke recorded a 3.229-second cold-start p95 above its performance target, while install, launch, document delivery, edit, save, recovery, removal, and universal-architecture checks passed; the unchanged receipt is included in the macOS evidence bundle.
  • Public technical documentation is split into navigable section pages generated from one normative specification source.
  • Release-authorized documentation publication and post-merge branch cleanup are automated with explicit concurrency, provenance, and failure reporting. A normal main push validates the site but cannot deploy release claims before the official release exists.

Issue traceability

  • #171: prevent universal Markdown preview failure across native and in-app open paths.
  • #172: reserve shell chrome and eliminate application-menu overlap.
  • #66: perform post-release manual and physical-device validation (remains open and is not claimed by this release).

Packages and platforms

The official release contains eight application packages: an unsigned Windows NSIS installer and portable ZIP, a universal macOS DMG with an ad-hoc signature that is not notarized, Linux AppImage and Debian packages with repository attestations, and Android universal APK, ARM64 APK, and AAB packages signed by the stable project-owned update key. Windows SmartScreen and macOS Gatekeeper may warn because this zero-cost community release does not use paid platform trust programs.

Each package is accompanied by SHA-256 checksums, software-bill-of-materials data, provenance, license notices, the reviewed source revision, and machine-readable trust evidence. Desktop release assembly additionally requires practical-use receipts bound to the exact candidate package manifest. Android retains API 24 and API 36 provider-backed delivery evidence and exact release-package inspection.

Supported capabilities and limits

Glitchpad v0.1.3 supports local Markdown, Mermaid, plain-text, and recognized source files with the released view, edit, save, search, inspection, recovery, and compact multi-document behaviors. Image, PDF, DOCX, and ODT support remains planned for later releases and is not included here. The application has no account, telemetry, or file-content network dependency. Remote document resources remain blocked.

Installation and feedback

Download packages only from the official GitHub release, verify SHA256SUMS, and review the platform trust evidence before installation. Report defects through the repository issue tracker. Manual real-world validation remains post-release work tracked by issue #66.

Release boundary

This release is published from the exact owner-approved v0.1.3 tag on reviewed S038 merge commit 82dda87e1ad0428bf5d082394b9551cbd22fb844. The published v0.1.2 release and its historical records remain immutable.

Glitchpad v0.1.2

Choose a tag to compare

@github-actions github-actions released this 11 Sep 05:34
1d9b227

Glitchpad v0.1.2 Corrective Release

Glitchpad v0.1.2 is the second corrective release following v0.1.0. It combines the public presentation and brand corrections from S029, the Markdown and compact-shell corrections from S030, the Android system file-opening corrections from S031, and the pre-release dependency security maintenance from S033 without broadening the stable format matrix.

What changed

  • Repository and website branding now use the current Glitchpad brand authority, legible lockups, ShruggieTech attribution, the approved slogan, compact actions, current release claims, and release-consistent specification dates and versions.

  • A document-scoped failure boundary keeps the application shell available and offers explicit source recovery for Markdown.

  • Markdown render results are accepted only for the current session, revision, and render generation.

  • Rendered mode shows a constant pending state without exposing source-derived content.

  • The application menu trigger remains fixed at the upper-left and its popup does not participate in document layout.

  • The README retains its supported-platform table while dropping the oversized Platforms badge.

  • Packaged Windows validation exercises two complex Markdown documents in both open orders and records active-content evidence.

  • Android exact-type file opening no longer depends on a filename or extension appearing in an opaque provider URI.

  • Android package evidence retains complete intent-filter groups so invalid merged matcher semantics cannot pass as a flat inventory.

  • Android cold-start and warm intents now drain through a permission-scoped native event into the bounded document gateway, so accepted provider content reaches the viewport and native source authority is released when the session closes.

  • Installed-package checks on API 24 and API 36 prove resolver eligibility plus cold and warm document delivery through scoped provider grants.

  • Providers that report only a generic binary media type for an opaque URI cannot be identified safely at resolver time. Glitchpad intentionally declines that ambiguous case instead of claiming every binary document; opening through the in-app picker remains available.

  • Android callers can supply broad request types such as text/*, application/*, or */*; Android matches those requests to Glitchpad's exact declarations. Glitchpad does not declare wildcard types and still applies its normal content detection after delivery.

  • Next.js was patched to 16.3.3 and the development-only transitive smol-toml resolution was patched to 1.7.1 before publication to clear the known release-blocking dependency advisories without changing product behavior.

Issue traceability

  • #151: repair README logo rendering.
  • #152: restore legible site lockups.
  • #153: align landing-page copy, attribution, actions, and navigation.
  • #154: deploy current release claims and prevent stale production content.
  • #155: correct technical-specification version and date authority.
  • #156: synchronize the authoritative brand kit.
  • #160: eliminate blank Markdown viewports and preserve usable content across sequential opens.
  • #161: prevent raw Markdown source from flashing while rendered preview is pending.
  • #162: keep the application menu trigger stable and clear of the document scrollbar.
  • #163: remove the redundant Platforms badge without weakening platform documentation.
  • #159: expose Glitchpad as an Android opener for released exact media types and prove resolved cold and warm delivery.
  • #167: clear the release-blocking Next.js and smol-toml dependency advisories with compatible patch releases.

Packages and platforms

The official release contains eight application packages: an unsigned Windows NSIS installer and portable ZIP, a universal macOS DMG with an ad-hoc signature that is not notarized, Linux AppImage and Debian packages with repository attestations, and Android universal APK, ARM64 APK, and AAB packages signed by the stable project-owned update key. Windows SmartScreen and macOS Gatekeeper may warn because this zero-cost community release does not use paid platform trust programs.

Each package is accompanied by SHA-256 checksums, software-bill-of-materials data, provenance, license notices, the reviewed source revision, and machine-readable trust evidence.

Supported capabilities and limits

Glitchpad v0.1.2 supports local Markdown, Mermaid, plain-text, and recognized source files with the released view, edit, save, search, inspection, recovery, and compact multi-document behaviors. Image, PDF, DOCX, and ODT support remains planned for later releases and is not included here. The application has no account, telemetry, or file-content network dependency. Remote document resources remain blocked.

Installation and feedback

Download packages only from the official GitHub release, verify SHA256SUMS, and review the platform trust evidence before installation. Report defects through the repository issue tracker. Manual real-world validation remains post-release work tracked by issue #66.

Release boundary

This reviewed document is the official v0.1.2 release-note authority. The S034 pull request does not create a tag or release; publication remains restricted to the exact owner-approved v0.1.2 tag on the reviewed S034 merge commit.

Glitchpad v0.1.1

Choose a tag to compare

@github-actions github-actions released this 09 Sep 04:46
eb97d86

Glitchpad v0.1.1 Corrective Release

Glitchpad v0.1.1 is the corrective successor to the initial community release. It keeps the same local-first Markdown, Mermaid, plain-text, and supported-source capabilities while fixing the application shell so the requested document owns the viewport.

What changed

  • A normal launch starts empty instead of opening synthetic demonstration documents.
  • Opening a TXT, Markdown, Mermaid, or supported source file displays the requested content immediately.
  • The tab strip appears only when at least two documents are open, and every visible tab has its own close control.
  • A compact application menu replaces the crowded always-visible command rows.
  • Outline, print, search, file information, and secondary panels now appear only when relevant to the active document.
  • Packaged Windows smoke coverage verifies launch, native file-open delivery, and visible document content.

Downloads

  • Windows 11 x86_64: NSIS installer and portable ZIP.
  • macOS 13+: universal DMG for Apple Silicon and Intel.
  • Linux x86_64: AppImage and Debian package, built against Ubuntu 22.04.
  • Android 7.0+: universal APK, ARM64 APK, and AAB.

Trust and installation

Windows packages are unsigned community artifacts and may trigger Microsoft Defender SmartScreen. Verify the SHA-256 checksum from this release, then use the ordinary per-application Windows approval control if you choose to run it. Do not disable SmartScreen globally.

The macOS application uses an ad-hoc signature and the DMG is not notarized by Apple. Verify its SHA-256 checksum, then use the ordinary Open Anyway control for this application if macOS blocks first launch. Do not disable Gatekeeper globally.

Linux artifacts carry GitHub repository-bound attestations. Android artifacts are signed with the same stable project-owned update key as v0.1.0 so existing installations can upgrade; verify the published certificate fingerprint before sideloading.

Integrity evidence

Every package family includes final-byte checksums, a CycloneDX SBOM, provenance, Apache-2.0 license material, notices, source revision, version, and machine-readable trust evidence. Download only from the official GitHub release page and compare the artifact SHA-256 before installation.

Known limits and feedback

Image, PDF, DOCX, and ODT viewing remain planned for later releases and are not supported in v0.1.1. Manual accessibility, physical-device, platform-polish, and real-world validation remains post-release work under issue #66. Report defects through the project issue tracker so they can be addressed before v0.2 feature development.

Glitchpad v0.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Sep 01:14
d474302

Glitchpad v0.1.0 Community Release

Glitchpad v0.1.0 is the first installable community release. It provides local Markdown and Mermaid viewing and editing, plain-text and supported source editing, compact document tabs, metadata inspection, recovery, native desktop file delivery, and Android document intents. Files remain local; Glitchpad has no account, cloud synchronization, or telemetry service.

Downloads

  • Windows 11 x86_64: NSIS installer and portable ZIP.
  • macOS 13+: universal DMG for Apple Silicon and Intel.
  • Linux x86_64: AppImage and Debian package, built against Ubuntu 22.04.
  • Android 7.0+: universal APK, ARM64 APK, and AAB.

Trust and installation

Windows packages are unsigned community artifacts and may trigger Microsoft Defender SmartScreen. Verify the SHA-256 checksum from this release, then use the ordinary per-application Windows approval control if you choose to run it. Do not disable SmartScreen globally.

The macOS application uses an ad-hoc signature and the DMG is not notarized by Apple. Verify its SHA-256 checksum, then use the ordinary Open Anyway control for this application if macOS blocks first launch. Do not disable Gatekeeper globally.

Linux artifacts carry GitHub repository-bound attestations. Android artifacts are signed with the stable project-owned update key; verify the published certificate fingerprint before sideloading.

Integrity evidence

Every package family includes final-byte checksums, a CycloneDX SBOM, provenance, Apache-2.0 license material, notices, source revision, version, and machine-readable trust evidence. Download only from the official GitHub release page and compare the artifact SHA-256 before installation.

Known limits and feedback

Image, PDF, DOCX, and ODT viewing are planned for later releases and are not supported in v0.1.0. Manual accessibility, physical-device, platform-polish, and real-world validation begins after publication under issue #66. Defects reported after this first release will be handled before v0.2 feature development.