Publish plugin to Forgejo npm registry on version tags #2

Merged

troed merged 8 commits from forgejo-publish into main

2026-08-07 19:10:38 +02:00

troed commented

2026-08-07 19:09:01 +02:00

Owner

Summary

Add files field to package.json so the gitignored dist/ client bundle ships in the npm tarball (without it, the published plugin is broken)
Add a Forgejo Actions workflow (.forgejo/workflows/publish.yml) that runs on every v* tag: npm ci → npm test → npm run build → verify package.json version matches the tag → publish to the Forgejo npm registry (owner troed)
Rewrite README: install from the Forgejo registry (with server-side .npmrc prerequisite), admin-panel/local-path alternatives, and a "Publishing a new release" section (tag flow + OWNER_TOKEN setup)

Test Plan

npx jest (15 suites / 93 tests passing)
npm run build
npm pack --dry-run ships dist/, src/, main.js, README.md, package.json
git tag v0.0.1 && git push --tags triggers the publish workflow (manual)

## Summary - Add `files` field to package.json so the gitignored `dist/` client bundle ships in the npm tarball (without it, the published plugin is broken) - Add a Forgejo Actions workflow (`.forgejo/workflows/publish.yml`) that runs on every `v*` tag: `npm ci` → `npm test` → `npm run build` → verify package.json version matches the tag → publish to the Forgejo npm registry (owner `troed`) - Rewrite README: install from the Forgejo registry (with server-side `.npmrc` prerequisite), admin-panel/local-path alternatives, and a "Publishing a new release" section (tag flow + OWNER_TOKEN setup) ## Test Plan - [ ] `npx jest` (15 suites / 93 tests passing) - [ ] `npm run build` - [ ] `npm pack --dry-run` ships dist/, src/, main.js, README.md, package.json - [ ] `git tag v0.0.1 && git push --tags` triggers the publish workflow (manual)

troed added 8 commits

2026-08-07 19:09:01 +02:00