upload attachment to release failing due to net::ERR_FAILED 301 (Moved Permanently)

[joyrider3774]

Select Topic Area

Product Feedback

Body

I tried doing a new release today and tried adding an opk file as release file. this had been working fine last week but today i get the following errors when doing the same:

Access to XMLHttpRequest at 'https://objects-origin.githubusercontent.com/github-production-release-asset-2e65be' from origin 'https://github.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.Understand this errorAI
attachment-upload.ts:114 
        
        
       POST https://objects-origin.githubusercontent.com/github-production-release-asset-2e65be net::ERR_FAILED 301 (Moved Permanently)

there is no left over file with same name, i tried deleting it and retyring. I also tried clearing cache but it made no difference.

Anyone else experiancing this ?

[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. ⭐

[joyrider3774]

It must have been something temporary or so as deleting the affected release draft completely and starting over fixed the upload

[mecodeatlas]

Thanks for posting in the GitHub Community, @joyrider3774!

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the Repositories category. I've gone ahead and moved it for you. Good luck!