ci: enable --strict flag in presubmit twine_check
Maintainers usually reply within 2 days
@ohmayr is already working on this.
Since Oct 1, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- build-system, ci-cd
Research direction
After #18211 populates long_description_content_type in the package setup.py files, open ci/run_single_test.sh and locate the presubmit twine_check command. Enable --strict for the dist/* check, then verify the presubmit check completes successfully with the stricter validation.
Written by the indexing model from the issue text.
Description
Overview
The presubmit twine_check step in ci/run_single_test.sh currently runs twine check dist/* without --strict to avoid false-positive failures caused by missing long_description_content_type metadata in existing setup.py files (see #18211).
Goal
Once long_description_content_type="text/x-rst" is populated across package setup.py files via #18211, re-enable the --strict flag in ci/run_single_test.sh:
twine check --strict dist/*
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1.8k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 140
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from googleapis/google-cloud-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
googleapis/google-cloud-python#19099 ·
Maintainers usually reply within 2 days
-
firestore: field path with a quoted name ending in a backslash is misparsedPossibly taken @sebxt claimed this 28 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/google-cloud-python#18771 ·
Maintainers usually reply within 2 days
-
api: spanner type: feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
googleapis/google-cloud-python#18584 ·
Maintainers usually reply within 2 days
-
auth: `impersonated_credentials` loses `subject` on copy, so `with_scopes()` and `with_quota_project()` turn off domain wide delegationPossibly taken @Om-singhaI claimed this 58 days ago. Openauth priority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
googleapis/google-cloud-python#18428 ·
Maintainers usually reply within 2 days
-
A client called `run_in_transaction` be stuck if Spanner is downPossibly taken @founderinaction claimed this 10 days ago. Openpriority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/google-cloud-python#18375 · 1 comment ·
Maintainers usually reply within 2 days
All issues in googleapis/google-cloud-python
Similar issues
-
[Bug]: HTTP 499 (Client Closed Request) is classified as a non-retryable format_error, so a mid-flight abort fails the turn over instead of retryingPossibly taken @yipinghuang1991 claimed this today. Opencomp/agent P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#156837 ·
Maintainers usually reply within 1 day
-
Bug: Missing continue on ValueError in CpanBackend.check_feed causes UnboundLocalError or duplicate yieldsPossibly taken @muskan-creates352 claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
fedora-infra/anitya#2188 ·
Maintainers usually reply within 1 day
-
docs documentation need-triage SaaS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
integration:hermes
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vectorize-io/hindsight#6601 ·
Maintainers usually reply within 1 day
-
triage:product type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dbt-labs/dbt-adapters#2333 ·
Maintainers usually reply within 1 day