Adopt tag-based release versioning and add a GitHub Actions release workflow

オープン
#49 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, ios, swift
領域
ci-cd, mobile, release

調査の方向性

Start by reading the two Info.plist files, Contributions.xcodeproj/project.pbxproj, and the existing Fastlane prepare_release setup. Then add the tag-triggered workflow in .github/workflows/release.yml, checking full-history checkout, version injection, archiving, upload secrets, and draft release creation. Update README.md, CONTRIBUTING.md, and CLAUDE.md for the branch rename; done means the listed release flow works from an annotated vX.Y.Z tag on main.

索引モデルが issue の本文から書いたものです。

説明

Releases today require a version bump in Contributions/Info.plist, ContributionsWidget/Info.plist, and CURRENT_PROJECT_VERSION in Contributions.xcodeproj/project.pbxproj (currently 1.6.2 / 21). There is no MARKETING_VERSION build setting. Fastlane prepare_release exists for release/X.Y.Z branches. There is no CI job that archives or uploads to App Store Connect.

The aim is a simpler flow: an annotated vX.Y.Z tag on the default branch starts a GitHub Actions workflow on GitHub-hosted macos-latest. The workflow sets the marketing version from the tag and the build number from git rev-list --count HEAD, injects both as build settings, archives, and uploads. The project file keeps placeholders only, so there are no bump commits.

Historical tags such as 1.6.2 stay as they are; new releases use the v prefix. Existing 1.* tags must not start the new workflow.

This is a public repository. Use GitHub-hosted macos-latest runners (standard hosted runners are free for public repositories). Do not use a self-hosted runner. Store App Store Connect credentials in GitHub Actions secrets; never commit them. After a successful upload, open a draft GitHub release and leave publishing to the maintainer.

Open a PR; never commit directly to master.

Decisions

  • Release tags are annotated vX.Y.Z. Next tag after 1.6.2 is v1.6.3 or v1.7.0.
  • Rename the default branch from master to main as part of this work.
  • The release workflow is tag-only. Do not add a pull-request build workflow for now.
  • The Actions checkout must use a full history (fetch-depth: 0) so the commit count is correct.

Checklist

  • Switch both Info.plists to $(MARKETING_VERSION) and $(CURRENT_PROJECT_VERSION).
  • Add placeholder MARKETING_VERSION = 0.0.0 and CURRENT_PROJECT_VERSION = 1 in the pbxproj.
  • Add .github/workflows/release.yml: on v*.*.* only, macos-latest, fetch-depth: 0, inject versions, archive, upload, and open a draft GitHub release.
  • Rename the default branch from master to main, and update README.md, CONTRIBUTING.md, and CLAUDE.md that still say master.
  • Retire prepare_release once the workflow is proven.

The first new build number will jump from 21 to the commit count on the default branch (182 as of this writing). That is expected.

Done when

  • Pushing an annotated vX.Y.Z tag on main uploads an App Store build versioned from that tag and the commit count, with no bump commit, no secrets in the repository, and no self-hosted runner.
  • The default branch is main.
主要言語
Swift
スター
401
フォーク
39
平均マージ
9分
マージ済み PR(30日)
9

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

latelunchapps/github-contributions-ios のほかの issue

latelunchapps/github-contributions-ios の issue をすべて見る

似ている issue

Swift の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。