Skip to content

Releasing.md

Latest commit

 

History

History
30 lines (28 loc) · 1.38 KB

Releasing.md

File metadata and controls

30 lines (28 loc) · 1.38 KB

Releasing SwiftLint

For SwiftLint contributors, follow these steps to cut a release:

  1. Update version number in the following files:
    • Source/swiftlint/Supporting Files/Info.plist
    • Source/SwiftLintFramework/Supporting Files/Info.plist
  2. Come up with a witty washer/dryer themed release name. Past names include:
    • Tumble Dry
    • FabricSoftenerRule
    • Top Loading
    • Fresh Out Of The Dryer
  3. Update the first header in CHANGELOG.md to the new version number & release name.
  4. Commit & push to the master branch.
  5. Tag: git tag -a 0.2.0 -m "0.2.0: Tumble Dry"; git push origin 0.2.0
  6. Make sure you have the latest stable Xcode version installed or symlinked under /Applications/Xcode.app and xcode-selected.
  7. Create the pkg installer & framework zip: make release
  8. Create a GitHub release: https://github.com/realm/SwiftLint/releases/new
    • Specify the tag you just pushed from the dropdown.
    • Set the release title to the new version number & release name.
    • Add the changelog section to the release description text box.
    • Upload the pkg installer and Carthage zip you just built to the GitHub release binaries.
    • Click "Publish release"
  9. File a PR towards Homebrew bumping the tag, revision & Xcode version dependency if necessary. See homebrew#45650 as an example.