Skip to content
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.

Some PyPI releases do not have corresponding tags #5

Closed
busunkim96 opened this issue Feb 4, 2020 · 2 comments
Closed

Some PyPI releases do not have corresponding tags #5

busunkim96 opened this issue Feb 4, 2020 · 2 comments
Assignees
@tseaver
Labels
api: cloudresourcemanager Issues related to the googleapis/python-resource-manager API. type: cleanup An internal cleanup or hygiene concern.

Comments

@busunkim96
Copy link
Contributor

I did a quick pass through the commit log and it's not completely clear which commit belongs to each tag. Many of the tags were from the days of the 'umbrella' package where all packages were released together.
@busunkim96 busunkim96 added the type: cleanup An internal cleanup or hygiene concern. label Feb 4, 2020
@product-auto-label product-auto-label bot added the api: cloudresourcemanager Issues related to the googleapis/python-resource-manager API. label Feb 4, 2020
@tseaver tseaver self-assigned this Nov 13, 2020
@tseaver
Copy link
Contributor

tseaver commented Nov 13, 2020

I just created tags for the v0.{20,22,23,24,25,26,27,28}.0 releases (v0.21.0 already existed).

I can't find any relevant commit for the PyPI v0.1.0 release: that date would appear to correspond to googleapis/google-cloud-python#2270, which was an umbrella release for google-cloud v0.19.0 (2016-09-19). https://github.com/googleapis/google-cloud-python/tree/4d66524a57d73742b5fe1f4ca571b305031ea5d2/google/cloud/resource_manager had files in it, but the PyPI release is metadata-only (no downloads).

@tseaver tseaver closed this as completed Nov 13, 2020
@busunkim96
Copy link
Contributor Author

Thank you @tseaver!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tseaver tseaver

Labels
api: cloudresourcemanager Issues related to the googleapis/python-resource-manager API. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tseaver @busunkim96