Release v0.4.4

Final attempt to clear all 5 platforms. Includes the full chain of
post-monorepo build fixes:
- #47: linux.executableName + Windows pnpm shell:true
- #49: extraMetadata.name=etherpad-desktop (deb/snap/Win path fix)
- #51: exclude etherpad/bin/ (Windows symlink cleanup)
- #54: pnpm hoisted node-linker for etherpad bundle (Windows junction fix)

Bundle size grows ~80-135MB vs v0.4.3 due to the hoisted layout
losing the .pnpm-store prune. Size-reclaim follow-up planned.

Snap publish still pending: previous v0.4.x uploads stuck in Snap
Store review at https://dashboard.snapcraft.io/ — needs manual reject.

Auto-tagged manually for the fifth time; release-please's component
match still misfires.

Release v0.4.3

Includes #51 (Windows bin/ exclude) — should now produce a complete
release: macOS + Linux deb + Linux AppImage + Windows NSIS .exe +
Windows portable.exe + snap (if previous reviews are cleared).

Auto-tagged manually for the fourth time in a row — release-please's
post-merge tagging step still fails on the configured-component
mismatch. Follow-up: tweak release-please-config to include scope in
title pattern.

Release v0.4.2

Auto-tagged manually for the third release in a row — release-please's
post-merge tagging step keeps failing (PR component: undefined does
not match configured component: desktop). Needs a follow-up tweak to
.release-please-config.json's pull-request-title-pattern to include
scope so PR titles like 'chore(desktop): release X.Y.Z' identify the
component on merge.

PR #49's extraMetadata fix is included, so this rebuild should
produce the deb/snap/Windows artifacts that v0.4.0 + v0.4.1 missed.

Release v0.4.1

Auto-tagged manually after release-please-action's component-match
recurrence kept PR #48 at autorelease:pending despite the merge of
its chore: release main commit. Same issue as the v0.4.0 path; needs
release-please-config tweak (pull-request-title-pattern with scope)
in a follow-up.

Triggers release.yml (electron-builder) and snap-publish.yml. PR #47
landed the post-monorepo build fixes (linux.executableName +
Windows pnpm shell:true), so this rebuild should produce the
.deb, .exe x2, and snap artifacts that v0.4.0 was missing.

Release v0.4.0

Auto-tagged manually after release-please-action's component-match
failed to create the tag at PR #40 merge time (still labeled
autorelease: pending). This commit (99b8e80) is the chore: release
main merge that release-please bumped manifest + package.json from
0.3.2 to 0.4.0.

Triggers release.yml (electron-builder) and snap-publish.yml.

chore(main): release 0.3.2 (#21)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

chore(main): release 0.3.1 (#16)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

chore(main): release 0.3.0 (#13)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

fix(snap): use basename for the artifact path so publish-edge finds it

Snap publish-edge failed with "'release/etherpad-desktop_0.2.0_amd64.snap'
is not a valid file" because actions/upload-artifact flattens path
patterns into the artifact root. The build job uploads `release/*.snap`,
which means the artifact's root contains the .snap file directly. When
publish-edge downloads the artifact, the file lands at the workspace
root — not under release/.

Output the BASENAME only from the find step, so the path is valid in
both the build context (where the file is at release/<name>.snap) and
the publish context (where it's at <name>.snap after download).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fix(release): scope snap to snap-publish.yml + don't double-publish (#11

)

Two issues surfaced on the v0.2.0 tag's first run:

1. snap-publish.yml's "Build snap" step failed because electron-builder
   detected the git tag and attempted an implicit publish to the Snap
   Store from inside the build job. SNAPCRAFT_STORE_CREDENTIALS is
   scoped to the dedicated publish-edge / publish-stable jobs only, so
   the build's keyring lookup failed and the workflow died before the
   snap was even uploaded as an artifact. Pass --publish never to the
   build step; the dedicated publish jobs use snapcore/action-publish
   with the credentials properly scoped.

2. release-linux's package step tried to build all three Linux targets
   from the electron-builder.yml (AppImage, deb, snap), which is
   redundant with snap-publish.yml AND triggers the same implicit-
   publish behaviour. Pass an explicit "AppImage deb" target list so
   this job only owns AppImage + deb. Snap is exclusively owned by
   snap-publish.yml.

(The release-linux run for v0.2.0 also showed an AppImage cache rename
race during the snap step — moot once snap is removed from this job.
The actual AppImage and deb artefacts uploaded successfully and are on
the v0.2.0 GitHub Release page; this commit just stops the spurious
failure.)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>