Skip to content

Push the tag with a command that actually pushes it #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devpeer-tom merged 1 commit into from
Aug 12, 2026
Merged

Push the tag with a command that actually pushes it #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ full semver, because Chrome rejects pre-release suffixes such as `1.1.0-rc.1`.

## [1.0.1] — 2026-08-12

No change to the extension itself. Every file under `src/` and `public/` is byte-identical
to 1.0.0 apart from the version string, and the built `dist/` reproduces the same content
digest 1.0.0 was built from.
No change to the extension itself. The only difference from 1.0.0 anywhere under `src/` or
`public/` is the version string in `public/manifest.json` — so the content digest below is
not the one 1.0.0 would have had, and could not be: the version is part of what is hashed.

What changes is that this is the first version you can check. 1.0.0 was uploaded to the
Chrome Web Store by hand, with nothing published to compare it against. 1.0.1 is built by
Expand Down
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,9 @@ exact commit. The zip attached to the release is the same file that goes to the
and you can prove it:

```bash
gh release download v1.0.0 --repo devpeer-net/website-blocker
sha256sum -c website-blocker-1.0.0.zip.sha256
gh attestation verify website-blocker-1.0.0.zip --repo devpeer-net/website-blocker
gh release download v1.0.1 --repo devpeer-net/website-blocker
sha256sum -c website-blocker-1.0.1.zip.sha256
gh attestation verify website-blocker-1.0.1.zip --repo devpeer-net/website-blocker
```

The last command trusts nothing in this repository — not the release page, not the
Expand All @@ -129,7 +129,7 @@ uploaded**, before any of that rewriting. Every release publishes a content dige
same hashes, so the two can be compared:

```bash
node scripts/verify-install.mjs --zip website-blocker-1.0.0.zip --installed <extension-dir>
node scripts/verify-install.mjs --zip website-blocker-1.0.1.zip --installed <extension-dir>
```

If the digests agree, the package Google received and signed is this release, file for
Expand Down
2 changes: 1 addition & 1 deletion docs/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ pnpm release:bump 1.1.0 # package.json, manifest, and a dated CHANGELOG h
$EDITOR CHANGELOG.md # say what changed under the new heading
git commit -am "Release 1.1.0"
git tag v1.1.0
git push --follow-tags
git push origin main v1.1.0 # not --follow-tags: that pushes annotated tags only
```

The tag is the trigger. Everything below happens on its own, except the one step that
Expand Down
2 changes: 1 addition & 1 deletion scripts/bump-version.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,5 +73,5 @@ writeFileSync(changelogPath, opened)
console.log(`bumped to ${version}`)
console.log('next: describe the change under the new CHANGELOG heading, then')
console.log(
` git commit -am "Release ${version}" && git tag v${version} && git push --follow-tags`,
` git commit -am "Release ${version}" && git tag v${version} && git push origin HEAD v${version}`,
)
Loading