Repository API: latest_version_href doesn't have mirroring latest_version_prn
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the repository API list/show endpoints, where the response includes latest_version_href, and trace how repository fields are serialized. The work is done when latest_version_prn is exposed alongside latest_version_href so clients can fetch the latest version by PRN.
Written by the indexing model from the issue text.
Description
Version
python3.12-pulp-glue-0.32.3-1.el9.noarch
pulpcore-selinux-2.1.0-1.el9.x86_64
python3.12-pulp-cli-0.32.3-1.el9.noarch
rubygem-smart_proxy_pulp-3.4.0-1.fm3_13.el9.noarch
python3.12-pulpcore-3.85.1-1.el9.noarch
python3.12-pulp-ansible-0.28.0-1.el9.noarch
python3.12-pulp-container-2.26.1-1.el9.noarch
python3.12-pulp-deb-3.7.0-2.el9.noarch
python3.12-pulp-ostree-2.5.0-1.el9.noarch
python3.12-pulp-python-3.19.0-1.el9.noarch
python3.12-pulp-rpm-3.32.0-1.el9.noarch
Describe the bug
{
"pulp_href": "/pulp/api/v3/repositories/ansible/ansible/0199cac6-2012-700c-9177-3647cc17263e/",
"prn": "prn:ansible.ansiblerepository:0199cac6-2012-700c-9177-3647cc17263e",
"pulp_created": "2025-10-09T21:00:06.035204Z",
"pulp_last_updated": "2025-10-09T21:00:06.039899Z",
"versions_href": "/pulp/api/v3/repositories/ansible/ansible/0199cac6-2012-700c-9177-3647cc17263e/versions/",
"pulp_labels": {},
"latest_version_href": "/pulp/api/v3/repositories/ansible/ansible/0199cac6-2012-700c-9177-3647cc17263e/versions/0/",
"name": "Default_Organization-Cabinet-pulp3_Ansible_collection_1",
"description": null,
"retain_repo_versions": null,
"remote": null
}
There is no latest_version_prn here.
To Reproduce
List/show repositories via the API
Expected behavior
latest_version_prn exists to fetch the latest version from the API, just like latest_version_href.
Additional context
Related to Katello's move to PRNs.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Contributor 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 pulp/pulpcore
-
Issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Feature
-
upgrading to 3.117.1 fails without saying which Distribution base_paths are violating constraint OpenIssue
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Issue Triage-Needed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100