OverviewFilesCommitsIssuesDocsReleasesPeers

pearbrowser-desktop commits / 85a80ad

mark legacy browser release records as historical
85a80ad6582f566e26e6f4763ca8e9632b333693
by bigdestiny2 <33146784+bigdestiny2@users.noreply.github.com> · 2026-07-22T23:41:20.000Z

Changed files (10) +31 -0

CHANGELOG.md +4 -0
……@@ -1,5 +1,9 @@
11# Changelog
22
3> Historical release record. Legacy remote Pear references below are retained
4> only to explain past releases; they are not current installation, launch, or
5> recovery instructions. Current native delivery requires a verified package.
6
37## v0.7.1 — 2026-07-16
48
59Corrective desktop transport release. The backend RPC handlers were healthy,
docs/DEEP_AUDIT_CATALOG_SEARCH_NAMING_NOSTR_2026-06-21.md +3 -0
……@@ -1,5 +1,8 @@
11# Deep Audit: Catalogue, Search, Naming, and Nostr Bridge
22
3> Historical audit record. Any legacy remote app references document the state
4> observed in June 2026 and are not current browser behavior or launch advice.
5
36Date: 2026-06-21
47
58This pass reviewed the four discovery surfaces that have to agree with each other:
docs/MANUAL_RELEASE_SMOKE_2026-06-23.md +3 -0
……@@ -1,5 +1,8 @@
11# Manual Release Smoke - 2026-06-23
22
3> Historical v2 smoke checklist. Do not execute its legacy app references;
4> current release proof uses verified native packages and the v3 release gates.
5
36Purpose: final human-run smoke checklist for the PearBrowser community release.
47Automated tests and fresh-peer verifiers prove most protocol and catalogue
58behavior, but these checks cover UI flows, third-party trust decisions, and
docs/RELEASE_NOTES_v0.7.0.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.7.0
22
3> Historical release notes. References to legacy remote Pear artifacts are not
4> installation or launch instructions for the current product.
5
36PearBrowser `v0.7.0` makes browser protection and extensions peer-to-peer.
47Content Shield can now subscribe to checksum-verified filter-list Hyperdrives,
58hot-swap updates, and keep blocking offline. Pear Plugins install from ordinary
docs/RELEASE_NOTES_v0.7.1.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.7.1
22
3> Historical release notes. References to legacy remote Pear artifacts are not
4> installation or launch instructions for the current product.
5
36PearBrowser `v0.7.1` is a corrective transport release for the desktop browser.
47It fixes the cluster of `RPC timeout` messages that could appear in Settings
58after a renderer reload or live-update handoff even though the identity,
docs/RELEASE_v0.6.0_OPERATOR.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.6.0 — operator release runbook
22
3> Historical v2 operator record. It must not be reused to publish, launch, or
4> recover current builds; use the verified native-package v3 release workflow.
5
36Date: 2026-07-15
47Tag: `v0.6.0`
58Repo: `bigdestiny2/pearbrowser-desktop`
docs/RELEASE_v0.6.1_OPERATOR.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.6.1 — corrective release runbook
22
3> Historical v2 operator record. It must not be reused to publish, launch, or
4> recover current builds; use the verified native-package v3 release workflow.
5
36Date: 2026-07-15
47Tag: `v0.6.1`
58Repo: `bigdestiny2/pearbrowser-desktop`
docs/RELEASE_v0.7.0_OPERATOR.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.7.0 — release runbook
22
3> Historical v2 operator record. It must not be reused to publish, launch, or
4> recover current builds; use the verified native-package v3 release workflow.
5
36Date: 2026-07-16
47Tag: `v0.7.0`
58Repo: `bigdestiny2/pearbrowser-desktop`
docs/RELEASE_v0.7.1_OPERATOR.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop v0.7.1 — release runbook
22
3> Historical v2 operator record. It must not be reused to publish, launch, or
4> recover current builds; use the verified native-package v3 release workflow.
5
36Date: 2026-07-16
47Tag: `v0.7.1`
58Repo: `bigdestiny2/pearbrowser-desktop`
docs/TEST-COMMAND-MATRIX-2026-06-23.md +3 -0
……@@ -1,5 +1,8 @@
11# PearBrowser Desktop Test Command Matrix
22
3> Historical v2 command matrix. Legacy remote-app commands are evidence of
4> past coverage only; current validation must not execute remote app code.
5
36Generated: 2026-06-23
47Loop candidate: `pearbrowser-desktop-test-matrix`
58Autonomy level: Level 1 docs-tests