Release 8.2.0 #781
Merged
Release 8.2.0 #781
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- bundle updated gems
- Bumped newrelic_rpm to 6.15.0 and ran `bundle update newrelic_rpm` - Set backport_fast_active_record_connection_lookup to true. As of 6.5, newrelic_rpm defaults this to false, but recommends setting it to true unless that causes problems with other gems' monkey-patching of ActiveRecord.
dawnpm
approved these changes
Sep 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Checklist
Please ensure you have addressed all concerns below before marking a PR "ready for review" or before requesting a re-review:
Functionality Checks
Code is functional.
Automated checks pass, if applicable. If Code Climate checks do not pass, explain reason for failures:
If your changes will be tested manually, you have run
bundle updateand committed your changes to Gemfile.lock.You have merged the latest changes from the target branch (usually
masterormain) into your branch.If your target branch is NOT
masterormain, specify the reason:Merging to
productionfor push to ProdPR title is either of the format SRCH-#### <description> matching the associated Jira ticket (i.e. "SRCH-123 implement feature X"), or Release #.#.# matching the release number
You have squashed your commits into a single commit (exception: your PR includes commits with formatting-only changes, such as required by Rubocop)
Multiple commits together for a release
Your primary commit message is of the format SRCH-#### <description> matching the associated Jira ticket
Process Checks