Versions Model

Overview

This table stores the versioning details of various packages or components within the system. It tracks different versions of packages, including their local versions, draft versions, and any associated metadata.

Fields

Field	Type	Description	Required
id	string	A unique identifier for each record in the table. Used to uniquely identify a specific version entry.	❌
type	string	Defines the type of package or entity, specifying its category or purpose.	❌
localVersion	any	Represents the version of the package that is stored or used locally, potentially differing from the main version.	❌
version	string	Indicates the current version of the package or entity. Used to indicate which release this entry represents.	❌
versionData	any	Contains metadata or additional information about the version, such as release notes or configuration details. It can hold large structured or unstructured content.	❌
versions	string	Stores a collection or list of all available versions related to the package or entity.	❌
package_id	string	A reference to the associated package, linking the record to a specific package entity.	❌
draft_version	any	Refers to a draft or unpublished version of the package that is still under development or review. Used when a version is being prepared but not finalized.	❌
created_at	date	The timestamp indicating when the record was created.	❌
modified_at	date	The timestamp indicating when the record was last updated or modified.	❌
packageId	string	Another identifier for the associated package, which seems to be a duplicate of package_id—this should be checked for redundancy.	❌

Sample JSON

{
  "id": "example_value",
  "type": "example_value",
  "localVersion": "example_value",
  "version": "example_value",
  "versionData": "example_value",
  "versions": "example_value",
  "package_id": "example_value",
  "draft_version": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "packageId": "example_value"
}