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
LPS-122765 Fix semantic versioning issue with frontend token definition api #457
Conversation
ci:test:sf |
ci:test:relevant |
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-122765 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#4689 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#3857 |
Hey @john-co, I'm not sure this makes sense... @izaera changed this recently liferay@27c80f1#diff-20a00663edca54e96364a5e6407aee9228677ebb12f983f36b746e5a66087753 because there were changes in the package... @izaera, can you figure out what happened here? |
ci:test:relevant |
Okay, I see now that this is setting to |
Asked @victorg1991 to do it in #458. Closing here so we don't have conflicting PRs in flight. |
Jenkins Build:test-portal-acceptance-pullrequest(master)#8395 |
This updates the package info to the recommended version to fix failing semantic versioning test described in https://issues.liferay.com/browse/LPS-122765