Release: promote Solr changes to main for TEST deployment#1608
Merged
Conversation
fix: route conflict checks through possible-conflicts API + fix bucket priority order
Restore the restricted-words path alignment that was reverted, so the Recipe area's conditions call hits the backend route /documents/restricted-words instead of the legacy /documents:restricted_words (which 404s and breaks 'Failed to load Recipe area').
…ignment fix: align postConditions to /documents/restricted-words endpoint
Oluwapizzy
requested review from
davemck513,
mengdong19,
ozamani9gh and
stevenc987
as code owners
Collaborator
|
/gcbrun |
|
Temporary Url for review: https://namex-dev--pr-1608-3frhpub9.web.app |
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.
SUMMARY
This PR promotes the Solr changes from feature-solr-merged into main as part of the planned Solr release to TEST.
Release Context
*Source branch: feature-solr-merged
*Target branch: main
*Target environment: TEST
*Release scope: Multi-repo Solr promotion
*Deployment workflow: Merge to main, then workflow/pipeline deploys to TEST
Validation Plan
After merge and TEST deployment, validation will include:
Confirming the deployment workflow completed
Validating known Solr search scenarios
Documenting any issues or follow-up actions
Post-Merge
Once the PR is approved/merged into main, the workflow/pipeline should deploy the changes to TEST.