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

Open
#49 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, ios, swift
Domain
ci-cd, mobile, release

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Swift
Stars
401
Forks
39
Avg merge
9m
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from latelunchapps/github-contributions-ios

All issues in latelunchapps/github-contributions-ios

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.