Update VERSION to 2.18.1, fix key loading from heroku for NPM, and use updated release note validation flow

Author: flyingsilverfin

.factory/automation.yml

@@ -101,7 +101,9 @@ release:
   validation:
     validate-release-notes:
       image: vaticle-ubuntu-22.04
-      command: bazel run @vaticle_dependencies//tool/release/notes:validate --test_output=streamed -- ./RELEASE_NOTES_LATEST.md
+      command: |
+        export NOTES_VALIDATE_TOKEN=$REPO_GITHUB_TOKEN
+        bazel run @vaticle_dependencies//tool/release/notes:validate --test_output=streamed -- $FACTORY_OWNER $FACTORY_REPO ./RELEASE_NOTES_LATEST.md
   deployment:
     deploy-github:
       image: vaticle-ubuntu-22.04
@@ -125,7 +127,7 @@ release:
     deploy-npm-release:
       image: vaticle-ubuntu-22.04
       command: |
-        curl https://cli-assets.heroku.com/apt/release.key | sudo apt-key add -
+        wget -q -O - https://cli-assets.heroku.com/apt/release.key | sudo apt-key add -
         wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
         sudo apt update -y
         sudo apt install -y expect

RELEASE_NOTES_LATEST.md

@@ -1,6 +1,6 @@
 # TypeDB Protocol
 
-This version extends the network API with exciting new features like value variables and querying with annotations more generally in concepts' APIs.
+This release aims to fix the release pipeline for client-nodejs. The remaining released artifacts are identical to 2.18.0.
 
 Documentation: https://docs.vaticle.com/docs/client-api/
 
@@ -47,40 +47,16 @@ yarn install typedb-protocol
 
 
 ## New Features
-- **Add protocol versioning transmitted during connection open**
-  
-  We add a new connection opening request, which allows transmitting the protocol version for the server to verify.
-  
-  As this is the first versioned protocol, we set the version number to version 1.
-  
-  Previous versions are assumed to be version < 1, and can be considered 0 for now.
-  
-  
-- **Introduce value query answers**
-  
-  Implement protocol required to return 'Value' answers in as part of the responses from `match` queries. To support this we generalise some of the message definitions used to transmit attribute values and value types.
-  
-  
-- **Introduce message types to encode annotations**
-  
-  We replace usages of `boolean` for key arguments with a message type called `Annotation` - this gives us a natural place to extend the set/capabilities of the annotations in the future. The new message type is used to implement the new "unique" annotation.
-  
-  
+
 
 ## Bugs Fixed
 
+- **Fix key loading from heroku for NPM**
+
 
 ## Code Refactors
 
 
 ## Other Improvements
-- **Update release notes workflow**
-  
-  We integrate the new release notes tooling. The release notes are now to be written by a person and committed to the repo.
-  
-  
-- **Make Concept.value.value_type use consistent underscoring**
-
-- **Annotation serialisation uses specialised message types**
 
 

VERSION

@@ -1 +1 @@
-2.18.0
+2.18.1

dependencies/vaticle/repositories.bzl

@@ -21,5 +21,5 @@ def vaticle_dependencies():
     git_repository(
         name = "vaticle_dependencies",
         remote = "https://github.com/vaticle/dependencies",
-        commit = "707fc228b5eff85527107243942f2cea1880f775", # sync-marker: do not remove this comment, this is used for sync-dependencies by @vaticle_dependencies
+        commit = "d09712afef2df4fc53d04aa197ae9cc8cfddee52", # sync-marker: do not remove this comment, this is used for sync-dependencies by @vaticle_dependencies
     )