Repository navigation
Release package #12
Description
Parent
What to build
The build produces the release package that both distribution channels use, following the release standards in the repository's release document.
Acceptance criteria
- One command produces
github-file-hider-YYYY.MM.DD.N.zipwithmanifest.jsonat the package root. - The manifest
versionandversion_namefollow the UTC date format, and the daily counter never reuses a published version (it reads the existingv*tags). - The README explains local installation from the ZIP and how to replace it with a newer version.
- The publication workflow stays out of scope.
Activity
ribeirogab commentedon Oct 2, 2026
Update: the implementation was reverted in a619cac. This issue is reopened and its acceptance criteria are unchecked.
Built pnpm release with existing tag lookup, UTC versions, increasing daily counters, Chrome version validation, and a ZIP with manifest.json at its root. Documented local installation and updates. ZIP contents verified; 41 unit tests and 8 end-to-end tests passed. Publication remains outside scope.
Validation: pnpm check, pnpm typecheck, pnpm test (unit and fixture-routed Chromium end-to-end suites), and pnpm build passed.
Commit: dd35e17. No acceptance criteria deferred.
ribeirogab commentedon Oct 2, 2026
Built
pnpm release: it fetches the existing tags from origin (falling back to local tags offline), builds the extension, and writesgithub-file-hider-YYYY.MM.DD.N.zipto the repository root withmanifest.jsonat the archive root.versiondrops leading zeros (2026.10.2.1) andversion_namekeeps the public format (2026.10.02.1); the daily counter continues after the highestvYYYY.MM.DD.Ntag of the UTC date and the command refuses a version that is not greater than every published one. The README explains local installation from the ZIP and how to replace it with a newer version. Publication stays out of scope.Tests:
Commit: b0eaabd. Nothing deferred.