Team access level to Repository stuck on Read; can't change to Maintain

[aneroid]

Select Topic Area

Bug

Body

TL;DR: In an org I'm owner/admin on, I am unable to change the access level a Team has to the added repository.

I have an Organisation with some Teams. In the past, I have added specific repositories to the team access.

When I added new repos now, it's always only with "Read"-level access. I try changing it to "Maintain" and it doesn't work. The UI dropdown shows the new role but refreshing the page shows that it's still just at "Read".

Before:

After, UI shows the new role:

Refresh the page and it still shows the role as "Read".

(In the past, I was able to set/change this as expected.)

I checked DevTools --> Network tab in Chrome, I see a request to stats and collect but nothing else. It's clearly broken.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[aneroid]

Posting a workaround provided by the Support team on a ticket I created:

I did find that if I went to the repository > Settings > Collaborators and teams, then I was able to update the permissions there, so this may work as a workaround for now.