Releases: wordpress-mobile/release-toolkit
Releases · wordpress-mobile/release-toolkit
9.2.0
New Features
- Added optional
build_gradle_path
andversion_properties_path
config items to actions that previously used thePROJECT_ROOT_FOLDER
environment variable [#519]
Internal Changes
- Added deprecation notices to any actions or methods using the
PROJECT_ROOT_FOLDER
environment variable [#519] - Added deprecation notices to any actions or methods using the
PROJECT_NAME
environment variable [#519]
Full Changelog: 9.1.0...9.2.0
9.1.0
New Features
- Adds
AppVersion
andBuildCode
models that can be used by version actions. [#512] - Adds calculator and formatter classes that can be used with the
AppVersion
andBuildCode
models. [#512] - Renamed
setbranchprotection
toupdate_branch_protection
, and allow it to provide additional optional protection
settings to set/update on the target branch (likelock_branch
,required_ci_checks
, etc).
Thesetbranchprotection
action name still exists for backward compatibility for now (with a deprecation notice),
but it will be removed in a future major release. [#513] - Renamed
removebranchprotection
toremove_branch_protection
.
Theremovebranchprotection
action name still exists for now for backward compatibility (with a deprecation notice),
but it will be removed in a future major release. [#513] - Added
copy_branch_protection
action to replicate the branch protection settings of one branch onto another. [#513]
9.0.1
9.0.0
Breaking Changes
See the MIGRATION.md
file for more detailed instructions and options to handle those breaking changes.
- Add the
public_version_xcconfig_file
parameter to theios_get_app_version
action to replace the need for an environment variable. [#445] - Remove the
ios_localize_project
andios_update_metadata
actions. [#447] - Remove the
skip_deliver
parameter fromios_bump_version_hotfix
andios_bump_version_release
actions. [#450] - Remove the
get_prs_list
action, as its was obsolete (and not used by any client project anymore). [#505]
New Features
- Adds
if_exists
parameter toupload_to_s3
action, with possible values:skip
,:fail
, and:replace
. [#495] - The
create_release
action now prints and returns the URL of the created GitHub Release. [#503] - Removes
bigdecimal
dependency. [#504] [#507] - Supports Ruby 3. [#492, #493, #497, and #504]
- Add
find_previous_tag
andget_prs_between_tags
actions. [#505]
Bug Fixes
- Prevent using non-integer
version_code
values for Android hotfixes [#167]
Internal Changes
8.1.0
What's Changed
- Adds the option to auto-retry for downloading metadata from GlotPress by @oguzkocer in #474
- Release 8.1.0 into trunk by @oguzkocer in #486
Full Changelog: 8.0.1...8.1.0
8.0.1
7.1.2
8.0.0
What's Changed
- Remove git push commands after creating a new commit or branch by @oguzkocer in #472
- Release 8.0.0 into trunk by @oguzkocer in #477
Full Changelog: 7.1.1...8.0.0
7.1.1
7.1.0
New Features
- Add
ios_get_build_number
action to get the current build number from anxcconfig
file. [#458]
Internal Changes
- Add "Mobile Secrets" to
configure_update
current branch message to clarify which repo it's referring to. [#455] buildkite_trigger_build
now prints the web URL of the newly scheduled build, to allow you to easily open it via cmd-click. [#460]- Add the branch information to the 'This is not a release branch' error that's thrown from complete code freeze lane. [#461]
- Update
octokit
to5.6.1
This is a major version bump from version4.18
, but is not a breaking change for the Release Toolkit because it doesn't change any public APIs for clients. [#464] - Update
danger
to9.3.0
. This is an internal-only change and is not a breaking change for clients. [#464] - Replace
rspec-buildkite-analytics
withbuildkite-test_collector
(Buildkite renamed the gem) and update it to2.2.0
. This is another internal-only change and is not a breaking change for clients. [#465] - Adds
ignore_pipeline_branch_filters=true
parameter to the API call triggering a Buildkite build [#468] - Replace all instances of
is_string
withtype
[#469] - Use
git_branch_name_using_HEAD
instead ofgit_branch
so that the return value is not modified by environment variables. This has no impact to our current release flow, that's why it's not in "Breaking changes" section. [#463]