j4k-oss/tropkod-client
Watch
2
0
Fork
You've already forked tropkod-client
 0
Code Issues Pull requests Releases 3 Packages 1 Activity Actions

chore: align repo config #1

Merged
jercik merged 1 commit from chore/align-repo-config into main 2026-07-17 18:41:23 +00:00
Conversation 0 Commits 1 Files changed 14 +3426 -25
jercik commented 2026-07-17 18:02:33 +00:00
Owner
Copy link

Aligns j4k-oss/tropkod-client to the fleet public-forge-npm-publish standard via j4k-align --fix.

What changed

  • Managed workflows (.forgejo/workflows/): checks.yml, commit-msg.yml, dedupe-check.yml, pr-review.yml, and release.yml. The release workflow is push-to-main triggered, mints an OIDC write:package token at NPM_PUBLISH_OSS_AUDIENCE for the @j4k-oss registry, and (because the package consumes private @j4k devDeps) mints a second npm-reader token at NPM_READ_AUDIENCE for the @j4k install line, then runs semantic-release.
  • Release tooling: added semantic-release and @j4k/semantic-release-forgejo to devDependencies; rendered release.config.mjs.
  • Config: tsconfig.app.json (declaration output for a published package), tsconfig.test.json, .oxfmtrc.json, .vscode/ editor settings, and knip.json (adds .forgejo/workflows/*.{yml,yaml} to the github-actions plugin so workflow-only deps are seen).
  • package.json: repository.url normalized (dropped the git+ prefix); engines.node bumped to >=24.15.0 to meet the fleet floor.

Forge-side (applied out of band by j4k-align --fix): repo settings (squash-only, delete-branch-on-merge, wiki/projects off), description sync, and the oss-publishers team-repo grant. Branch protection on main (enable_push: false, Owners-only merge whitelist) was created manually — Forgejo cannot atomically create the first exact rule on an unprotected branch, so j4k-align hands that off.

Full local gate green: typecheck, lint, knip, format:check, tests, build.

Aligns `j4k-oss/tropkod-client` to the fleet public-forge-npm-publish standard via `j4k-align --fix`. ## What changed - **Managed workflows** (`.forgejo/workflows/`): `checks.yml`, `commit-msg.yml`, `dedupe-check.yml`, `pr-review.yml`, and `release.yml`. The release workflow is push-to-`main` triggered, mints an OIDC `write:package` token at `NPM_PUBLISH_OSS_AUDIENCE` for the `@j4k-oss` registry, and (because the package consumes private `@j4k` devDeps) mints a second `npm-reader` token at `NPM_READ_AUDIENCE` for the `@j4k` install line, then runs `semantic-release`. - **Release tooling**: added `semantic-release` and `@j4k/semantic-release-forgejo` to devDependencies; rendered `release.config.mjs`. - **Config**: `tsconfig.app.json` (declaration output for a published package), `tsconfig.test.json`, `.oxfmtrc.json`, `.vscode/` editor settings, and `knip.json` (adds `.forgejo/workflows/*.{yml,yaml}` to the github-actions plugin so workflow-only deps are seen). - **package.json**: `repository.url` normalized (dropped the `git+` prefix); `engines.node` bumped to `>=24.15.0` to meet the fleet floor. Forge-side (applied out of band by `j4k-align --fix`): repo settings (squash-only, delete-branch-on-merge, wiki/projects off), description sync, and the `oss-publishers` team-repo grant. Branch protection on `main` (`enable_push: false`, Owners-only merge whitelist) was created manually — Forgejo cannot atomically create the first exact rule on an unprotected branch, so `j4k-align` hands that off. Full local gate green: typecheck, lint, knip, format:check, tests, build.
chore: align repo config
All checks were successful
commit-msg / commitlint (pull_request) Successful in 17s
Details
Checks / quality-checks (pull_request) Successful in 34s
Details
Dedupe check / dedupe-check (pull_request) Successful in 36s
Details
088866b026
jercik merged commit 6b87904e30 into main 2026-07-17 18:41:23 +00:00
jercik deleted branch chore/align-repo-config 2026-07-17 18:41:23 +00:00
jercik referenced this pull request from a commit 2026-07-17 18:41:25 +00:00
chore: align repo config (#1)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
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
j4k-oss/tropkod-client!1
No description provided.