Skip to content

Releases: typedb/typedb-console

Grakn Console 1.0.7

11 Aug 11:32
c9f6b77
Compare
Choose a tag to compare

New Features

Bugs Fixed

Code Refactors

Other Improvements

  • fix deps for release and bump VERSION.
    Fix deps for release to release tags and bump VERSION.

  • Depend on testing via grakn core artifact.
    Change console to depend on Grakn core artifact for testing.

  • Test building with updated @graknlabs_dependencies.
    Update @graknlabs_dependencies to latest version

  • Integrate building with BuildBuddy.
    Migrate from RBE to BuildBuddy

  • Declare most dependencies using maven() rule.
    Declare most dependencies using maven rule from @graknlabs_dependencies

  • Fix CI by updating client-java.
    Fix CI by updating client-java

  • Add deploy-console-distribution.
    As part of our move away from building artefacts from other repos using bazel source (which causes subtly different artefacts to be built from the ones that were testing within that repo), we need to add deploy steps to repos that build artefacts that can be depended on.
    We are adding a deploy rule to console to deploy the /console sub-directory of the distribution, complete with logback.xml.

  • Depend on @graknlabs_dependencies.
    Console now uses dependencies that are declared in graknlabs_dependencies

  • Add console-deps deployment to repo as archive.
    Grakn core depends on console in order to create an "all" release package, however, it currently builds console from source (via bazel) which means we have two "releases" of console, one in this repo and one in the grakn repo, and they can have different sets of dependencies. This could cause any number of problems, not least being that tests run in this repo do not necessarily reflect the correctness of console in grakn. It also causes problems for us locally when using bazel to develop locally, because external workspaces imported in our own repo can leak into console unintended.
    In order to fix this "artifact drift" we need to move to a "single true artifact" pattern. Currently, this artifact will only be console-deps, which does not include configuration (only logback.xml right now). At some point, we should move to the full console release being the distributed artifact and combined into the grakn "all" release.

Grakn Console 1.0.6

17 Jun 20:46
3686b81
Compare
Choose a tag to compare

New Features

Bugs Fixed

Code Refactors

  • Update to 1.8 dependencies.
    We upgrade console to use the latest grakn core and client-java dependencies, resolving their own build issues induced by circular dependencies.

Other Improvements

  • Remove extra logback inclusion.
    Starting console from April 2020 onwards resulted in verbose startup logging. This was due to an extra logback file being included in the JAR, which we remove again.

  • Migrate load relative path file in and bump deps.
    typedb/typedb#5043 as a part of refactoring test packages in core, we move one end-to-end test into console as it should not have been tested in core.
    Bump dependencies of core, protocol, client-java, build-tools. Significant change includes using value instead of datatype.

Grakn Console 1.0.5

24 Apr 18:58
593e84f
Compare
Choose a tag to compare

Bugs Fixed

  • Disable excessive logging

    We accidentally enabled logging at the info level, causing excessing logging. This has been properly disabled in this release.

Other Improvements

  • Use new 1.7 client-java improvements

    Update console to use the improvements coming in the 1.7 release of client-java.

Grakn Console 1.0.4

14 Apr 23:02
b8199c3
Compare
Choose a tag to compare

New Features

  • Add ability to list and delete keyspaces from console.
    List, Delete existing keyspaces from console. Previously we had to spin up an interactive python console or something similar to see what keyspaces even exist in a distribution, let alone delete them.
    To access the new commands, we would run in any console session:
    grakn> keyspace list
    
    which should print the list of keyspaces on the grakn distribution the console is connected to.
    Similarly, we can do:
    grakn> keyspace delete somekeyspace
    Successfully deleted somekeyspace
    

Bugs Fixed

Code Refactors

Other Improvements

  • Upgrade to Bazel 3.0.0.
    Upgrade Bazel to latest upstream version

  • Update copyright headers to 2020.
    In order for build not to break after typedb/typedb-dependencies#122, copyright headers need to be updated.

Grakn Console 1.0.3

17 Jan 14:15
8a493cc
Compare
Choose a tag to compare

New Features

Bugs Fixed

Code Refactors

Other Improvements

  • Update gRPC to 1.24.1
    Bump @graknlabs_build_tools and @graknlabs_protocol versions
    Upgrade gRPC Maven dependencies to 1.24.1; add grpc-api
    Update targets to depend on grpc-api

Grakn Console 1.0.2

25 Nov 18:04
2c3a61c
Compare
Choose a tag to compare

New Features

Bugs Fixed

  • Make history file optional.
    Fix #7
    Previously, Grakn Console would crash in case history file could not be created (possible reasons are user's home directory being non-present or mounted read-only)

  • Remove Grakn Core Concept dependency.

  • Reflect Client/Server API and Concept split.
    Since the split of client-java and server's interfaces to use grakn.core.concept versus grakn.client.concept various classes in console have to be refactored. Also enables GraknConsoleIT for grakn console.

Code Refactors

  • New Delete Behavior.

  • Refactor how version is provided to deployment rules.
    Adapt @graknlabs_console to latest changes in bazel-distribution (in particular, typedb/bazel-distribution#150)

Other Improvements

  • We've updated graql, common and protocol which are depended by client-java.

  • Upgrade protocol and add README.

Grakn Console 1.0.1

25 Sep 10:31
28069a3
Compare
Choose a tag to compare

New Features

Bugs Fixed

Code Refactors

Other Improvements

  • Use release-validate-deps to ensure that Console depends on released versions of common, console, graql, protocol , and client-java.
    We have added a validation step using //ci:release-validate-deps in order to ensure that console is releasable only if it depends on released versions of common, console, graql, protocol , and client-java.