Donate to OSS-Singularity/website

• github.com/sponsors/oss-singularity

---

See the documentation for more details on donation links.

Port repository checks and static publication to Forgejo Actions #1

Merged

ClaudiuSchuster merged 9 commits from oss-oo/forgejo-pipeline-20260923 into main 2026-09-23 01:50:08 +00:00

Conversation 0 Commits 9 Files changed 7 +949

ClaudiuSchuster commented 2026-09-23 00:44:11 +00:00

Owner

• Copy link
• Copy Markdown

Brings the website deployment home to the laboratory: the full Repository-checks suite runs on our own runner, and static publication drives the proven static_publication.transition engine (filesystem journal, HTTP acceptance, retained rollback) with a forge-native trust layer — same-run double builds, forge policy reads, and an append-only oss-static-ledger branch replacing the GitHub deployments ledger.

• Gates: identical checks to .github/workflows/repository-checks.yml (incl. pinned Foundry v1.8.3 settlement exercise), no marketplace actions, pinned job containers.
• Publication: .forgejo/workflows/static-publication.yml with plan/publish dispatch, oss-production concurrency, STATIC_PUBLISH_ENABLED gate; report keeps source_rebuilt / publication_verified / rollback_retained.
• Docs: docs/release-forgejo.md (access table + equivalence mapping + not-yet-ported recover mode); CONTRIBUTING table and checklist extended.

Local evidence: check-repository (incl. check-site + agent-data) passed; test-static-publication (37), test-static-recovery (11), test-forgejo-publication (18, incl. real double-build) passed in both normal and -O modes; site boundary audit with --history passed.

Follow-up in this PR before merge: fill REQUIRED_CONTEXT with the exact forge status context observed from this PR's own CI run.

Brings the website deployment home to the laboratory: the full Repository-checks suite runs on our own runner, and static publication drives the proven static_publication.transition engine (filesystem journal, HTTP acceptance, retained rollback) with a forge-native trust layer — same-run double builds, forge policy reads, and an append-only oss-static-ledger branch replacing the GitHub deployments ledger. - Gates: identical checks to .github/workflows/repository-checks.yml (incl. pinned Foundry v1.8.3 settlement exercise), no marketplace actions, pinned job containers. - Publication: .forgejo/workflows/static-publication.yml with plan/publish dispatch, oss-production concurrency, STATIC_PUBLISH_ENABLED gate; report keeps source_rebuilt / publication_verified / rollback_retained. - Docs: docs/release-forgejo.md (access table + equivalence mapping + not-yet-ported recover mode); CONTRIBUTING table and checklist extended. Local evidence: check-repository (incl. check-site + agent-data) passed; test-static-publication (37), test-static-recovery (11), test-forgejo-publication (18, incl. real double-build) passed in both normal and -O modes; site boundary audit with --history passed. Follow-up in this PR before merge: fill REQUIRED_CONTEXT with the exact forge status context observed from this PR's own CI run.

ClaudiuSchuster added 1 commit 2026-09-23 00:44:11 +00:00

Port repository checks and static publication to Forgejo Actions ... f40007e2c5

Add .forgejo/workflows/ci.yml (gate-equivalent port of repository-checks.yml,
same checks and pinned Foundry, laboratory-style checkout without marketplace
actions) and .forgejo/workflows/static-publication.yml with the forge-native
publication boundary: scripts/forgejo_publication.py reuses the proven
static_publication.transition engine (filesystem, HTTP acceptance, rollback)
and replaces the GitHub provenance chain with same-run double builds, forge
policy reads and an append-only oss-static-ledger branch. Documented in
docs/release-forgejo.md; CI and CONTRIBUTING extended.

ClaudiuSchuster added 1 commit 2026-09-23 00:45:29 +00:00

Pin the forge required-status context observed from the first forge CI run 2298d86af5

ClaudiuSchuster added 1 commit 2026-09-23 00:48:14 +00:00

Gate publication enablement via secrets: this forge exposes no variable write API ab6d786ab3

ClaudiuSchuster added 1 commit 2026-09-23 00:50:15 +00:00

Run repository checks on Python 3.12 with pinned Node 24 tarball ... 959b15d446

The node:24-bookworm image ships Python 3.11 and the archive suite's
zip64 streaming-descriptor test fails there with invalid_archive; the
GitHub baseline (ubuntu-24.04) and station both run 3.12. Match 3.12 in
the container and install Node v24.21.0 as a pinned official tarball.

ClaudiuSchuster added 1 commit 2026-09-23 00:53:18 +00:00

Install the full Node tarball: the pinned solc gate needs npm and npx d97f5b285e

ClaudiuSchuster added 1 commit 2026-09-23 01:03:42 +00:00

Install openssh-client: the publication transport tests require ssh-keygen 6621c81d80

ClaudiuSchuster added 1 commit 2026-09-23 01:16:38 +00:00

CI: rerun after the infrastructure restart interrupted the previous run 662cc81880

ClaudiuSchuster added 1 commit 2026-09-23 01:27:49 +00:00

CI: rerun after a runner container recreate interrupted the suite 12a0ce5323

ClaudiuSchuster added 1 commit 2026-09-23 01:39:36 +00:00

Build with the container's python3 on PATH (/usr/local/bin) 235d8429f4

ClaudiuSchuster merged commit 5f9c808452 into main 2026-09-23 01:50:08 +00:00

ClaudiuSchuster referenced this pull request from a commit 2026-09-23 01:50:09 +00:00

Port repository checks and static publication to Forgejo Actions (#1)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

OSS-Singularity/website!1

No description provided.