Skip to content

Releases: CVEProject/cve-services

v2.7.5

20 Apr 20:25
791d31f

Choose a tag to compare

v2.7.5 Pre-release
Pre-release

What's Changed

Full Changelog: v2.7.4...v2.7.5

v2.7.4

13 Apr 21:19
09e58a6

Choose a tag to compare

v2.7.4 Pre-release
Pre-release

What's Changed

Full Changelog: v2.7.3...v2.7.4

v2.7.3

09 Apr 18:55
15238d1

Choose a tag to compare

v2.7.3 Pre-release
Pre-release

What's Changed

  • Update Staging with version 2.7.3 - getAllOrgs DocumentDb bug fix. by @david-rocca in #1726

Full Changelog: v2.7.2...v2.7.3

v2.7.2

07 Apr 20:01
5f94285

Choose a tag to compare

v2.7.2 Pre-release
Pre-release

What's Changed

  • Resolves issue #1717 , Replace old CNA fields with new generic partner fields across organization APIs. by @david-rocca in #1718
  • v2.7.2 - Renaming some fields & Reports_to and Oversees updates by @david-rocca in #1725

Full Changelog: v2.7.1...v2.7.2

v2.7.1

01 Apr 15:24
5fcbad4

Choose a tag to compare

v2.7.1 Pre-release
Pre-release

What's Changed

Full Changelog: v2.6.2...v2.7.1

v2.6.2

24 Mar 19:56

Choose a tag to compare

What's Changed

  • Resolves #1629: Prevents ambiguous timestamps in ADP containers
  • Upgrades to node v24

Full Changelog: v2.6.1...v2.6.2

v2.6.1

11 Feb 18:48
34fe473

Choose a tag to compare

What's Changed

  • Resolves #1626 Formats timeline.time values to yyyy-MM-ddTHH:mm:ss.sssZ (ISO-8601, UTC)
  • Resolves #1623 Prevents invalid timeline.time values by @jdaigneau5 in #1625

Full Changelog: v2.6.0...v2.6.1

v2.6.0

23 Oct 19:04
0079738

Choose a tag to compare

What's Changed

Full Changelog: v2.5.4...v2.6.0

ur-v0.2.0-beta.3

23 Sep 14:54
a4e205e

Choose a tag to compare

ur-v0.2.0-beta.3 Pre-release
Pre-release

What's Changed

Full Changelog: ur-v0.2.0-beta.1...ur-v0.2.0-beta.3

ur-v0.2.0-beta.1

22 Aug 15:20

Choose a tag to compare

ur-v0.2.0-beta.1 Pre-release
Pre-release

Release Notes:

  • This is an incremental release of proposals 1 through 3 discussed at the the AWG.
  • This is NOT the intended to PR to go to production. There are known issues and work still to be done.
  • We originally intended to deploy this to test on Thursday, August 21st. However, due to some pipeline issues and failing tests we decided to take Thursday to ensure we were stable enough. Deploying on Fridays is bad karma, so as of right now we will plan to deploy this PR to the staging (test) branch on Monday, August 25th.

What is this release

  1. Migration from using query parameter api/org/x/y?registry=true to url path parameter format api/registry/org/x/y/z to signal the opt in usage of the new registry options
  2. Iteration of the User and Org Model for user Registry
    • Removed bi-directional relationships, Orgs now own all relationships.
    • Simplified some field values (removing items that were nested for no reason) and field names.
  3. Implementation of JSON Schema Validation for Users and Organizations
    • Includes new Schema files!
    • Implements Mongoose Automatic Validation on writes.
  4. Repository updates, to handle the "Discriminator" Mongoose paradigm
  5. Repositories, now handle "backwards compatibility" instead of the controllers themselves.
    • Reduced Controller complexity. Controllers Now only call the repository to check for known errors to return to the user OR to perform the actual CRUD Action. The controllers are agnostic of if you are dealing in "Legacy or Registry" formats.
    • Allowed more streamline usage with the Mongoose ORM instead of raw Mongo Based Queries
    • Allows for multiple routes to call the same endpoint, with flags set to control repository functions

Known Issues

  • Only Secretariat and CNA org types are implemented. Bulkdownload and ADP are not completed.
  • The active flag on users is not disabling access correctly when set to false
  • In an effort to work incrementally, the "BaseOrg" and "BaseUser" models have been made to replace "registry-org" and "registry-user" models. However, these will eventually be named to keep the "registry" name.
  • Black box tests still need to be migrated
  • Unit tests still need to be migrated.

PRs Closed

  • User registry initial Implementation. by @david-rocca in #1392
  • Resolves issue 1412 Create Registry Tests - createUserTest.js by @afoote-mitre in #1420
  • Resolves issue 1413 Create Registry Tests - updateUserTest.js by @afoote-mitre in #1422
  • Resolves issue #1414, Creating node registry tests replacing the ones in org_as_org_admin.py by @david-rocca in #1421
  • Add integration test for regularUser trying to make Org and User requests with registry=true by @emathew5 in #1424
  • Resolves issue #1410 - registry tests for postOrgTest, and issue #1426 - improper handling of contact_info for registry org by @cberger8 in #1429
  • Resolves issue #1411 - integration tests for creating org users with registry enabled by @cberger8 in #1430
  • Resolves issue 1417, Testing User Get Request for /api/org with the registry=true flag by @emathew5 in #1431
  • Closes: 1415 / Bug 1425 / Bug 1427 - Org.py New tests for Registry by @david-rocca in #1428
  • Resolves issue 1401, Validates the request body for registryOrg POST request by @emathew5 in #1432
  • Resolves issue #1402 - updated swagger docs for registry endpoints by @cberger8 in #1439
  • Fixed line endings for swagger doc by @cberger8 in #1440
  • Resolves Issue #1399 - Update getOrg in registry-org controller to allow for uuid or shortname by @david-rocca in #1438
  • Resolves issue #1408 and #1407 - Fixes Session Closures by @david-rocca in #1437
  • Resolves issue #1409, Make Argon2 calls consistant by @david-rocca in #1436
  • Resolves issue #1406 - fixed error handling when UUID provided for registry org/user creation by @cberger8 in #1443
  • Resolves issue 1400, Add createUserByOrg registryOrg/ endpoint by @emathew5 in #1441
  • Resolves issue #1447, Create Registry User Schema by @emathew5 in #1475

New Contributors

Full Changelog: ur-v0.1.1...ur-v0.2.0-beta.1