Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Review group release workflow dist/wheels workflow step

Open
#235 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
github-actions, python

Research direction

Start with the dist/wheels workflow step and the discussion in PR #234. Compare the current matrix-based publishing flow with the proposed shared step, then settle on and apply the preferred workflow approach. Done means the wheel and sdist publishing workflow is reviewed and the chosen behavior is verified.

Written by the indexing model from the issue text.

Description

Review if using a shared sep to publish wheels is worth it compared to the matrix style we currently have.

I believe you can run this action once to upload many build wheel/sdists in the packages-dir. I guess you could theoretically gather all the artifacts together and run once instead of in a matrix.

Maybe this was has some benefits though.

Originally posted by @aabmass in https://github.com/open-telemetry/opentelemetry-python-genai/pull/234#discussion_r3553980947

Dominant language
Python
Stars
46
Forks
93
Avg merge
2d 20h
Merged PRs (30d)
121

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/opentelemetry-python-genai

All issues in open-telemetry/opentelemetry-python-genai

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.