GH Reloaded 1.0.0: release verification record
What was checked on the 1.0.0 candidate and on the published release, and what is still open. Date of the checks: 2026-10-17. Nothing here is claimed beyond its own evidence: a green CI run is not “live in the store”, and an anonymous check is not a signed-in one.
Candidate
| What |
Value |
| Release PR #77 head |
a6c2ecc16328aaecbf3495f7c6aa91fd9a3ad570 |
Merge commit and tag v1.0.0 |
9a63019dea835915edec33b505b4dccf54d524cc |
| Tree of both commits |
fb9b4560bfe267d8fcae22c8c6ef8d663b4df715 (git rev-parse <sha>^{tree} gives the same value), so the code tested on #77 is the code that was tagged |
| Release request commit |
1daaf61376e014b06d0c1b3b2e8360d668cc1a5a (Release-As: 1.0.0 as its last line) |
| GitHub Release |
v1.0.0, published 2026-10-17 07:23 UTC, asset gh-reloaded-1.0.0.zip (185,378 bytes) |
Scope
- In 1.0.0: dependency graph, Projects boards (dependency arrows, full-width board, Standup mode), Quick-create, My Issues by project, HTML preview, Settings with per-token Verify access (#75 / #76).
- Deferred to 1.1.0: PR triage (#78, draft #82) and any other open feature work. No PR triage file is in the ZIP.
- No version override is left in the Release Please configuration; a unit test asserts there is no
release-as key.
Automated evidence
| Check |
Result |
CI test job (npm test: unit and Playwright e2e) on #77 head a6c2ecc |
success: run 39013032697 |
CI on main at 1daaf61 |
success: run 39012815845 |
CI on main at the tag commit 9a63019 |
success: run 39013454818 |
Release workflow on 9a63019 (packaging, store credential check, upload and publish, ZIP attachment) |
success: run 39013454811 |
Local npm run test:unit on the tag |
226 tests, 226 pass, 0 fail |
Local npm test on the tag (full suite, Chromium) |
all 297 e2e tests pass |
A successful publish step shows the submission was accepted by the store API. It does not show that the listing is live (see the open items).
Package
gh-reloaded-1.0.0.zip downloaded from the release: 59 entries, 47 files. Its file list is identical to git ls-tree -r of v1.0.0 over the release.yml path list (manifest.json, background.js, background, features, icons, lib, options), and the contents match: the ZIP was extracted next to a git archive v1.0.0 of the same paths and diff -r reported no difference.- Every file the manifest references is in the ZIP; tests, fixtures,
docs/ and .plans/ are not.
Permissions and safety
git diff v0.14.0 v1.0.0 -- manifest.json changes two lines: version (0.14.0 to 1.0.0) and the description.- Permissions are unchanged:
storage, host access to https://api.github.com/*, content scripts on https://github.com/*. No new permission to accept on update.
- No remotely hosted code: a search of the shipped paths for remote
<script src>, eval( and new Function finds nothing.
- Release Please still owns the version, changelog, tag and release;
CHANGELOG.md is generated.
Smoke checklist
| Scenario |
Status |
| Unit and e2e suites on the candidate |
Verified (above) |
| Release, tag and ZIP match the candidate |
Verified (above) |
| Preparation and upgrade checks on public pages |
Recorded in #81 (anonymous) |
| This pass: the 1.0.0 ZIP loaded unpacked and driven on live github.com |
Not run in this pass |
| My Issues by project |
Maintainer, signed in |
| Private repositories and organization Projects |
Maintainer, signed in |
| Quick-create |
Maintainer, signed in |
| Verify access on a real token |
Maintainer, signed in |
| Update from a 0.14.0 install keeps settings and tokens |
Maintainer |
Open items