Fix Forgejo publishing and document macOS installation #4

Merged

riley merged 4 commits from docs/forgejo-macos-install into main 2026-11-10 23:19:12 +00:00

Conversation 0 Commits 4 Files changed 13 +407 -47

riley commented 2026-11-10 23:01:00 +00:00

Owner

Copy link

Summary

Bring the pending Forgejo release fixes and installation documentation onto main.

• Use daemon-local Docker image export plus stopped-container copy for Windows release artifacts, avoiding the expired BuildKit client export session.
• Create Forgejo tags with the API's target field and verify the SHA before creating a release.
• Point the README, Unix installer, and release-note generator at Forgejo.
• Add Apple Silicon/Intel macOS guidance, Rosetta-aware native architecture selection, a checksum-verified no-sudo install example, zsh PATH troubleshooting, and unsigned/notarized-binary caveats.
• Keep the Windows PowerShell installer explicitly identified as GitHub-backed.
• Add focused regression tests and wire them into release verification.

Commits

• 91208cf13: Windows artifact export recovery.
• fb1741c39: correct Forgejo tag API field and mismatch guard.
• 11f050606: Forgejo installation and macOS documentation/tests.

Verification

• Static/local: shell syntax, ShellCheck on touched test/generator/publisher scripts, workflow routing, and Git diff checks passed.
• Mocked local: prerelease/platform/checksum tests; six archive/target combinations and missing-binary preservation; documented ARM64, Intel, and Rosetta installs; corrupt-download rejection; Windows export cleanup/error propagation; tag-target and mismatch-guard tests passed.
• Evidence retained under artifacts/forgejo-install-docs/ and artifacts/release-verification/ in the authoring workspace (not committed).
• Focused CI-like, earlier build commit: run 132 built all four platforms and passed verification, but its publication job failed. It is not an all-green workflow result.
• Real platform upload, earlier release: v4.7.6-dev.75 was recovered separately as release 238 using unchanged artifacts from run 132. This does not establish CI success for the new docs commit.
• Not-run: a new full release run or live end-to-end installation of this new installer revision.

Merge/deployment note

The README's automatic installation URLs target main; the new installer behavior becomes available at those URLs after merge. This PR does not alter or republish the existing release assets. No Forgejo server changes are included.

## Summary Bring the pending Forgejo release fixes and installation documentation onto main. - Use daemon-local Docker image export plus stopped-container copy for Windows release artifacts, avoiding the expired BuildKit client export session. - Create Forgejo tags with the API's `target` field and verify the SHA before creating a release. - Point the README, Unix installer, and release-note generator at Forgejo. - Add Apple Silicon/Intel macOS guidance, Rosetta-aware native architecture selection, a checksum-verified no-sudo install example, zsh PATH troubleshooting, and unsigned/notarized-binary caveats. - Keep the Windows PowerShell installer explicitly identified as GitHub-backed. - Add focused regression tests and wire them into release verification. ## Commits - `91208cf13`: Windows artifact export recovery. - `fb1741c39`: correct Forgejo tag API field and mismatch guard. - `11f050606`: Forgejo installation and macOS documentation/tests. ## Verification - **Static/local:** shell syntax, ShellCheck on touched test/generator/publisher scripts, workflow routing, and Git diff checks passed. - **Mocked local:** prerelease/platform/checksum tests; six archive/target combinations and missing-binary preservation; documented ARM64, Intel, and Rosetta installs; corrupt-download rejection; Windows export cleanup/error propagation; tag-target and mismatch-guard tests passed. - Evidence retained under `artifacts/forgejo-install-docs/` and `artifacts/release-verification/` in the authoring workspace (not committed). - **Focused CI-like, earlier build commit:** run 132 built all four platforms and passed verification, but its publication job failed. It is not an all-green workflow result. - **Real platform upload, earlier release:** v4.7.6-dev.75 was recovered separately as release 238 using unchanged artifacts from run 132. This does not establish CI success for the new docs commit. - **Not-run:** a new full release run or live end-to-end installation of this new installer revision. ## Merge/deployment note The README's automatic installation URLs target `main`; the new installer behavior becomes available at those URLs after merge. This PR does not alter or republish the existing release assets. No Forgejo server changes are included.

riley added 3 commits 2026-11-10 23:01:00 +00:00

fix: export Windows release artifacts through Docker daemon ... 91208cf13b

CodeTether-Provenance-ID: ctprov_7fd6a191cae7464e86057815da3a7b82
CodeTether-Origin: local_cli
CodeTether-Agent-Name: build
CodeTether-Agent-Identity: ctagent_6cd9c634bbb048df999b0b2042703dc8
CodeTether-Session-ID: 7a2b7ee6-5290-4b9a-8bd1-9430b809dee7

fix: pin Forgejo release tags with the correct API field ... fb1741c390

CodeTether-Provenance-ID: ctprov_7fd6a191cae7464e86057815da3a7b82
CodeTether-Origin: local_cli
CodeTether-Agent-Name: build
CodeTether-Agent-Identity: ctagent_6cd9c634bbb048df999b0b2042703dc8
CodeTether-Session-ID: 7a2b7ee6-5290-4b9a-8bd1-9430b809dee7

docs: document Forgejo and native macOS installation ... 11f0506068

CodeTether-Provenance-ID: ctprov_7fd6a191cae7464e86057815da3a7b82
CodeTether-Origin: local_cli
CodeTether-Agent-Name: build
CodeTether-Agent-Identity: ctagent_6cd9c634bbb048df999b0b2042703dc8
CodeTether-Session-ID: 7a2b7ee6-5290-4b9a-8bd1-9430b809dee7

riley added 1 commit 2026-11-10 23:03:40 +00:00

Merge branch 'main' into docs/forgejo-macos-install 86747177c7

riley merged commit ad39489636 into main 2026-11-10 23:19:12 +00:00

riley referenced this pull request from a commit 2026-11-10 23:19:12 +00:00

Merge pull request 'Fix Forgejo publishing and document macOS installation' (#4) from docs/forgejo-macos-install into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something isn't working

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

invalid

This doesn't seem right

  

question

Further information is requested

  

wontfix

This will not be worked on

No labels

bug

documentation

duplicate

enhancement

good first issue

help wanted

invalid

question

wontfix

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

riley/codetether-agent!4

No description provided.