Skip to content

Commit 1bcc9ac

Browse files
feat: add instructions for getting Cocoapods token
Signed-off-by: Jonathan Norris <[email protected]>
1 parent d6d4564 commit 1bcc9ac

File tree

2 files changed

+30
-1
lines changed

2 files changed

+30
-1
lines changed

.github/workflows/cocoapods.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,4 +35,4 @@ jobs:
3535
# Ensure the version in podspec matches the release
3636
./scripts/update_podspec.sh
3737
# Push the podspec to trunk
38-
pod trunk push --allow-warnings
38+
pod trunk push OpenFeature.podspec --allow-warnings --verbose

OWNERS.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,32 @@
88
- Mattias Frånberg (mfranberg, Spotify)
99
- Alina Andersone (alina-v1, Spotify)
1010
- Brian Hackett (Calibretto, Spotify)
11+
12+
## CocoaPods Release Token Management
13+
14+
The automated CocoaPods releases require a valid trunk token that expires every 128 days (~4 months). When the token expires, a core developer needs to update the `COCOAPODS_TRUNK_TOKEN` repository secret.
15+
16+
### Getting a New Token
17+
18+
1. Install CocoaPods if not already installed:
19+
```bash
20+
gem install cocoapods
21+
```
22+
23+
2. Register with CocoaPods trunk to generate a new token:
24+
```bash
25+
pod trunk register [email protected] 'OpenFeature' --description='OpenFeature Deployment User'
26+
```
27+
28+
3. Check your email and click the verification link (check https://groups.io/g/openfeature-core for the email)
29+
30+
4. Extract the token from your local configuration:
31+
```bash
32+
cat ~/.netrc
33+
```
34+
Look for the `password` field
35+
36+
### Updating the GitHub Secret
37+
38+
1. Go to the repository settings: `Settings``Secrets and variables``Actions`
39+
2. Find the existing `COCOAPODS_TRUNK_TOKEN` secret and update it

0 commit comments

Comments
 (0)