-
Notifications
You must be signed in to change notification settings - Fork 604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 9.3.0 #2102
Release 9.3.0 #2102
Conversation
Use Rackup >=v2.0.0
CI fix: Rails40 and Rails41
instrumentation config: use :unsatisfied
- safe autocorrected rubocops - new todo file generated
Rubocop updates
Raise line test coverage threshold
To prevent the agent from subscribing to Active Record notifications and otherwise instrumenting Active Record, the configuration parameter `:disable_active_record_instrumentation` should be set to a value of `true` in the `newrelic.yml` config file. This change permits that parameter to function as expected by fixing a typo in which the code expected `:disable_activerecord_instrumentation` without an underscore. Note that prior to this change, putting `:disable_activerecord_instrumentation` in the config file would also not work, because the config parameter is spelled correctly in `default_source.rb`. This change is needed for the parameter to function at all.
Pin redis version
AR notifications will now be disabled if ANY of the 4 config params are present with a non-default `true` value: - `disable_active_record_instrumentation` - `disable_activerecord_instrumentation` - `disable_active_record_notifications` - `disable_activerecord_notifications`
Active Record notifications: permit disabling
The setup-ruby tool does not dynamically use shas to permit grabbing Ruby versions that have been released since the current version of setup-ruby was released and instead requires an allow-list of versions to be updated with a setup-ruby version update before the new Ruby version can be installed via the action.
…ild_list_pr Add changelog entry for community pr 2089
…_record_models Bugfix for code level metrics on active record classes
Prerelease 9.3.0
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
env: | ||
MY_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
||
jobs: | ||
assign_one_project: | ||
runs-on: ubuntu-latest | ||
permissions: write-all |
Check failure
Code scanning / Scorecard
Token-Permissions
run: echo "branch_name=$(ruby -r $PWD/.github/workflows/scripts/generate_release_notes.rb -e GenerateReleaseNotes.new.branch_name)" >> $GITHUB_ENV | ||
|
||
- name: Checkout docs website repository | ||
uses: actions/checkout@v3 |
Check warning
Code scanning / Scorecard
Pinned-Dependencies
@@ -0,0 +1,55 @@ | |||
name: Create Prerelease |
Check failure
Code scanning / Scorecard
Token-Permissions
create_prerelease: | ||
runs-on: ubuntu-22.04 | ||
permissions: | ||
contents: write |
Check failure
Code scanning / Scorecard
Token-Permissions
@@ -0,0 +1,34 @@ | |||
name: Create Release PR |
Check failure
Code scanning / Scorecard
Token-Permissions
if: ${{ (github.event.pull_request.merged == true) && (contains(github.event.pull_request.labels.*.name, 'prerelease')) }} | ||
runs-on: ubuntu-22.04 | ||
permissions: | ||
contents: write |
Check failure
Code scanning / Scorecard
Token-Permissions
@@ -0,0 +1,19 @@ | |||
name: PR Closed |
Check failure
Code scanning / Scorecard
Token-Permissions
issue_closer: | ||
if: github.event.pull_request.merged == true | ||
runs-on: ubuntu-latest | ||
permissions: write-all |
Check failure
Code scanning / Scorecard
Token-Permissions
Update pull request step
…with_psych5 CI: test config file loading with psych 5
discuss.newrelic.com is now forum.newrelic.com
Update community portal links
Add issue write permissions to repolinter
- This project uses `ncc` and a single .js file instead of a `node_modules` directory, so align with that standard - Target Node.js 18 LTS for all 3 first party actions - Add an Eslint config, align `index.js` with it - Update the Issue Closer README with contributing information
SimpleCov Report
|
Automated PR for 9.3.0 release