TypeDB Console 2.27.0-rc0

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.27.0-rc0

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Fix null ptr in diagnostics user-id generation

TypeDB Console 2.26.6

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.26.6

New Features

• Allow unicode TypeQL variables

  We update to the latest TypeQL, which supports unicode variables. This means TypeDB Console can now use unicode variables, as well as labels and string attribute values.

  For example, we can use Mandarin character sets:

  test::schema::write> define 人 sub entity;
                    
  Concepts have been defined
  
  test::schema::write*> commit
  Transaction changes committed
  > transaction test data write
  test::data::write> insert $人 isa 人; 
                  
  { $人 iid 0x826e80017fffffffffffffff isa 人; }
  
  answers: 1, total duration: 102 ms
  
  test::data::write*> commit
  Transaction changes committed
  > transaction test data read
  test::data::read> match $人 isa 人; get;
                 
  { $人 iid 0x826e80018000000000000000 isa 人; }
  
  answers: 1, total duration: 54 ms
  

Bugs Fixed

Code Refactors

• Use typedb-common from typeql/common, only deploy to CloudSmith

  We update Bazel dependencies and target paths following the merging of typedb-common into vaticle/typeql (see typedb/typeql#313).

  We also no longer upload build artifacts to the github releases page. Instead, the artifacts are available from our public cloudsmith repository, linked in the release notes.

• Bring in launch binary and console runner library from common

  We move the binary package and console-runner into this repository from typedb-common. typedb-console-runner is deployed to maven such that we can safely depend on it from other repos without creating Bazel dependency cycles.

Other Improvements

• Explicitly install python tool dependencies

  Since the upgrade to rules-python v0.24 (typedb/typedb-dependencies#460), we are required to explicitly install python dependencies in the WORKSPACE file. The python tools happened to be unused, so these errors were not visible until the sync dependencies tool was restored.

• Sync dependencies in CI

  We add a sync-dependencies job to be run in CI after successful snapshot and release deployments. The job sends a request to vaticle-bot to update all downstream dependencies.

  Note: this PR does not update the dependencies repo dependency. It will be updated automatically by the bot during its first pass.

• Only submit uncaught exceptions to diagnostics

• Set up CI filters for master-development workflow

• Make console runner use the same java installation as the calling process
  Makes TypeDB console runner use the same java installation as the calling process, so the system remain hermetic.

• Fix CI file and disable Core diagnostics in test

• Migrate artifact hosting to cloudsmith
  Updates artifact credentials, and deployment & consumption rules to use cloudsmith (repo.typedb.com) instead of the self-hosted sonatype repository (repo.vaticle.com).

• Remove typedb-console-runner's dependency on typedb-common

  We remove typedb-console-runner's dependency on common in order to reduce deployment complexity and make the maven library self-contained.

• Force hermitic JDK for builds

• Fix install-bazel-apt typo

TypeDB Console 2.26.6-rc1

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.26.6-rc1

New Features

• Allow unicode TypeQL variables

  We update to the latest TypeQL, which supports unicode variables. This means TypeDB Console can now use unicode variables, as well as labels and string attribute values.

  For example, we can use Mandarin character sets:

  test::schema::write> define 人 sub entity;
                    
  Concepts have been defined
  
  test::schema::write*> commit
  Transaction changes committed
  > transaction test data write
  test::data::write> insert $人 isa 人; 
                  
  { $人 iid 0x826e80017fffffffffffffff isa 人; }
  
  answers: 1, total duration: 102 ms
  
  test::data::write*> commit
  Transaction changes committed
  > transaction test data read
  test::data::read> match $人 isa 人; get;
                 
  { $人 iid 0x826e80018000000000000000 isa 人; }
  
  answers: 1, total duration: 54 ms
  

Bugs Fixed

Code Refactors

• Use typedb-common from typeql/common, only deploy to CloudSmith

  We update Bazel dependencies and target paths following the merging of typedb-common into vaticle/typeql (see typedb/typeql#313).

  We also no longer upload build artifacts to the github releases page. Instead, the artifacts are available from our public cloudsmith repository, linked in the release notes.

• Bring in launch binary and console runner library from common

  We move the binary package and console-runner into this repository from typedb-common. typedb-console-runner is deployed to maven such that we can safely depend on it from other repos without creating Bazel dependency cycles.

Other Improvements

• Explicitly install python tool dependencies

  Since the upgrade to rules-python v0.24 (typedb/typedb-dependencies#460), we are required to explicitly install python dependencies in the WORKSPACE file. The python tools happened to be unused, so these errors were not visible until the sync dependencies tool was restored.

• Sync dependencies in CI

  We add a sync-dependencies job to be run in CI after successful snapshot and release deployments. The job sends a request to vaticle-bot to update all downstream dependencies.

  Note: this PR does not update the dependencies repo dependency. It will be updated automatically by the bot during its first pass.

• Only submit uncaught exceptions to diagnostics

• Set up CI filters for master-development workflow

• Make console runner use the same java installation as the calling process
  Makes TypeDB console runner use the same java installation as the calling process, so the system remain hermetic.

• Fix CI file and disable Core diagnostics in test

• Migrate artifact hosting to cloudsmith
  Updates artifact credentials, and deployment & consumption rules to use cloudsmith (repo.typedb.com) instead of the self-hosted sonatype repository (repo.vaticle.com).

• Remove typedb-console-runner's dependency on typedb-common

  We remove typedb-console-runner's dependency on common in order to reduce deployment complexity and make the maven library self-contained.

• Force hermitic JDK for builds

• Fix install-bazel-apt typo

TypeDB Console 2.26.5

New Features

Bugs Fixed

Code Refactors

• Reconfigure CircleCI executors to use GLIBC 2.26

  We compile and release TypeDB Console using an older version of Linux, which requires GLIBC 2.26 instead of GLIBC 2.27. This change switches the build platform to Amazon Linux 2 (via Docker), which is based on CentOS, instead of Ubuntu 18.04, which is based on Debian.

  Additionally, we upgrade the Windows Orb to 5.0.0, which also allowed using a larger executor to reduce CI time.

Other Improvements

• Shorten diagnostic ID to 16 hex chars

TypeDB Console 2.26.3

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Downgrade release jobs to Ubuntu 18.04 for GLIBC version 2.27.0

• Implement error diagnostics

  We implement completely anonymous error reporting using Sentry. We submit error messages when the user receives a fatal error in Console.

  To disable diagnostics, use:

  typedb console --diagnostics-disable=true
  

• Update driver with fetch null fix

• Disable CircleCI mac remote cache to avoid too_many_open_files

TypeDB Console 2.26.0

API Changes

1. When connecting to TypeDB Core, we now use --core=<uri> instead of --server=<uri>
2. When connecting to TypeDB Cloud (previously Entperise), we now use --cloud=<uri> instead of --enterprise=<uri>

New Features

Bugs Fixed

Code Refactors

• Replace all instances of 'enterprise' with 'cloud'

  We replace the term 'enterprise' with 'cloud', to reflect the new consistent terminology used throughout Vaticle.
  In particular, this means that to connect to a Cloud instance (previously Enterprise), typedb console --cloud <address> replaces typedb console --enterprise <address>.

• Update command line interface

  We update the CLI options to use the more distinct --core flag for connecting to the core server, mirroring --enterprise (note: subsequently renamed to --cloud).

  Connecting to TypeDB Core:

  typedb console --core=<address>
  

  Connecting to TypeDB Cloud:

  typedb console --cloud=<address> --username=<username> --password --tls-enabled
  

  See typedb/typedb#6942 for full details.

  We also improve the UX of the windows version of the entry point. Console no longer opens in a new window, but rather begins the REPL in the current command line window.

Other Improvements

• Add aliases for encryption enable to match Cloud options more closely

TypeDB Console 2.25.7

New Features

• Upgrade to the latest TypeDB Driver, which includes improved error messages

Bugs Fixed

Code Refactors

Other Improvements

• Add ulimits to mac and linux releases

TypeDB Console 2.25.6

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Remove APT deployment and targets

TypeDB Console 2.25.0

New Features

• Implement Fetch query

  We update to the newest version of TypeDB Driver which supports Fetch queries.

  For more details on fetch queries, see typedb/typeql#300

Bugs Fixed

Code Refactors

Other Improvements

• Add newline after define and undefine print status to match new streaming query formatting

TypeDB Console 2.24.15

New Features

Bugs Fixed

• Fix unpacking driver runtime files into working directory

Due to a bug in the Java driver, we unpacked the driver dynamic library into the current working directory, rather than into a temporary directory.

We update to the driver version with the fix.

Code Refactors

Other Improvements