release
Skill2.3k starsChanged yesterdayMITView on GitHub
Walk the maintainer through releasing a new PiGallery2 version (man page, translations, Hungarian review, tests, docs screenshots, tag, GitHub release with notes and the CI zip, sample extension update). Use when the maintainer asks to do / prepare / cut a release.
- Commits and pushes
193 other projects use a version of this.
Trending
Quiet this year.about the whole repository
Most recently taken up by
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
- CoreBunch/Instatictheir own version, first seen Nov 16, 2026
- coredevices/PebbleOStheir own version, first seen Nov 16, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
Who's talking about bpatrik/pigallery2
- kvalev/photoprism“Import face region metadata”GitHub · Mar 26, 2022 · 4 reactions
- immich-app/immich“Mispositioned imported face regions and missing person thumbnails”GitHub · Sep 7, 2024 · 3 reactions
- A Hacker News story“PiGallery2 – self-hosted photo gallery website”Hacker News · Feb 14, 2020 · 2 points
- A Hacker News story“PiGallery2 – A fast directory-first photo gallery website, with rich UI”Hacker News · Feb 9, 2023 · 1 points
- homarr-labs/dashboard-icons“feat(icons): update pigallery2”GitHub · Aug 6, 2025
The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 17
Talked about on GitHub and Hacker News (17 times).
On GitHub · 15
- Mar 26, 2022Import face region metadata — kvalev/photoprism4 reactions · 24 comments
- Sep 7, 2024Mispositioned imported face regions and missing person thumbnails — immich-app/immich3 reactions · 11 comments
- Aug 6, 2025feat(icons): update pigallery2 — homarr-labs/dashboard-icons0 reactions
- Jul 30, 2025ARMv7: Sharp V34 won't run on node:22-alpine3.22 — libvips/libvips0 reactions · 2 comments
- Jul 4, 2025Use "edge" as PG2 base image to include more recent fixes/features — kagahd/pigallery2-metadata-editor0 reactions
10 more on GitHub
- May 8, 2025Allow Pigallery2 "edge-debian-bookworm" tag selection — truenas/apps0 reactions · 1 comment
- Apr 2, 2025✨ [REQUEST] new addon pigallery2 — alexbelgium/hassio-addons0 reactions · 2 comments
- Dec 22, 2024PiGallery 2 unable to add external path for media — truenas/apps0 reactions · 2 comments
- Apr 12, 2024Loading a partial config into an array doesn't populate default values — bpatrik/typeconfig0 reactions · 2 comments
- Sep 4, 2023[BUG] 404 Nginx with custom proxy conf — linuxserver/docker-swag0 reactions · 4 comments
- Feb 17, 2023⚡ — PiGallery 2 — homarr-labs/dashboard-icons0 reactions
- Aug 8, 2022pigallery2 — NixOS/nixpkgs0 reactions · 2 comments
- Oct 10, 2021Add PiGallery2 — trueforge-org/truecharts0 reactions · 4 comments
- May 11, 2021Sidecar support — MikeKovarik/exifr0 reactions · 9 comments
- Oct 19, 2020Output changes after modifying Lightroom image with Exiftool — mattiasw/ExifReader0 reactions · 7 comments
On Hacker News · 2
- Feb 14, 2020PiGallery2 – self-hosted photo gallery website2 points
- Feb 9, 2023PiGallery2 – A fast directory-first photo gallery website, with rich UI1 point
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the steps in order. Keep a task list with one item per step.
- Distinctive: line 27
Ask how long the current edge has been running there and whether anything came up.
- Very specific: line 32
Do the prep work on a branch release-X.Y.Z (PR into master), unless the maintainer says to do it on master directly.
- Very specific: line 50
Don't read messages.hu.xlf itself (~470 KB).
- Very specific: line 61
Write the agreed list as [{id, target}] to a JSON file and run node .claude/skills/release/translation-review.mjs apply <file>.
- Distinctive: line 64
Run the export again: it should come out empty, apart from what the maintainer chose to leave for later.
- Very specific: line 90
Look at every new screenshot (Read the PNGs) and compare it with the one in docs/assets with the same name: loading spinners, missing map …
- Distinctive: line 104
Don't watch it in a loop: start the next step and check the run once it should be done (~20-30 min).
- Distinctive: line 118
Write the draft to a file in the scratchpad (give the full path) and let the maintainer edit it.
- Very specific: line 136
Wait until the tag's CI run has published the kit: npm view pigallery2-extension-kit@X.Y.Z version.
- Distinctive: line 146
Leave the changes for review.
- Distinctive: line 156
When the maintainer changes the process during a release, update this file in the same session.
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PiGallery2 release checklist
Run the steps in order. Keep a task list with one item per step. Stop and ask at every step marked (ask). The global rules still apply: never commit unasked (leave each step's changes for review in the IDE), and pushing a tag or publishing a release is outward-facing, so confirm it first.
Versions: master carries X.Y.Z-edge in package.json; a release is X.Y.Z with a git tag of exactly that name.
The extension kit (pigallery2-extension-kit) needs no publish step: the tag's CI run publishes it with the app's version.
The sample extension that uses it is updated in step 8b.
Release candidate (since 3.8.0): do steps 0-5b with the version X.Y.Z-rc.1 instead of X.Y.Z (branch release-X.Y.Z-rc.1)
and merge it without a tag. Its master CI run pushes Docker edge and publishes the kit X.Y.Z-rc.1 with the npm dist-tag edge
(every prerelease version is published once, from master). The maintainer runs it for about a week; fixes land on master as usual
(bump to -rc.2 only if the kit should be republished). Then the release itself is only step 4 with X.Y.Z
(rerun step 2/3 if strings changed since the RC), then steps 6-9.
0. Preconditions (ask)
- On
master, clean, up to date withorigin/master, and the latest CI run on master is green (gh run list --workflow ci.yml --branch master --limit 3). - Soft rule: the maintainer runs the
edgebuild on their own server for a while before a release. Ask how long the current edge has been running there and whether anything came up. If it's only been a short time, say so, but it's their call. - Pick the version: list what changed since the last tag (
git describe --tags --abbrev=0,git log --oneline <last-tag>..master) and proposeX.Y.Z(usuallypackage.jsonwithout-edge; breaking changes → bump major). - Do the prep work on a branch
release-X.Y.Z(PR into master), unless the maintainer says to do it on master directly.
1. Man page
npm run generate-manregeneratesdocs/user-guide/configuration.mdfrom the config classes.- Show the diff summary; it should only reflect config changes since the last release.
2. Translations
npm run merge-new-translation: extracts the strings (ng extract-i18n) and merges them into everysrc/frontend/translate/messages.*.xlf; new strings get a Google machine translation.- Build and run the translation check:
npm run build-backend && npx mocha test/frontend/translation.spec.js.
3. Hungarian review (ask)
The maintainer wants a clean Hungarian translation of everything a gallery user sees; admin/settings strings may stay machine-translated or English.
Don't read messages.hu.xlf itself (~470 KB). Use the script next to this file:
node .claude/skills/release/translation-review.mjs export --out <scratchpad>/hu.jsonwrites a small JSON ([{id, reason, where, source, target}]) of the units that are new or whose English changed since the last tag (--since <ref>to change), plus units whose translation still equals the English. It skips units used only by the admin UI (settings, admin, duplicates, job texts, config);--with-adminincludes them. Units listed intranslation-reviewed.hu.json(reviewed earlier, including those that stay English on purpose:FPS,OpenStreetMap, ...) are skipped.- Propose natural Hungarian wording for each, consistent with the terms the file already uses (to check a term, grep
<target>lines for it rather than reading the file). Keep every<x id="..." .../>placeholder; write plain text (&,<,>), the script encodes it. Keep a translation that is right as it is. - Show the proposals as a table (source / old / new, mark the ones you'd keep or leave English) and let the maintainer adjust.
- Write the agreed list as
[{id, target}]to a JSON file and runnode .claude/skills/release/translation-review.mjs apply <file>. It checks the placeholders, writes nothing if any unit is wrong, and adds every applied id totranslation-reviewed.hu.json(commit it with the translations). Include the units that are fine as they are (with their current target), so they count as reviewed too. - Run the export again: it should come out empty, apart from what the maintainer chose to leave for later.
4. Version bump
npm version X.Y.Z --no-git-tag-version(updatespackage.jsonandpackage-lock.json).- Suggested commit message:
Version bump to X.Y.Z.
5. Everything builds and passes
Save the output to the scratchpad and read only the summaries (see AGENTS.md "Build and test"). Run long ones in the background.
npm run build-backendnpm run lintnpm run test-backendwith MySQL (the full suite is recommended before a release; see the local MySQL memory)npm run test-frontendnpm run build-en(production build), thennpm run test-e2e- Report failures with their output; don't release over a red suite unless the maintainer says so.
5b. Docs screenshots (ask)
The docs images (docs/assets/*.png, used by docs/features.md) come from a Playwright spec, so they show the current UI.
- Needs the maintainer's docs photos in
demo/images2/docs/puerto rico(not in git; ask if they're missing) and the production build indistfrom step 5. DOCS_SCREENSHOTS=true npm run test-e2e -- docs-screens(it starts its own server,start-docs-e2e-server; stop any own server on 8080 first or setE2E_PORT). It writestest/playwright/screenshots/*.png(git-ignored).- Look at every new screenshot (Read the PNGs) and compare it with the one in
docs/assetswith the same name: loading spinners, missing map tiles or thumbnails, toasts or dev-only UI mean a rerun, not a copy. - Copy the good ones over the same names in
docs/assets/. Images the spec doesn't make (extension.png,events.png,demo.gif,demo.mp4, icons) stay as they are; mention them if the UI they show changed a lot. - The maintainer checks the image diff in the IDE.
Then the maintainer commits, the release PR is merged, and CI on master must be green
(gh run list --workflow ci.yml --branch master --limit 1).
6. Tag (ask)
- On the merged master commit whose
package.jsonsaysX.Y.Z:git tag X.Y.Zandgit push origin X.Y.Z. - The tag's CI run (
gh run list --workflow ci.yml --branch X.Y.Z) builds the release zip and pushes the Docker images (X.Y.Z,latest,latest-<distro>). - Don't watch it in a loop: start the next step and check the run once it should be done (~20-30 min).
7. Release notes (ask)
- Collect:
git log --oneline <last-tag>..X.Y.Z, merged PRs since the last release (gh pr list --state merged --base master --search "merged:>=<last-release-date>" --limit 200 --json number,title,author,body), issues closed by them, and first-time contributors. - Look specifically for:
- a
DataStructureVersionbump (git diff <last-tag>..X.Y.Z -- src/common/DataStructureVersion.ts) → the DB is rebuilt on first start (users kept), - config changes that need user action (diff of
docs/user-guide/configuration.md), - extension API breaking changes (PR descriptions list them;
extension/andsrc/backend/model/extension/IExtension.tsdiffs).
- a
- Draft in the style of earlier releases (
gh release view <last-tag>): Breaking changes, Main new features (with issue/PR links), Further changes, New Contributors, and**Full Changelog**: https://github.com/bpatrik/pigallery2/compare/<last-tag>...X.Y.Z. - Write the draft to a file in the scratchpad (give the full path) and let the maintainer edit it. These notes are written by the maintainer about their own project; don't add an AI footer unless they want one.
8. GitHub release with the CI zip (ask)
- Download the
pigallery2-releaseartifact of the tag's CI run as the same zip the web UI gives (earlier releases attach it aspigallery2-release.zip):gh api repos/bpatrik/pigallery2/actions/runs/<run-id>/artifacts --jq '.artifacts[] | select(.name=="pigallery2-release") | .id'gh api repos/bpatrik/pigallery2/actions/artifacts/<artifact-id>/zip > <scratchpad>/pigallery2-release.zip- Sanity-check it:
unzip -lshowspackage.json,src/backend/index.jsand thedist/languages.
gh release create X.Y.Z --title X.Y.Z --notes-file <draft> --verify-tag <scratchpad>/pigallery2-release.zip(add--draftif the maintainer wants a last look on GitHub), then give the release URL.
8b. Sample extension (ask)
The sample extension (listed in extension/REPOSITORY.md)
must work with the new release. Its local checkout is extensions/pigallery2-sample-extension (its own git repo, branch main).
- Wait until the tag's CI run has published the kit:
npm view pigallery2-extension-kit@X.Y.Z version. - In the sample's
package.json: setversionandpigallery2-extension-kittoX.Y.Z, and the devDependencies that the app also has (typescript,typeconfig,typeorm,@types/node,@types/express) to the app's versions. Bumplodashto its latest. npm install, thennpm run build. Fix compile errors against the new kit and TypeScript (keep itstsconfig.jsonclose to the app's:module: nodenext, CommonJS output).server.js/server.js.map/config.jsare committed there, so rebuild them.- Its CI (
.github/workflows/ci.yml) builds on the Node versions of the app'sci.ymlmatrix; keep that matrix and the action versions in line with the app's. - Try it in the real app (see AGENTS.md "Running the app"), with
--Extensions-folder=<abs path>/extensionsand a throwaway config/DB: the log should showRunning init on extension: pigallery2-sample-extension, its routes andSampleMessenger, and no errors; after logging in asadmin,GET /pgapi/extension/pigallery2-sample-extension/samplereturns the saved rows. - Leave the changes for review; the maintainer commits and pushes them in that repo.
9. Back to edge
- Bump master to the next prerelease, e.g.
npm version X.(Y+1).0-edge --no-git-tag-version(commitVersion bump to X.(Y+1).0-edge, like42af9167). - Wrap up with what was released, links (release, Docker Hub), and anything left open.
Improving this checklist
When the maintainer changes the process during a release, update this file in the same session.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

