Skip to content

Conversation

@XxdpavelxX
Copy link
Contributor

@XxdpavelxX XxdpavelxX commented Dec 1, 2025

Ticket: https://consensyssoftware.atlassian.net/browse/INFRA-3180

Fix bug discussed here https://consensys.slack.com/archives/C09B64PEHAQ/p1764576026224679.
Update create-release-pr workflow to use new topology.json) instead of old teams.json file which no longer exists to create commits.csv.


Note

Switches team lookup from teams.json to topology.json in commit-to-team mapping for commits.csv generation.

  • Scripts:
    • Update getTeam in .github/scripts/generate-rc-commits.mjs to fetch topology.json instead of teams.json for author-to-team mapping.
    • Adjust related URL and error message strings accordingly.

Written by Cursor Bugbot for commit 2641000. This will update automatically on new commits. Configure here.

if (response.status !== 200 || !response.data) {
console.error(
`Invalid response when fetching teams.json: ${response.status}`,
`Invalid response when fetching topology.json: ${response.status}`,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: JSON structure mismatch causes all teams to return Unknown

The topology.json file has a different structure than the old teams.json. The new file is an array of team objects containing members, pm, em, tl, and githubLabel fields (as shown in .github/actions/add-team-label/action.yml). However, the code still uses teamsJson[author] which expects a flat object keyed by username. Since topology.json is an array and author is a username string, this lookup will always return undefined, causing all commits to be labeled as 'Unknown'.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants