Jean-Luc MakiolaandClaude Opus 5
97ed6cf6f5
Both siblings' pipelines are near-identical; the real difference between them is which forge is canonical. This is Agendula's spine — it pushes the tag to Codeberg itself and flags pre-1.0 releases as pre-releases — with Calendula's `play` job grafted on unchanged. Taking Agendula's spine means there is no Gitea-canonical phase to migrate out of later, which is the one thing Agendula had to unwind. The Codeberg publish step stays NOT continue-on-error, inherited that way deliberately: in Agendula it reported green through five consecutive releases while never once publishing, which is how a crash-fix release reached F-Droid but not the users who needed it. Comments that recount that history now name Agendula, so an inherited scar isn't misread as ours. The `play` job runs last and isolated, and skips cleanly until PLAY_SERVICE_ACCOUNT_JSON exists — so it stays dormant through the whole pre-1.0 run, which is the correct behaviour anyway. Templates, the contributing guide and verify-release.sh are rewritten for this app's domain rather than renamed: the architectural rule here is that Room types stay in the data layer, and the on-device release check is an alarm that survives a lock screen and a reboot, not a task list that loads. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L94fydiJC37LtxVusNQBDy
11 lines
491 B
Ruby
11 lines
491 B
Ruby
source "https://rubygems.org"
|
|
|
|
# fastlane is used ONLY to upload the release bundle to Google Play
|
|
# (see fastlane/Fastfile). It is not part of the build or the signing path, so
|
|
# it never runs on a PR — only in release.yaml's `play` job.
|
|
#
|
|
# Pinned exactly; Renovate's bundler manager keeps it bumped. No Gemfile.lock is
|
|
# committed on purpose: this resolves an uploader's transitive deps, not the
|
|
# app's, and none of it affects the reproducible release build.
|
|
gem "fastlane", "2.237.0"
|