Skip to content

7.0.0

Compare
Choose a tag to compare
@orta orta released this 16 Apr 13:40
· 534 commits to master since this release

Breaking for BitBucket Cloud users only - with changes in their API, see below, then Danger has a new env var
requirement in order to support editing existing comments. You add DANGER_BITBUCKETCLOUD_UUID which is the UUID of
the account which Danger should be using for commenting.

  • Added support to git.info_for_file for added and deleted files. @ethan-riback #1216
  • Allow danger to run with Faraday 1.0.0.
  • Add message aggregation in a non-request-source-specific way:
    When the DANGER_MESSAGE_AGGREGATION environment variable is set (to anything
    that isn't an empty string) and the PR source supports it, this new
    message-aggregation method is used. Otherwise, the old way is used.
    @telyn #1201
  • Allow github repository redirects to be followed. @telyn #1209
  • Fix 404 on Bitbucket Cloud fetching /users/$DANGER_BITBUCKETCLOUD_USERNAME.
    This fix requires that everyone using Bitbucket Cloud now provides the
    DANGER_BITBUCKETCLOUD_UUID environment variable containing the UUID of
    danger's user on bitbucket (with or without the {} braces). See
    this blog post from Atlassian
    for details on the change Atlassian made which broke Danger. @telyn #1217