mirror of
https://github.com/ether/etherpad-lite.git
synced 2026-07-17 16:47:05 +00:00
a698e34772
The releaseEtherpad workflow renames ep_etherpad-lite -> ep_etherpad and publishes ./src to npm, but that publish is not load-bearing: - `ep_etherpad` has 0 dependents on npm; nothing in this repo depends on it. - Plugins import `ep_etherpad-lite` resolved from the LOCAL core install, and plugin CI clones `ether/etherpad` rather than `npm install`-ing core. - Etherpad is run via git clone / Docker / zip / snap, never `npm install`. It has been failing with E404 (the ep_etherpad package has no OIDC trusted publisher configured on npmjs.com), which is why npm is stuck at 2.5.0 while 3.0/3.1/3.2/3.3 shipped fine without it. Rather than chase a trusted-publisher setup for a publish nobody consumes, park the workflow: gate the job behind an explicit `confirm: true` dispatch input so a stray run fails fast with a clear message instead of a confusing 404, and document the status in the header + the AGENTS.MD Releasing section. This is the package owner's (samtv12345) call: either finish the trusted- publisher config to revive it, or remove the workflow. Parked pending that decision; nothing about the release depends on it. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| backend-tests.yml | ||
| build-and-deploy-docs.yml | ||
| codeql-analysis.yml | ||
| deb-package.yml | ||
| dependency-review.yml | ||
| docker.yml | ||
| downstream-smoke.yml | ||
| frontend-admin-tests.yml | ||
| frontend-tests.yml | ||
| handleRelease.yml | ||
| installer-test.yml | ||
| load-test.yml | ||
| perform-type-check.yml | ||
| rate-limit.yml | ||
| release.yml | ||
| releaseEtherpad.yml | ||
| snap-build.yml | ||
| snap-publish.yml | ||
| stale.yml | ||
| update-plugins.yml | ||
| upgrade-from-latest-release.yml | ||