Release 9.11.0 #2726
Merged
Release 9.11.0 #2726
Conversation
This file contains hidden or 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
to simplify 3rd party GitHub Actions versions specified across our various workflow files, put the versions in a `versions.yml` file and define a new `gha:update_versions` rake task to automatically reconcile the workflows with the versions specified.
add gha:update_versions Rake task
previously, errors that were noticed and treated as expected because the HTTP status code matched the list configured via `:'error_collector.expected_status_codes'` would not actually end up with their `expected` attribute set to a `true` value. the relevant agent error processing behavior has been updated so that `expected: true` should always be applied to all errors that are treated as expected by the agent. resolves #2708
Grape is unhappy with the new Rack version. Let's lock down Rack in Grape testing contexts until a Grape fix is out.
new Rubies are out, so let's upgrade to the latest setup-ruby sha and start testing with them
it should be fine to use the latest Rack version with Grape v2+
correct method name
the `starts_with?` check for the grape version string needs to strip away any Bundler version locking prefix
For Ruby v3.4/3.5 compatibility, declare `mutex_m` and `ostruct` as dev dependencies
relax the Rack driven content-length check for Grape
CI: Lock down Rack for old Grape v1.x versions
- assume all Rack testing will now involve a Rack at or above v1.4 - stop checking for `Rack::VERSION`, as modern Rack uses `Rack.release`
We have some tests that were designed to work with Rack v1.x as long as Rack was at or above v1.4. We checked to see if the minor version was at or above 4 without checking the major version. These tests haven't worked properly since Rack v2 as a result. Given that we no longer test against Rack v1.x, the tests have been removed.
CI: stop checking for / testing against Rack v1
When naming Stripe metrics, include only the first two (API version and category) portions of the path and not the id. Continue to start the metric name with "Stripe" and end it with the method (ex: "get"). This will prevent metric name exhaustion resulting from regular Stripe usage. Given a 'get' request performed against a path of '/v1/payment_methods/pm_8675309', the metric name will now be 'Stripe/v1/payment_methods/get'. resolves #2654 resolves #2709
Add Grape release notifications
CI: use Ruby v3.3.3 and v3.1.6
List the HTTP status code `expected: true` bugfix in the changelog
set `expected: true` for matching status codes
List the Stripe bugfix (PR 2716) in the changelog
Stripe: do not include path ids in metric names
CI: Grape Envfile tweaks
CI: update GHA nick-fields/retry to v3.0.0
- Enforce Ruby v2.7+ for the latest version of Grape, which has dropped support for Ruby v2.6 in Grape v2.1.0. - Add a version entry for Grape v2.0.0.
API change required when going from v2.0 to v2.1
…cipe CI: Grape v2.1.0 related updates
Co-authored-by: Hannah Ramadan <76922290+hannahramadan@users.noreply.github.com>
Add SQS instrumentation
Prerelease 9.11.0-pre
fallwith
requested review from
fallwith,
hannahramadan,
kaylareopelle and
tannalynn
as code owners
fallwith
approved these changes
Jun 20, 2024
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.
Automated PR for 9.11.0 release