Adopt tag-based release versioning and add a GitHub Actions release workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
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 after1.6.2isv1.6.3orv1.7.0. - Rename the default branch from
mastertomainas 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.0andCURRENT_PROJECT_VERSION = 1in the pbxproj. - Add
.github/workflows/release.yml: onv*.*.*only,macos-latest,fetch-depth: 0, inject versions, archive, upload, and open a draft GitHub release. - Rename the default branch from
mastertomain, and updateREADME.md,CONTRIBUTING.md, andCLAUDE.mdthat still saymaster. - Retire
prepare_releaseonce 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.Ztag onmainuploads 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from latelunchapps/github-contributions-ios
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 43/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
enhancement good first issue
Difficulty 4/5 1-2 days Newbie friendliness 43/100
latelunchapps/github-contributions-ios#31 · 1 comment ·
All issues in latelunchapps/github-contributions-ios
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
haacked/switchboard#420 ·
Maintainers usually reply within 1 day
-
area: sidebar enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ZigaoWang/zigzag#351 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manaflow-ai/cmux#46584 ·
Maintainers usually reply within 1 day
-
android:core ios:core
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
An exit-test child that can't find its exit test runs the whole suite (can fork-bomb)Possibly taken @grynspan claimed this today. Openai-assisted bug command-line experience exit-tests
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
swiftlang/swift-testing#2054 · 1 comment ·
Maintainers usually reply within 1 day