10 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
omar	a5dd271588	ci: drop release workflow, switch install URLs to raw/HEAD ... Gitea has no /releases/latest/download/<file> shortcut (GitHub-only), so the URL we wired up last commit served 404. Switch all user-facing install commands to /raw/HEAD/install.{sh,ps1} -- the HEAD ref resolves to the default branch (secure-main) without naming it, gives a stable "always latest" URL, and survives a future branch rename. With install no longer routed through release assets, the release workflow becomes dead weight: secure-main is the curated branch (every merge is manually reviewed), so every commit there is already vetted. A separate tagged-release step duplicates that gate without adding new information. Drop .gitea/workflows/release.yml; tag manually if you ever want an immutable audit checkpoint. The orphan v1.1.7-secure.1 tag + release is left in place as a historical snapshot; harmless and can be deleted from the Gitea UI later if desired.	2026-05-21 03:47:26 +03:00
omar	32663a7b18	ci: replace GitHub workflows with Gitea release workflow ... The three .github/workflows files (release.yml, compat-daily.yml, cache-cleanup-weekly.yml) all target the GitHub API: - release.yml uses `gh release create` - compat-daily.yml does `git push https://x-access-token@github.com/...` to a `badges` branch - cache-cleanup-weekly.yml uses `gh cache delete` On Gitea Actions these silently mis-route to GitHub with a Gitea-issued GITHUB_TOKEN, which github.com rejects ("Invalid username or token") — so every scheduled run fails. Drop them on secure-main (upstream main keeps them for the original GitHub repo, untouched) and add .gitea/workflows/release.yml that: - triggers on tag push v* or manual workflow_dispatch - builds release notes from the changelog window since the prior tag - creates the release via Gitea API, or refreshes assets if it already exists (so re-runs are idempotent) - attaches install.sh + install.ps1 so the README's /releases/latest/download/install.{sh,ps1} URLs resolve Tag a release with: git tag v1.0.0 && git push origin v1.0.0	2026-05-21 03:34:39 +03:00
omar	f6ee715478	fix: strip BOM + reverse cp1251 mojibake; migrate URLs to releases/latest/download ... Commit 56bc5a7 was authored from a PowerShell session whose console code page was cp1251 (Cyrillic), so PowerShell read the UTF-8 byte stream of each touched file as cp1251 and re-saved it as UTF-8 -- adding a leading EF BB BF BOM and double-encoding every multi-byte character (em-dash, arrows, CJK). README headings, Chinese/Japanese link labels, and inline hyphens all turned into vЂ" / в†' / дё-ж–' style mojibake. Restore the eight affected files (READMEs, docs/clawgod-handbook/*, *.html) from main's clean blobs, then re-apply the qomar.pw redirect substitutions on top. Install URLs now point at git.qomar.pw/omar/clawgod/releases/latest/download/install.{sh,ps1} instead of /raw/branch/secure-main/... in both the markdown/HTML docs and the patcher snippet inside install.sh / install.ps1 (the snippet that rewrites `claude update`). Note: this assumes a Gitea release pipeline publishes install.sh + install.ps1 as assets under each tag. Without that, the new URLs 404.	2026-05-21 03:32:41 +03:00
omar	907613f657	Fix: remove non-ASCII characters and fix PowerShell Here-Strings to resolve encoding and parser errors	2026-05-21 03:20:53 +03:00
omar	fd65bf1b17	Update sync schedule to @hourly shorthand	2026-05-21 03:15:35 +03:00
omar	766d0cb479	Restore production sync schedule (6 hours)	2026-05-21 03:12:47 +03:00
omar	4a201858e9	Update sync workflow: add push trigger and 30min schedule	2026-05-21 03:08:28 +03:00
omar	1d4cf88f8b	Trigger Gitea Actions indexing	2026-05-21 03:07:31 +03:00
omar	56bc5a79e7	Security: redirect updates to private Gitea fork omar/clawgod	2026-05-21 03:04:23 +03:00
omar	a6cf45b883	Add Gitea Action for upstream synchronization	2026-05-21 03:02:54 +03:00