Danger Versions Save

• Silence the ObjectifiedHash warnings when iterating over GitLab notes. - @dstull
• Replace URI.escape which is obsolete in Ruby 3. - @mataku
• Fix run with Azure Pipelines as CI Source and Azure Repos Git as Request Source - @damien-danglard
• Delegate explicitly keyword arguments for Ruby 3. - @mataku

• Add danger.import_dangerfile(url:) to import Dangerfile from custom URL - @dstranz
• Fixes issue with not being able to update comments, and instead always posting new comments regardless of settings for Bitbucket Cloud @tskulbru
• Fix incorrect command in error message @revolter

• Add support for Concourse-CI @matthewellis
• Add support for pull_request_target in GitHub actions. - @chesire

• correct the usage of double splat to fix Ruby 2.7 warning
• Adds support for Code Insights for Bitbucket Server. To use Code Insights, please ensure DANGER_BITBUCKETSERVER_CODE_INSIGHTS_REPORT_KEY, DANGER_BITBUCKETSERVER_CODE_INSIGHTS_REPORT_TITLE and DANGER_BITBUCKETSERVER_CODE_INSIGHTS_REPORT_DESCRIPTION optional environment variables are set. @qbeorama

• Add ability to set dismiss_out_of_range_messages for gitlab. - @fahmisdk6
• Preserve single and double quotes @caalberts
• Add support for multiple patterns {a,b} in FileList#include? - @l15 #1258

• Handle ssh URLs with port in Bitrise
• Fixes warnings when using GitLab with Ruby 2.7 @chwo #1250

• Fix request source detection for GitLab. @rymai #1234

Breaking - Drop support for Ruby 2.3, support Ruby 2.4+ [@Kaspik] #1225

• Fix github inline-comments always being struck-through. This was caused by a regression in PR #1182, fixed in PR #1208 for 6.3.2 but didn't make it to 7.0.0 [@Kaspik] #1225

• Fixed import Dangerfile in directory from GitLab
• Fixes warnings when using GitHub with Ruby 2.7
• Improves messaging specific to GitLab
• Updates Git dependency to 1.7 with Ruby 2.7 support without warnings

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