DRYD-2114 CI/CD > JS Packages > Auto-resolve frontend patch versions#537
Open
spirosdi wants to merge 2 commits into
Open
DRYD-2114 CI/CD > JS Packages > Auto-resolve frontend patch versions#537spirosdi wants to merge 2 commits into
spirosdi wants to merge 2 commits into
Conversation
Contributor
Author
|
converting to draft, as I just realised I haven't changed the public browser configuration. |
mikejritter
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
It drops the patch version of cspace-ui.js, public browser and profile plugins inside the different build.properties files.
Why are we doing this? (with JIRA link)
Doing so allows us to auto resolve the latest patch version during deployment, without the need to build and release a whole new cspace version: https://collectionspace.atlassian.net/browse/DRYD-2114
How should this be tested? Do these changes have associated tests?
You don't really need to rebuild so that the changes have effect. You can just run the
deploy_tenantsant target, which callsdownload_cspace_ui_jsanddownload_tenant_jsfor each tenant. Please run it inside the cspace-ui directory:ant deploy_tenants. Then you may check the welcome screens of the different tenants: http://localhost:8180/cspace/core/welcome, http://localhost:8180/cspace/anthro/welcome etc... And confirm that the "UI version" and "{Plugin} profile version" are set correctly.For public browser, please run the
deploy_cspace_public_browser_jsant target and check in the http://localhost:8180/cspace/core/public/search page that the correct script source is being set.Dependencies for merging? Releasing to production?
I created the branch from
mainso that we are able to release the changes before the next release. But let us first merge it todevelopand test also there.The dts-hosting/data-toolkit#255 is related but not a blocker.
Has the application documentation been updated for these changes?
The https://collectionspace.atlassian.net/wiki/spaces/CPD/pages/3701473281/Release+Checklist should be updated accordingly. A new page describing the Acceptance Criteria of a patch version should also be added.
Did someone actually run this code to verify it works?
@spirosdi ran it locally
Have any new security vulnerabilities been handled?
no new security vulnerabilities.