Bug 2436021 - rust-podlet-0.3.1 is available
Summary: rust-podlet-0.3.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-podlet
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-02 17:40 UTC by Upstream Release Monitoring
Modified: 2026-04-28 01:33 UTC (History)
3 users (show)

Fixed In Version: rust-podlet-0.3.1-1.fc45 rust-podlet-0.3.1-1.fc43 rust-podlet-0.3.1-1.fc42 rust-podlet-0.3.1-1.fc44
Clone Of:
Environment:
Last Closed: 2026-04-18 13:18:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2026-02-02 17:40:02 UTC
Releases retrieved: 0.3.1
Upstream release that is considered latest: 0.3.1
Current version/release in rawhide: 0.3.0-4.fc44
URL: https://crates.io/crates/podlet

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/372862/


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

Comment 1 Martin Beckert 2026-03-06 09:55:28 UTC
@decathorpe I'm one of the maintainers of the Podlet project (https://github.com/containers/podlet). Is there a blocker that prevents the update to v0.3.1?

Comment 2 Fabio Valentini 2026-03-06 10:50:30 UTC
I briefly looked into it, and it looks like there aren't any obvious problems.

It requires updating k8s-openapi 0.22 -> 0.27 and compose_spec 0.2 -> 0.3, but podlet is the only dependent package so those three can just be updated together.

So right now the only blocker I know of is time - busy with F44 / GNOME 50 work, but I hope to be able to build podlet 0.3.1 soon.

Comment 3 Fedora Update System 2026-04-18 13:14:57 UTC
FEDORA-2026-2e027e70d2 (rust-compose_spec-0.3.0-1.fc45, rust-k8s-openapi-0.27.1-1.fc45, and 1 more) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2e027e70d2

Comment 4 Fedora Update System 2026-04-18 13:15:27 UTC
FEDORA-2026-c2c03cae22 (rust-compose_spec-0.3.0-1.fc44, rust-k8s-openapi-0.27.1-1.fc44, and 1 more) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c2c03cae22

Comment 5 Fedora Update System 2026-04-18 13:15:41 UTC
FEDORA-2026-0fef618601 (rust-compose_spec-0.3.0-1.fc43, rust-k8s-openapi-0.27.1-1.fc43, and 1 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-0fef618601

Comment 6 Fedora Update System 2026-04-18 13:16:01 UTC
FEDORA-2026-6249cf6654 (rust-compose_spec-0.3.0-1.fc42, rust-k8s-openapi-0.27.1-1.fc42, and 1 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6249cf6654

Comment 7 Fedora Update System 2026-04-18 13:18:03 UTC
FEDORA-2026-2e027e70d2 (rust-compose_spec-0.3.0-1.fc45, rust-k8s-openapi-0.27.1-1.fc45, and 1 more) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-04-19 00:53:45 UTC
FEDORA-2026-c2c03cae22 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-c2c03cae22`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c2c03cae22

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

Comment 9 Fedora Update System 2026-04-19 01:44:25 UTC
FEDORA-2026-0fef618601 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-0fef618601`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0fef618601

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

Comment 10 Fedora Update System 2026-04-19 02:02:57 UTC
FEDORA-2026-6249cf6654 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-6249cf6654`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6249cf6654

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

Comment 11 Fedora Update System 2026-04-28 00:58:41 UTC
FEDORA-2026-0fef618601 (rust-compose_spec-0.3.0-1.fc43, rust-k8s-openapi-0.27.1-1.fc43, and 1 more) 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-04-28 01:14:14 UTC
FEDORA-2026-6249cf6654 (rust-compose_spec-0.3.0-1.fc42, rust-k8s-openapi-0.27.1-1.fc42, and 1 more) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2026-04-28 01:33:04 UTC
FEDORA-2026-c2c03cae22 (rust-compose_spec-0.3.0-1.fc44, rust-k8s-openapi-0.27.1-1.fc44, and 1 more) has been pushed to the Fedora 44 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.