Bug 2119196 - python-google-cloud-private-ca-1.4.1 is available
Summary: python-google-cloud-private-ca-1.4.1 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: python-google-cloud-private-ca
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Major Hayden 🤠
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2022-08-17 20:49 UTC by Upstream Release Monitoring
Modified: 2022-08-17 22:14 UTC (History)
3 users (show)

Fixed In Version: python-google-cloud-private-ca-1.4.1-1.fc38
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2022-08-17 22:14:20 UTC
Type: ---

Attachments (Terms of Use)

Description Upstream Release Monitoring 2022-08-17 20:49:19 UTC
Releases retrieved: 1.4.1
Upstream release that is considered latest: 1.4.1
Current version/release in rawhide: 1.4.0-1.fc37
URL: https://pypi.org/project/google-cloud-private-ca/0.3.0

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Based on the information from Anitya: https://release-monitoring.org/project/202178/

To change the monitoring settings for the project, please visit:

Comment 1 Fedora Update System 2022-08-17 21:27:19 UTC
FEDORA-2022-7c34743df5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7c34743df5

Comment 2 Fedora Update System 2022-08-17 22:14:20 UTC
FEDORA-2022-7c34743df5 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.