6.2.0

What's Changed

• Use custom bot token in stale workflow by @ofalvai in #171
• Configure Renovate by @renovate in #173
• Apply YAML lint by @ofalvai in #175
• Update filedownloader package by @lpusok in #178
• Remove run_if condition to allow for use in non-CI environments by @hisaac in #179

New Contributors

• @renovate made their first contribution in #173
• @hisaac made their first contribution in #179

Full Changelog: 6.1.2...6.1.3

6.1.2

[#170] Mark Git LFS as a step dependency to avoid a missing dependency in the future

6.1.1

Fixed a bug when a failure during fetch was not handled properly and mistakenly presented the step's run as success

6.1.0

Will correctly export commit author, hash and other outputs for PR builds.
Previously this was not always the case, and the commit information was output for a temporary merge commit (author: J. Doe).
From now the commit by the PR author from the source (head) branch will be used.

The outputs are not exported for PR builds if using hosted Bitbucket with the Manual merge input set to no. (In this case the the commit by the PR author is not available).

Outputs exported for PR builds:
GIT_CLONE_COMMIT_AUTHOR_NAME, GIT_CLONE_COMMIT_AUTHOR_EMAIL, GIT_CLONE_COMMIT_HASH, GIT_CLONE_COMMIT_MESSAGE_SUBJECT, GIT_CLONE_COMMIT_MESSAGE_BODY
Outputs not exported for PR builds:
GIT_CLONE_COMMIT_COMMITER_NAME, GIT_CLONE_COMMIT_COMMITER_EMAIL, GIT_CLONE_COMMIT_COUNT

6.0.0

Version 6.0.0 replaces the limit_submodule_update_depth input by the submodule_update_depth input, which can be used to specify the depth of the submodule update command.

The submodule_update_depth is only applied if it is greater than 0 and update_submodules is set to "yes".

Related pull requests

• submodule update depth made configurable (#161)

5.1.2

Fix sparse checkout for git 2.25.1, by calling git "config" "extensions.partialClone" "origin" "--local".

5.1.1

Introduced --jobs flag on submodule update and fetch commands

5.1.0

Introducing sparse_directories input to limit which directories should be cloned by the Step.

Input can be used either of the following way:

 - sparse_directories: client/android
OR
- sparse_directories: |-
               client/android
               client/common

5.0.1

Update fetch_tags input description.

5.0.0

This version Introduces a new input (fetch_tags), which can be used to control whether git fetch calls should fetch all tags or no tags at all.
Set fetch_tags to "yes" if you plan to generate a changelog or want to use the repository's tags in further Steps.
If you want to speed up the step run set fetch_tags to "no", this is the default value.

Tag checkout strategy's fetch changed from git "fetch" "--tags" to git "fetch" "origin" "refs/tags/<TAG>:refs/tags/<TAG>"so that in case of tag checkout the step only fetches the desired tag.

Migration guide

If your workflow relied on git tags, set fetch_tags to "yes".