-
Notifications
You must be signed in to change notification settings - Fork 17
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
The 0.8.0 release tag fails to install #111
Comments
From the Composer docs,
For that reason, we've already moved away from it. However, not coming up at all on 0.8.0 is a problem. Maybe just a lock file update would make it work. I'm not sure what to do about branches since we're now supposed to be on Drupal 10 (and some of that isn't working right now). It's unclear to me what to focus on and what to deliver (e.g. are we going to start a new branch for updates to drupal 9?). |
OH I found the problem. When we transfered over digitalutsc/advanced_search to islandora/advanced_search, Github put in a redirect so that they'd resolve. Now there is a new repo at https://github.com/digitalutsc/advanced_search/ and it does not have the required tags. |
@kstapelfeldt @Natkeeran @kylehuynh205 If you could push the 2.0.0-beta3 tag to your fork of advanced_search, then we'd still be able to run the (legacy but still used/useful) starter site version that uses Drupal 9. |
Hi @rosiel , the tag 2.0.0-beta3 has been pushed. https://github.com/digitalutsc/advanced_search/tags. |
This fixed it for me! Thank you so much @rosiel and @kylehuynh205 |
The error:
2.0.0-beta3 is gone (history was rewritten?)
The url here needs to be changed to https://github.com/islandora/advanced_search and the lock file would need to be updated.
Those changes do fix the error but since it's a tagged release can a pr be done? Would an alternative be making a branch to pull from instead?
The text was updated successfully, but these errors were encountered: