Skip to content

Latest commit

 

History

History
165 lines (88 loc) · 4.46 KB

CHANGELOG.md

File metadata and controls

165 lines (88 loc) · 4.46 KB

Changelog

The format of this document is inspired by Keep a Changelog and the project follows Semantic Versioning.

Unreleased

Breaking Changes

None.

New Features

None.

Bug Fixes

None.

Internal Changes

None.

3.4.1

Bug Fixes

  • Fix for the unbound variable error seen on run_swiftlint [#92]

3.4.0

Internal Changes

  • Restrict the possible run_swiftlint command arguments to "--strict" and "--lenient" [#90]
  • Update swiftlint_version RegExp to check for top-level node [#89]

3.3.0

New Features

  • Make publish_private_pod support --allow-warnings. [#86]

Internal Changes

  • Fixed Ruby, RuboCop and RSpec versions on CI [#88]

3.2.2

Bug Fixes

  • Fix crash in recent update of the publish_pod implementation — 2nd attempt [#85]

3.2.1

Bug Fixes

  • Fix crash in recent update of the publish_pod implementation. [#84]

3.2.0

New Features

  • Make validate_podspec support --allow-warnings, --sources=…, --private, --include-podspecs=… and --external-podspecs=… flags that it will forward to the pod lib lint call. --include-podspecs=*.podspec is also now added by default if not provided explicitly. [#82]
  • Make publish_pod support --allow-warnings and --synchronous flags that it will forward to the pod trunk push call. This is especially useful for repos containing multiple, co-dependant podspecs to publish at the same time, to avoid issues with CDN propagation delays. [#82]

3.1.0

New Features

  • Added run_swiftlint command. It will use the project's SwiftLint version defined in .swiftlint.yml property swiftlint_version to run the right SwiftLint version via Docker, reporting the warnings/errors as Buildkite annotations.

3.0.1

Internal Changes

  • Fix an issue where validate_podspec and publish_pod fail on Xcode 15.0.1 if the pod has a dependency which targets iOS version older than 13. [#78]

3.0.0

Breaking Changes

  • nvm_install utility is removed. See MIGRATION.md for details. [#73]

Bug Fixes

  • Fix issue in annotate_test_failures where the error details' XML node could sometimes be nil. [#76]
  • Make install_swiftpm_dependencies use -onlyUsePackageVersionsFromResolvedFile flag, to prevent Package.resolved from being modified on CI. [#75]

Internal Changes

  • Refine message in annotate_test_failures when configuration for optional Slack reporting is missing. [#74]

2.18.2

Bug Fixes

  • Ensure that install_gems doesn't restore a macOS cache on Linux build machines. [#69]
  • Ensure that install_gems uses the correct ruby version in its CACHE_KEY in all cases. [#70]

2.18.1

Bug Fixes

  • Fix an issue with annotate_test_failures on CI steps that are using the parallelism attribute. [#67]

2.18.0

Bug Fixes

  • annotate_test_failures no longer prints an empty <code> box when reporting a failure with no extra details. [#63]
  • annotate_test_failures is now able to remove annotations on successful step retry even if the step label contains special characters. [#65]

2.17.0

New Features

  • When install_cocoapods fails because Podfile.lock changed in CI, it now prints a diff of the changes. [#59]
  • Update annotate_test_failures to be able to send Slack Notification when there are failures. [#60]

Bug Fixes

  • Fix the annotate_test_failures to include test cases with error nodes in the failures list. [#58]

2.16.0

New Features

  • Add a new github_api utlity to make API requests to GitHub.com or Github Enterprise instances. [#51]
  • Extend the comment_on_pr utility to update or delete the existing comment. [#51]

Bug Fixes

  • Prevent annotate_test_failures to print a misleading red error message when trying to remove previous annotation. [#50]

Internal Changes

  • Added this changelog file. [#49]
  • Re-implement the comment_on_pr utility to use curl instead of gh. [#51]