9 Commits

Include renames

Author	SHA1	Message	Date
dc	5980e2caba	chore(ci): regenerate the lockfile and gate deploys on critical vulns ... Review follow-up. Lockfile: the previous commit pruned the surfer subtree by hand and left orphaned nested entries behind (node_modules/cloudron-surfer/node_modules/*, plus children of removed parents such as @cloudron/pankow's filesize and express-session's cookie). Regenerated from the unmodified main lockfile with `npm install --package-lock-only --legacy-peer-deps`, so the lock is npm's own output rather than an edit. No dangling entries remain. Publish workflow: added a blocking `npm audit --audit-level=critical` step between install and build. Critical rather than the suggested default/low: the tree carries 102 advisories at low/moderate/high that have no non-breaking fix (mostly the Gatsby 5 build toolchain), so a low gate would fail every deploy from the first run. The tree is now clear of criticals, having bumped the two that were live, both within their parents' existing ranges: - proxy-addr 2.0.7 -> 2.0.8 (GHSA-jqcg-44mw-7w3h, via express ~2.0.7) - shell-quote 1.8.1 -> 1.12.0 (GHSA-w7jw-789q-3m8p, GHSA-395f-4hp3-45gv, via react-dev-utils ^1.7.3) .pre-commit-config.yaml: gitleaks hook pinned to v8.30.1 for staged-content secret scanning. Developer-side only - `pre-commit install` per clone. Verified: `npm ci --legacy-peer-deps` clean against the regenerated lock, `npm audit --audit-level=critical` exits 0, build 136 pages, typecheck clean, lint unchanged at the 8 pre-existing files.	2026-10-28 12:04:06 +00:00
dc	27a6d98d0c	chore(deploy): drop the stale v6 surfer dependency and the gh-pages workflow ... The publish workflow now deploys with `npx --yes @cloudron/surfer@7.2.0` (pinned) and the v6 `put` command it replaced no longer exists, so `cloudron-surfer@6` in devDependencies was dead weight in every `npm ci`. Removing it also drops 35 packages that only existed for its bundled admin UI (monaco-editor, three, openid-client, ejs, webdav-server, ...). Only those entries are removed from package-lock.json - no re-resolution, so the diff is pure deletion. `.github/workflows/publish.yml` is the pre-Cloudron deploy path: it pushes the build to a `gh-pages` branch with a third-party action and a `DCSITE` secret. The site is published by surfer from `.gitea/workflows/publish.yml`, so this file describes a deploy that cannot run and only misleads a reader looking for how the site goes live. Verified locally: `npm ci --legacy-peer-deps` (lock still in sync), `npm run build` (136 pages), `npm run typecheck` clean, `npm run lint` reports the same 8 pre-existing files as main and no new ones.	2026-10-28 11:50:11 +00:00
4gl	73fccc70a5	feat: first announcement	2026-07-26 15:27:48 +01:00
Unknown	8a10d127c1	feat: feed feature, typescript, remove google, fix errs & warns	2026-07-17 22:22:29 +01:00
Unknown	2fee73cb9a	fix: local surfer	2026-07-13 22:12:36 +01:00
sead	eda6c62f03	fix(deps): update gatsby, remove ignore scripts due to sharp install error	2025-12-13 19:24:26 +01:00
Yury	c94ed82dba	fix: fixed build and resolved conflicting dependencies	2024-06-19 15:23:24 +03:00
Yury	99521fe8c7	feat: used sendDM method in contact form	2024-06-19 11:49:56 +03:00
Mihajlo Medjedovic	fd510b88c4	init	2024-06-05 15:53:46 +02:00