Alexey Safronov 99152dc100 Consume ui-kit 4.0.0 from npm instead of a tarball ...

Point every app and shared at `@onlyoffice/apps-ui-kit@^4.0.0` from the registry and drop the `file:../../onlyoffice-apps-ui-kit.tgz` specifier. Delete the committed `onlyoffice-apps-ui-kit.tgz` and the stale `onlyoffice-ai-chat-0.6.39.tgz`; the apps already pull ai-chat `^1.0.0` from npm.

The Dockerfiles copy `*.tgz` in the same `COPY` as the manifests. The glob is now optional: it still lets a locally packed tarball be wired in as `file:../../<name>.tgz` for development, and it matches nothing in a clean checkout.

The `minimumReleaseAgeExclude` comment in `pnpm-workspace.yaml` now explains the real reason the two packages are listed. They are first-party packages adopted on release day, so they are always younger than the release-age window. They are no longer listed because the tarballs were never on the registry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 19:06:05 +04:00

..

e2e

Consume ui-kit 4.0.0 from npm instead of a tarball

2026-10-08 19:06:05 +04:00

docker-compose.yml

Fix docker for pnpm

2025-06-23 14:47:28 +04:00

Dockerfile

Consume ui-kit 4.0.0 from npm instead of a tarball

2026-10-08 19:06:05 +04:00