Adopt tag-based release versioning and add a GitHub Actions release workflow
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Swift
- Estrellas
- 401
- Forks
- 39
- Merge medio
- 9 min
- PR fusionados (30 d)
- 9
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de latelunchapps/github-contributions-ios
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
feat: organization’s graphAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 43/100
-
feat: allow macOS and visionOSAbiertoenhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 25/100
-
enhancement good first issue
Dificultad 4/5 1-2 días Aptitud para principiantes 43/100
latelunchapps/github-contributions-ios#31 · 1 comentario ·
Todos los issues de latelunchapps/github-contributions-ios
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Enzoo404/gravitybox#21 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
haacked/switchboard#420 ·
Los mantenedores suelen responder en 1 día
-
area: sidebar enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ZigaoWang/zigzag#351 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
manaflow-ai/cmux#46584 ·
Los mantenedores suelen responder en 1 día
-
android:core ios:core
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día