Andreas Niemann
35dc008759
Forgejo 11.0.15 does NOT support reusable workflows (job-level `uses:` / `workflow_call`): the call is silently dropped and no run is scheduled (verified live — a same-repo and a cross-repo reusable call both produced zero runs, while an equivalent inline job ran green). The working cross-repo reuse primitive here is the COMPOSITE ACTION referenced by FULL URL (a short-form `uses: olsitec/foundation/...@master` resolves against the runner's DEFAULT_ACTIONS_URL = data.forgejo.org, not the local instance, and 404s; the full-URL form `uses: https://forge.olsitec.net/olsitec/foundation/actions/<x>@master` was verified green). - Replace the four reusable-*.yml with composite actions under actions/: node-build, docker-build, lint, semantic-release-version (same logic + inputs). - actions/README.md documents the pattern, the Forgejo-11 limitation, and the 999_testing candidate coverage (C2/C3/C4 self-contained; C1/C5 blocked on the not-yet-published @olsitec package registry). - ecosystem-selftest paths filter: actions/** (was reusable-*.yml). The capabilities that need no external repo (semantic-release bump sequence, eslint/yamllint gates) keep running green via ecosystem-selftest's inline jobs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.4 KiB
Testing the new foundation
In order to verify that the new foundation is working, there are several things we should test.
CI Testing
Test candidate 1: A docker container with no dependency to npm packages
Candidate: /Users/andiolsi/work/seaspots/services/seaspots-homepage
Test candidate 2: A npm package built with npm
Candidate: /Users/andiolsi/work/olsitec-nci/lib/olsicrypto
Test candidate 3: A npm package built with bun
Candidate: /Users/andiolsi/work/olsitec-nci/lib/document-engine
Test candidate 4: A non-artifact versioned repo
Candidate: /Users/andiolsi/work/olsitrack2/api
Test candidate 5: A docker container with dependency to npm packages
Candidate: /Users/andiolsi/work/olsitrack2/services/token-service
Has an (albeit oudated) dependency on olsicrypto (candidate 2).
semantic-release testing
Create some test git repo, push it to master/main. Expected outcome: 1.0.0
Pull rebase, commit a feat commit. Expected outcome 1.1.0
Pull rebase, commit a fix/chore commit. Expected outcome 1.1.1
Pull rebase, commit a commit with an !, such as feat!. Expected outcome 2.0.0
Pull rebase, commit a commit with BRREAKING CHANGE or BRREAKING CHANGES. Expected outcome 3.0.0
linter testing
Push something with a eslint error in it. Expected outcome: Job exit non-zero
Push something with a yamllint error in it. Expected outcome: Job exit non-zero