Releases: jdee/settings-bundle
Release 1.3.2
Release 1.3.1
Fastlane is only a development dependency of this gem. At runtime, it can be used with any version of Fastlane, so now there is a check for the existence of the Actions#add_modified_files
method, introduced in the last release, before calling it. This prevents crashing with older versions of Fastlane, which will still require a settings
option for commit_version_bump
.
Release 1.3.0
This takes advantage of a change in Fastlane 2.64.0. The built-in commit_version_bump
action no longer requires a settings
option when used with version 1.3.0 of this plugin:
increment_build_number
update_settings_bundle key: "CurrentAppVersion", value: ":version (:build)"
commit_version_bump
Changes accumulated by multiple invocations of update_settings_bundle
will be included in the commit, in case you update multiple files in the Settings.bundle
.
Release 1.2.1
Fixed inference of Info.plist location when macros are used in the project, e.g. $(SRCROOT)
. (#16)
Release 1.2.0
- Fixed a bug that occurred when the Settings.bundle was in a group in Xcode. (#12)
- Made
:xcodeproj
parameter optional in cases where there is only one non-Pods project in the repo, likecommit_version_bump
. - Added
:bundle_name
parameter to support custom bundle names.
Release 1.1.1
Release 1.1.0
This release adds an optional :target parameter to select a specific target in the project:
update_settings_bundle(
xcodeproj: "MyProject.xcodeproj",
key: "CurrentAppVersion",
value: ":version (:build)",
target: "MyAppTarget"
)
By default, the action takes the first non-test, non-extension target in the project.