Skip to content
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

chore(main): release opentelemetry-instrumentation-mysql2 0.26.0 #32

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

🤖 I have created a release beep boop

0.26.0 (2024-02-27)

⚠ BREAKING CHANGES

  • Move shared sql behavior to helper gems (#529)
  • obfuscation for mysql2, dalli and postgresql as default option for db_statement (#682)
  • Drop support for EoL Ruby 2.7 (#389)
  • Removed deprecated instrumentation options (#265)
  • Remove parent repo libraries (#3)

Features

  • add config[:obfuscation_limit] to pg and mysql2 (#224) (b369020)
  • Add Obfuscation Limit Option to Trilogy (#477) (234738c)
  • add option to configure span name (#222) (99026b1)
  • Drop support for EoL Ruby 2.7 (#389) (233dfd0)
  • instrument mysql2 prepare statement (#862) (5d40562)
  • obfuscation for mysql2, dalli and postgresql as default option for db_statement (#682) (20e1cd0)
  • Removed deprecated instrumentation options (#265) (bf82e8d)

Bug Fixes

  • add missing requires for sql-helpers to mysql, pg, and trilogy instrumentation (#859) (0de90bb)
  • Base config options (#499) (7304e86)
  • broken test file requirements (#1286) (3ec7d8a)
  • Ensure encoding errors handled during SQL obfuscation for Trilogy (#345) (1a5972f)
  • handle encoding errors in mysql obfuscation (#160) (ed4eec3)
  • regex non-match with obfuscation limit (issue #486) (#488) (6a9c330)
  • regex non-match with obfuscation limit (issue #486) (#488) (b31a4cb)
  • Remove inline linter rules (#608) (bc4a937)

Code Refactoring

  • Move shared sql behavior to helper gems (#529) (c89d681)
  • Remove parent repo libraries (#3) (3e85d44)

This PR was generated with Release Please. See documentation.

Copy link
Author

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

@github-actions github-actions bot added the stale label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants