Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenUPM couldn't publish updates after 5.0.2 #314

Open
ilterbilguven opened this issue Oct 21, 2024 · 6 comments
Open

OpenUPM couldn't publish updates after 5.0.2 #314

ilterbilguven opened this issue Oct 21, 2024 · 6 comments

Comments

@ilterbilguven
Copy link

I can't update Adjust using OpenUPM due to errors while cloning the repository:
https://openupm.com/packages/com.adjust.sdk/?subPage=pipelines

OpenUPM clones the repo and prepares the release after that. But sdk @ cfa3d1a is missing. Thus, it couldn't continue.

This is important for devs using OpenUPM.

@uerceg
Copy link
Contributor

uerceg commented Oct 21, 2024

Hi @ilterbilguven,

Very interesting. Thank you for reporting this. Do you know if there's maybe some OpenUPM .gitignore equivalent where one can specify what should OpenUPM ignore during the attempt to clone the repo?

@ilterbilguven
Copy link
Author

Unfortunately, no.

It has some settings like that:
image

The repo must be cloneable incl. submodules.

@uerceg
Copy link
Contributor

uerceg commented Oct 21, 2024

I think that the reason why it's currently failing is just because we left that submodule reference to point to a private repo. Let me quickly switch it back to the public one to see if that's gonna do the trick for you. Will ping in here in a bit after that's done.

@uerceg
Copy link
Contributor

uerceg commented Oct 21, 2024

@ilterbilguven Whenever you manage to, give it another try and looking forward to hear if anything has changed now that the submodules are aiming at the public repos.

@ilterbilguven
Copy link
Author

OpenUPM works with tags, so you need to push a new update with this commit.

@uerceg
Copy link
Contributor

uerceg commented Oct 21, 2024

👍 Then, it might take a bit to do that, but it will be part of the next release.

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

No branches or pull requests

2 participants