Skip to content

tox: remove google-genai tox environments - #4957

Open
xrmx wants to merge 1 commit into
open-telemetry:mainfrom
xrmx:remove-google-genai-instrumentations-from-tox
Open

tox: remove google-genai tox environments#4957
xrmx wants to merge 1 commit into
open-telemetry:mainfrom
xrmx:remove-google-genai-instrumentations-from-tox

Conversation

@xrmx

@xrmx xrmx commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Description

Since the package has been moved to python-genai we can spare some CI jobs. It ain't much, but it's honest work.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A

Does This PR Require a Core Repo Change?

  • Yes. - Link to PR:
  • No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

Since the package has been moved to python genai we can spare some CI
jobs. It ain't much, but it's honest work.
@xrmx
xrmx requested a review from a team as a code owner August 14, 2026 13:32
@xrmx xrmx added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Aug 14, 2026
@xrmx xrmx moved this to Easy to review / merge / close in Python PR digest Aug 14, 2026
@xrmx xrmx changed the title tox: remove google-genai tox environemnt tox: remove google-genai tox environments Aug 14, 2026
@xrmx

xrmx commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

@lmolkova @aabmass WDYT?

@opentelemetry-pr-dashboard

opentelemetry-pr-dashboard Bot commented Aug 14, 2026

Copy link
Copy Markdown

Pull request dashboard status

Waiting on the author · refreshed 2026-08-24 21:22 UTC

Respond to 3 review items (e.g. link a commit, explain why not, ask a follow-up):

  • Top-level threads: 1, 2, 3
Status above doesn't look right?
  • Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
  • Should this be with reviewers? Comment /dashboard route:reviewers to route it to them.
  • Anything wrong — including the routing? Report it with what you expected; it helps us improve the dashboard.

@aabmass aabmass left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM since this one is fully moved to the new repo and I don't think we will be releasing google-genai from this repo again

@github-project-automation github-project-automation Bot moved this from Easy to review / merge / close to Approved PRs in Python PR digest Aug 14, 2026
@aabmass

aabmass commented Aug 14, 2026

Copy link
Copy Markdown
Member

I wonder if we can just delete this code altogether tbh. I don't remember why we didn't yet. There is a note in the README about security patching. But I imagine we would just do patch releases off the old branch and not main

Versions ``1.0b0`` and later come from that repository; the copy here only
receives security patches. Upgrade with:

@opentelemetry-pr-dashboard

Copy link
Copy Markdown

Hi @xrmx — just a friendly reminder that this pull request is waiting on you. The dashboard status comment has the open items and is kept current.

  • Replying is enough to hand it off — answer, explain why no change is needed, or ask a follow-up. The dashboard routes it onward once nothing on the list is waiting on you.
  • To hand it back for any other reason, including the dashboard getting this wrong, comment /dashboard route:reviewers.

@aabmass

aabmass commented Aug 24, 2026

Copy link
Copy Markdown
Member

I wonder if we can just delete this code altogether tbh. I don't remember why we didn't yet. There is a note in the README about security patching. But I imagine we would just do patch releases off the old branch and not main

@xrmx chatted with folks offline and we agreed to just delete. Do you want me to send a separate PR for this, or just update this one?

@aabmass aabmass left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blocking for now to discuss

@github-project-automation github-project-automation Bot moved this from Approved PRs to Reviewed PRs that need fixes in Python PR digest Aug 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip Changelog PRs that do not require a CHANGELOG.md entry

Projects

Status: Reviewed PRs that need fixes

Development

Successfully merging this pull request may close these issues.

4 participants