-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Investigate issues with v3.0.5 release, prepare v3.0.6 #217
Comments
@joewiz The The release was cut from a hotfix branch that has its own Regards the release notes in the |
The tests do not pass. There is one failing cypress test. |
Why was there a release from a hot fix branch in the first place? |
related issue eXist-db/exist#4622 |
The tests were failing due to an unrelated reason to these changes. The reason that they failed is that there was a bad Docker image for the |
That is the only way you can create a hotfix release after the main branch has moved on from the previous release tag!
Yes. The hotfix release does not include the update to |
How was that? The images are automatically updated from develop. How was the image bad? Could you just have triggered the deploy step on ci, or did you need to do something else ? |
@duncdrum I don't know how it got into the bad state |
@adamretter will we know if it gets into a bad state again? |
@joewiz after the most recent merges, I think we are ready for 3.0.6 which should run on both 5.x and 6.x |
v3.0.5 was released but the pom.xml file still reads 3.0.5-SNAPSHOT, and release notes are missing.
We should investigate what happened with this release and then prepare a new version with release notes and an updated pom, etc.
The text was updated successfully, but these errors were encountered: