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

chore: upgrade resource-server from 1.3.1 to 1.4.0 #555

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bjagg
Copy link
Member

@bjagg bjagg commented Jan 20, 2022

Checklist
Description of change

Upgrade Resource Server to v1.4.0

Copy link
Contributor

@jgribonvald jgribonvald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested in test env with uP 5.8.2

@@ -18,7 +18,7 @@ notificationPortletVersion=4.7.3
# Required for very old front-end dependencies
resourceServerVersion=1.0.48
# Includes newer front-end dependencies and web components
resourceServer13Version=1.3.1
resourceServer13Version=1.4.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mhhh why the name of the property contains 13 ? Shouldn't be an other name to distinguish ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.3 is the version that introduced WebJars support, so 1.3 became 13. I agree, It should be updated at some point.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested with the 1.4.1 version of the resource server, and it seems good. I didn't deployed on production

Copy link
Contributor

@jonathanmtran jonathanmtran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested against a local copy of our branch. Things appear to continue working as they should.

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

Successfully merging this pull request may close these issues.

None yet

4 participants