2.8.4 release - #1952
Merged
Merged
Conversation
Add optional projection parameters to OrgRepository.getAllOrgs and UserRepository.getAllUsers so callers can limit returned fields. getFilteredCveId now fetches only UUID and short_name for orgs, and UUID, username, and org_UUID for users, instead of entire documents.
…e-id-filter Resolves issue #1843, Use field projections in getFilteredCveId.
Closes #1928: Remove legacy registry=true support
Add Secretariat-only endpoints for assigning and removing an organization’s reports-to relationship with a ROOT organization. - Add documented POST endpoints to add and remove ROOT `oversees` relationships. - Validate that the overseeing organization has ROOT authority and return clear errors when either organization is not found. - Reassign a reporting organization atomically by removing it from a previous ROOT organization before adding the new relationship. - Audit additions, removals, and reassignments for every affected ROOT organization. - Ignore `oversees` in standard organization PUT requests so reports-to relationships can only be managed through the dedicated endpoints. - Update existing CRUD coverage to verify PUT requests cannot create `oversees` or derived `reports_to` relationships. - Add ROOT organization integration coverage for successful assignment, reassignment, removal, invalid non-ROOT parents, missing organizations, and Secretariat-only authorization.
Add Secretariat endpoints for ROOT organization reports-to management
Remove unused middleware helpers
linter issue
Align user format flag semantics
jdalphond-mitre
approved these changes
Aug 5, 2026
jdalphond-mitre
left a comment
jdalphond-mitre
left a comment
Collaborator
There was a problem hiding this comment.
All features/bug fixes look good
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
4 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.
Resolves issues #1843, #1918, #1921, #1928, #1930, and #1933 by merging the 2.8.4 release changes into
dev.Closes Issue #1843, #1918, #1921, #1928, #1930, and #1933
Summary
Merges 2.8.4-release into
dev, including registry-route consolidation, legacy endpoint cleanup, ROOT organization relationship management, CVE-ID query projections, and format-flag consistency fixes.Important Changes
src/controller/registry.controller/src/controller/cve-id.controller/cve-id.controller.jssrc/controller/format.constants.jssrc/controller/org.controller/andsrc/controller/user.controller/registry=truesupport and unused endpoint/middleware code.api-docs/openapi.jsontest/Testing
Steps to manually test updated functionality, if possible
bash -i -c "npm run test:unit-tests".bash -i -c "npm run test:integration".reports_torelationship through the registry API./api/registryOrgand/api/registryUserroutes return 404.Notes
REGISTRY_FORMATflag.