WordPress / WordPress/wordpress.org
Profiles: WordPress releases list is stuck at 7.0
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 163
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The WordPress releases section on profiles.wordpress.org still stops at 7.0, even though WordPress 7.1 shipped on 19 August 2026.
Example: annezazu was 7.1 Release Lead, and the Credits API already lists her as such, but the profile chips still end at 7.0 (“Contributed to 16 releases”).
This is not a Credits API gap. api.wordpress.org/public_html/core/credits/wp-71.php is present and https://api.wordpress.org/core/credits/1.1/?version=7.1 returns 7.1 data.
The UI is probably rendered by the profiles theme.
That theme is not in this GitHub mirror. profiles.wordpress.org/ here only has the three AJAX handler plugins. There is no themes/ directory, so the 7.1 display bug cannot be patched from this repo.
Related but separate: #701 (squad labels in the same section).
Request
Please include the profiles.wordpress.org theme (and any other non-private profiles front-end code) in this public repository, the same way wordpress.org/public_html/wp-content/themes/ already is.
That would:
- Let contributors patch profile UI bugs like this 7.1 cutoff from GitHub
- Open profile front-end work to the wider community
- Avoid a split where handlers are public but the theme that consumes them is not
I understand some profiles/dotorg paths may stay private. The theme that renders public profile pages should be able to live here.
Test plan
Once the theme is mirrored (or otherwise patched):
- Confirm a 7.1 credited profile (e.g. annezazu) shows a 7.1 chip under WordPress releases
- Confirm older versions (7.0, 6.9, …) are unchanged
- Confirm the list still updates from Credits API data, not a hardcoded max version
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by checking the profiles.wordpress.org/ tree and compare it with wordpress.org/public_html/wp-content/themes/, since this mirror has no themes/ directory. Identify whether the public profiles theme can be mirrored without private paths, then verify the requested outcome with a credited 7.1 profile such as annezazu: 7.1 appears while 7.0 and older releases remain unchanged and the list still comes from Credits API data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100