-
Notifications
You must be signed in to change notification settings - Fork 601
[Admin] Release Process
Here are a memo to steps needed to release a new version:
Ensure that Travis-CI is all-green and that all Unit Tests pass for both iOS and OSX.
One can even run Unit Tests locally especially test them against older iOS SDKs (Travis-CI don't support older SDKs and older versions of Xcode so we can't make it run the tests on iOS7 Simulators for example)
Edit the CHANGELOG.md
file to list all the changes.
Bump the s.version
field of the OHHTTPStubs.podspec
file.
Note: You may use pod lib lint
to check that the podspec is still valid at that point.
For each Example project (Examples/ObjC
and Examples/Swift
):
- Go in the example project's directory and run
pod update
to ensure the example include the latest version - Run the example and ensure it still works properly
git tag
the latest commit then push the tag to GitHub.
Run pod trunk push OHHTTPStubs.podspec
.
This will validate the podspec, ensure it still works and compile, then push it to CocoaPods Trunk (which will in turn automatically trigger the generation of the new documentation on CocoaDocs.org, etc…)
In the Release tab of GitHub, add the corresponding release and copy/paste the CHANGELOG.md
entries to the Release description
Run carthage build --no-skip-current
to build the framework using Carthage (WIP, not tested yet)
Use carthage archive OHHTTPStubs
to create the archive and attache it to the GitHub release (WIP, not tested yet)