Bug 2439337 - postgresql16-16.13 is available
Summary: postgresql16-16.13 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql16
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Filip Januš
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-12 15:12 UTC by Upstream Release Monitoring
Modified: 2026-03-31 01:08 UTC (History)
3 users (show)

Fixed In Version: postgresql16-16.13-1.fc45 postgresql16-16.13-1.fc44 postgresql16-16.13-1.fc43 postgresql16-16.13-1.fc42
Clone Of:
Environment:
Last Closed: 2026-03-10 18:03:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2026-02-12 15:12:54 UTC
Releases retrieved: 16.12
Upstream release that is considered latest: 16.12
Current version/release in rawhide: 16.11-2.fc44
URL: https://www.postgresql.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/375691/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/postgresql16

Comment 1 Upstream Release Monitoring 2026-02-26 14:44:12 UTC
Releases retrieved: 16.13
Upstream release that is considered latest: 16.13
Current version/release in rawhide: 16.11-2.fc44
URL: https://www.postgresql.org/

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://docs.fedoraproject.org/en-US/package-maintainers/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/375691/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/postgresql16

Comment 2 Fedora Update System 2026-03-10 17:59:23 UTC
FEDORA-2026-830ce55480 (postgresql16-16.13-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-830ce55480

Comment 3 Fedora Update System 2026-03-10 18:03:47 UTC
FEDORA-2026-830ce55480 (postgresql16-16.13-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2026-03-10 18:04:04 UTC
FEDORA-2026-3becfd4739 (postgresql16-16.13-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-3becfd4739

Comment 5 Fedora Update System 2026-03-10 18:12:02 UTC
FEDORA-2026-4c9c009c9a (postgresql16-16.13-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-4c9c009c9a

Comment 6 Fedora Update System 2026-03-10 18:13:07 UTC
FEDORA-2026-09262f9ffe (postgresql16-16.13-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-09262f9ffe

Comment 7 Fedora Update System 2026-03-11 01:32:52 UTC
FEDORA-2026-09262f9ffe has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-09262f9ffe`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-09262f9ffe

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-03-11 01:50:18 UTC
FEDORA-2026-3becfd4739 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3becfd4739`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3becfd4739

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-03-11 02:12:25 UTC
FEDORA-2026-4c9c009c9a has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4c9c009c9a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4c9c009c9a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-03-19 00:17:25 UTC
FEDORA-2026-09262f9ffe (postgresql16-16.13-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-03-19 00:54:15 UTC
FEDORA-2026-3becfd4739 (postgresql16-16.13-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2026-03-31 01:08:37 UTC
FEDORA-2026-4c9c009c9a (postgresql16-16.13-1.fc42) has been pushed to the Fedora 42 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.