Unable to publish UPM packages to GitHub Package Repo as of 07/10/2020

https://github.community/t/unable-t...t-name-to-publish-url-as-of-07-10-2020/136643

We use GitHub Package Repo to store our UPM packages. Yesterday we've stated getting the following error:

Code (csharp):

1.  
2. npm ERR! code E400
3. npm ERR! 400 Bad Request - PUT https://npm.pkg.github.com/@electricplaybox/com.electricplaybox.test - name in package.json "com.electricplaybox.test" does not match publish URL "@electricplaybox/com.electricplaybox.test"
4.  
5. npm ERR! A complete log of this run can be found in:
6. npm ERR!     C:\Users\Matt\AppData\Roaming\npm-cache\_logs\2020-10-08T15_47_42_234Z-debug.log
7.  

Indicating that GitHub no-longer supports packages that are not named @scoope/com.who.what. We've been using the trick of adding our @Scope to the end of the repo URL so that we end up with UPM compatible package names without the @Scope.

I've raised a support ticket with Github, asking if this is an intentional (although not documented in the change log) on their part.

Has anyone else been experiencing this issue?

 

Yep, same issue here, just yesterday I started trying the custom packages functionality for the first time, and almost went crazy trying to make them work with GitHub Packages, until I gave up... Please, @MattTaylorEP, let us know if you get a response for the support ticket.

 

ok, so until now we've been working with a hack to make them work together.

UPM does not like packages with the @Scope in the name, so in your manifest.json scoped repo section you need to add your @Scope to the end of the package repo URL, and then publish the packages to github without that in the name.

It seems that a few days ago GitHub has switched up their publish requirements that you have to have the repo URL and package name the same, which for us breaks this workaround.

Will definitely post back as soon as I hear anything back from them or we work out another workaround.

 

Just to update everyone this end, it looks like the change was intentional on GitHub's end, and their suggested workaround causes the same/opposite problem with UPM erroring because the package URL and name no-longer match.

full details of their response: https://github.community/t/unable-t...-url-as-of-07-10-2020/136643/5?u=larsisgaming