-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpod.addversion.txt
More file actions
28 lines (19 loc) · 1.12 KB
/
pod.addversion.txt
File metadata and controls
28 lines (19 loc) · 1.12 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
NOTE NOTE NOTE: I think I can't increase the Swift version of this pod to 4.0 until all of its component pods are also at 4.0
# 0) Run `jazzy` to generate the docs. Check for warnings. Check the docs to see if they look OK.
# 1) Validate pod by building it locally from Example app, using :path notation.
# 2) validate the pod, without downloading
pod lib lint --sources="https://github.com/crspybits/Specs.git,https://github.com/CocoaPods/Specs.git" --allow-warnings
# 3) push updated revision of pod to its repo
# 4) push a new tag:
RELEASE_TAG="19.3.0"
git add -A
git commit -m "version $RELEASE_TAG"
git tag -a "$RELEASE_TAG" -m "version $RELEASE_TAG"
git push
git push --tags
# 5) validate the pod, with downloading
pod spec lint --sources="https://github.com/crspybits/Specs.git,https://github.com/CocoaPods/Specs.git" --allow-warnings
# 6) to push my podspec to my Specs repo:
# See also: ls ~/.cocoapods/repos/
# These need to be done from the relevant directory, e.g., Client
pod repo push crspybits-specs SyncServer.podspec --sources="https://github.com/crspybits/Specs.git,https://github.com/CocoaPods/Specs.git" --allow-warnings