CI/CD Integration
StorePush's REST API makes it straightforward to integrate App Store metadata management into your existing CI/CD pipelines.
Common Workflows
Automated Metadata Push After Build
After your CI builds and uploads a new binary to App Store Connect, trigger StorePush to push metadata:
- Upload your build to App Store Connect (via Xcode Cloud, Fastlane, etc.)
- Call StorePush's API to trigger a
pullChangesto detect the new build - Call the metadata push endpoint to update descriptions and release notes
Release Notes Automation
Automatically update release notes from your changelog:
- Parse your
CHANGELOG.mdor git commit history in CI - Call StorePush's API to update the release notes for the current version
- Push the updated metadata to Apple
Multi-Locale Release Notes
Combine CI/CD with AI translation:
- Write release notes in your primary locale during the release process
- Call StorePush to update the primary locale's release notes
- Trigger the AI translation job to generate localized versions
- Push all metadata to Apple
Example: GitHub Actions
name: Push Metadataon: release: types: [published]
jobs: push-metadata: runs-on: ubuntu-latest steps: - name: Update release notes run: | curl -X POST https://storepush.dev/api/apps/$APP_ID/versions/$VERSION/metadata \ -H "Cookie: $SESSION_COOKIE" \ -H "Content-Type: application/json" \ -d '{"localizations": [{"locale": "en-US", "releaseNotes": "${{ github.event.release.body }}"}]}'
- name: Push to Apple run: | curl -X POST https://storepush.dev/api/apps/$APP_ID/tasks/push-metadata \ -H "Cookie: $SESSION_COOKIE"Best Practices
- Use dedicated API credentials — Create a separate session for CI/CD use
- Check job status — Poll the tasks endpoint to verify push operations complete successfully
- Handle failures — Implement retry logic for transient API errors
- Test in staging — Validate your CI/CD integration before using it with production releases