Release from git.borodutch.com (Forgejo Actions) #36

Merged

backmeupplz merged 3 commits from forgejo-release into main 2026-10-23 02:21:40 +00:00

Conversation 0 Commits 3 Files changed 5 +65 -19

backmeupplz commented 2026-10-23 01:13:45 +00:00

Owner

Copy link

Moves the Release workflow from .github/workflows/ to .forgejo/workflows/, so a release published on git.borodutch.com ships everything. GitHub stops running it once this is merged.

What changed

• Trigger: release: published on Forgejo, plus workflow_dispatch with the same dry-run / testflight-only / full modes. Gates, store submissions and artifact names are unchanged.
• APK on the release: the new shared .github/scripts/attach.sh attaches absplus-X.Y.Z.apk and absplus.apk to the Forgejo release, replacing files with the same name. It then waits for the tag to reach the GitHub mirror, creates the GitHub release if it's missing (same title, notes and prerelease flag, --verify-tag), and uploads the same files there with --clobber. absplus.app and F-Droid keep downloading from GitHub. It uses GH_MIRROR_TOKEN for GitHub and the job token for Forgejo.
• Android job: adds android-actions/setup-android@v3 (platform-tools), because the Forgejo job image has no Android SDK.
• iOS job (shared Mac, host mode): the App Store Connect key goes to a folder in $RUNNER_TEMP, which is removed at the end, instead of ~/.appstoreconnect. ios/release.sh (which now passes --p8-file-path to altool) and appstore.py read API_PRIVATE_KEYS_DIR and still default to ~/.appstoreconnect/private_keys. I dropped the sudo xcode-select "Newest Xcode" step: it needs sudo and would change the whole machine, so the Mac's selected Xcode is used.
• .github/scripts stays in place. It is byte-identical in absplus, meshtastic-plus and todorant (new: attach.sh, plus the appstore.py key folder).
• The README release section now uses tea release create.

Validation

• forgejo-runner validate passes. The script unit tests pass. attach.sh was run against a mock Forgejo API with a stub gh, covering the replace, create and missing-release paths.
• A temporary push trigger with MODE hard-coded to dry-run ran on the Forgejo runners (run 37), and I removed it in the last commit:
  • version: ok.
  • iOS on macos-26: archive, cloud-signed export and the App Review dry-run all succeeded ("Would use build 1.2.1 (6), now VALID…").
  • Android: built and signed. Google Play's dry run got as far as the bundle upload, where Play answered "Version code 6 has already been used". That is expected when dry-running an already-released version and shows the Play credentials work. The F-Droid dry run printed its diff.
• Not exercised, since that would publish: the attach.sh uploads with the real tokens.

Not ported

Nothing. Every job runs on Forgejo.

First real release

1. Merge this PR.
2. Bump versionName/versionCode, add fastlane/metadata/android/en-US/changelogs/<versionCode>.txt, and merge.
3. tea release create --repo backmeupplz/absplus --tag vX.Y.Z --target main --title "ABS+ X.Y.Z" --note-file fastlane/metadata/android/en-US/changelogs/<versionCode>.txt
4. Watch Actions → Release on git.borodutch.com. Check that both releases (Forgejo and GitHub) have absplus-X.Y.Z.apk and absplus.apk, and that GitHub marks the release Latest.

🤖 Generated with Claude Code

Moves the Release workflow from `.github/workflows/` to `.forgejo/workflows/`, so a release published on git.borodutch.com ships everything. GitHub stops running it once this is merged. ## What changed - **Trigger:** `release: published` on Forgejo, plus `workflow_dispatch` with the same `dry-run` / `testflight-only` / `full` modes. Gates, store submissions and artifact names are unchanged. - **APK on the release:** the new shared `.github/scripts/attach.sh` attaches `absplus-X.Y.Z.apk` and `absplus.apk` to the Forgejo release, replacing files with the same name. It then waits for the tag to reach the GitHub mirror, creates the GitHub release if it's missing (same title, notes and prerelease flag, `--verify-tag`), and uploads the same files there with `--clobber`. absplus.app and F-Droid keep downloading from GitHub. It uses `GH_MIRROR_TOKEN` for GitHub and the job token for Forgejo. - **Android job:** adds `android-actions/setup-android@v3` (platform-tools), because the Forgejo job image has no Android SDK. - **iOS job (shared Mac, host mode):** the App Store Connect key goes to a folder in `$RUNNER_TEMP`, which is removed at the end, instead of `~/.appstoreconnect`. `ios/release.sh` (which now passes `--p8-file-path` to altool) and `appstore.py` read `API_PRIVATE_KEYS_DIR` and still default to `~/.appstoreconnect/private_keys`. I dropped the `sudo xcode-select` "Newest Xcode" step: it needs sudo and would change the whole machine, so the Mac's selected Xcode is used. - `.github/scripts` stays in place. It is byte-identical in absplus, meshtastic-plus and todorant (new: `attach.sh`, plus the `appstore.py` key folder). - The README release section now uses `tea release create`. ## Validation - `forgejo-runner validate` passes. The script unit tests pass. `attach.sh` was run against a mock Forgejo API with a stub `gh`, covering the replace, create and missing-release paths. - A temporary `push` trigger with MODE hard-coded to `dry-run` ran on the Forgejo runners (run 37), and I removed it in the last commit: - version: ok. - iOS on macos-26: archive, cloud-signed export and the App Review dry-run all succeeded ("Would use build 1.2.1 (6), now VALID…"). - Android: built and signed. Google Play's dry run got as far as the bundle upload, where Play answered "Version code 6 has already been used". That is expected when dry-running an already-released version and shows the Play credentials work. The F-Droid dry run printed its diff. - Not exercised, since that would publish: the `attach.sh` uploads with the real tokens. ## Not ported Nothing. Every job runs on Forgejo. ## First real release 1. Merge this PR. 2. Bump `versionName`/`versionCode`, add `fastlane/metadata/android/en-US/changelogs/<versionCode>.txt`, and merge. 3. `tea release create --repo backmeupplz/absplus --tag vX.Y.Z --target main --title "ABS+ X.Y.Z" --note-file fastlane/metadata/android/en-US/changelogs/<versionCode>.txt` 4. Watch Actions → Release on git.borodutch.com. Check that both releases (Forgejo and GitHub) have `absplus-X.Y.Z.apk` and `absplus.apk`, and that GitHub marks the release Latest. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

backmeupplz added 3 commits 2026-10-23 01:13:45 +00:00

Release from git.borodutch.com: move the release workflow to Forgejo Actions ... 03962e64ad

A release published on git.borodutch.com now runs the Release workflow there. It attaches the
APKs to that release and to the same release on the GitHub mirror, which it creates when missing
(releases don't mirror and the download links point at GitHub). The Android job installs the SDK,
which the Forgejo job image lacks, and the iOS job keeps the App Store Connect key in its temp
folder instead of ~/.appstoreconnect on the shared Mac, without sudo xcode-select.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

TEMPORARY: dry-run this branch on Forgejo Actions ... 7074f701df

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Remove the temporary dry-run trigger ... df810afb51

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

backmeupplz merged commit f44a383e15 into main 2026-10-23 02:21:40 +00:00

backmeupplz referenced this pull request from a commit 2026-10-23 02:21:43 +00:00

Release from git.borodutch.com (Forgejo Actions) (#36)

backmeupplz deleted branch forgejo-release 2026-10-23 02:21:43 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

accessibility

Barrier affecting people with disabilities

  

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

accessibility

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

backmeupplz/absplus!36

No description provided.