Release v5.2.0 (#35)

* Bump rust sdk version * Update changelog * Add GitHub release automation to CI * Bump package.json version
hasura · Jul 30, 2024 · 5f2fc58 · 5f2fc58
1 parent e68e5b8
commit 5f2fc58
Show file tree

Hide file tree

Showing 6 changed files with 67 additions and 27 deletions.
diff --git a/.github/workflows/build_test_publish.yaml b/.github/workflows/build_test_publish.yaml
@@ -50,3 +50,21 @@ jobs:
       - run: npm publish --access public
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Get version from tag
+        id: get-version
+        run: |
+          echo "tagged_version=${GITHUB_REF#refs/tags/v}" >> $GITHUB_OUTPUT
+        shell: bash
+
+      - uses: mindsers/changelog-reader-action@v2
+        id: changelog-reader
+        with:
+          version: ${{ steps.get-version.outputs.tagged_version }}
+          path: ./CHANGELOG.md
+
+      - uses: softprops/action-gh-release@v1
+        with:
+          draft: false
+          tag_name: v${{ steps.get-version.outputs.tagged_version }}
+          body: ${{ steps.changelog-reader.outputs.changes }}
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,58 +1,60 @@
-# Changelog
+# NDC TypeScript SDK Changelog
 
-## Unreleased
-- The connector now listens on both ipv4 and ipv6 interfaces by default. This can be configured by using the `HASURA_CONNECTOR_HOST` environment variable, which sets the host the web server listens on.
+## [5.2.0] - 2024-07-30
+- The connector now listens on both ipv4 and ipv6 interfaces by default. This can be configured by using the `HASURA_CONNECTOR_HOST` environment variable, which sets the host the web server listens on. ([#34](https://github.com/hasura/ndc-sdk-typescript/pull/34))
+- Updated to support [v0.1.5 of the NDC Spec](https://hasura.github.io/ndc-spec/specification/changelog.html#015) ([#35](https://github.com/hasura/ndc-sdk-typescript/pull/35))
+  - There are no real changes in this version; it is a version number-only change
 
-## 5.1.0
+## [5.1.0] - 2024-06-19
 - Updated to support [v0.1.4 of the NDC Spec](https://hasura.github.io/ndc-spec/specification/changelog.html#014) ([#33](https://github.com/hasura/ndc-sdk-typescript/pull/33))
   - Support for [aggregates](https://hasura.github.io/ndc-spec/specification/queries/aggregates.html) over nested fields
 
-## 5.0.0
+## [5.0.0] - 2024-05-31
 - Updated to support [v0.1.3 of the NDC Spec](https://hasura.github.io/ndc-spec/specification/changelog.html#013) ([#32](https://github.com/hasura/ndc-sdk-typescript/pull/32))
   - Breaking change: new `nested_fields` property on `QueryCapabilities`; set it to `{}` to retain previous v0.1.2 semantics and not support new v0.1.3 capabilities.
   - Support [field arguments](https://hasura.github.io/ndc-spec/specification/queries/arguments.html#field-arguments)
   - Support [filtering](https://hasura.github.io/ndc-spec/specification/queries/filtering.html#referencing-nested-fields-within-columns) and [ordering](https://hasura.github.io/ndc-spec/specification/queries/sorting.html#type-column) by nested fields
   - Added a [`biginteger` type representation](https://hasura.github.io/ndc-spec/specification/schema/scalar-types.html#type-representations)
 
-## 4.6.0
+## [4.6.0] - 2024-04-17
 - Use [`prom-client`](https://github.com/siimon/prom-client) to implement the metrics endpoint ([#29](https://github.com/hasura/ndc-sdk-typescript/pull/29))
 - Allow any error code in custom HTTP responses ([#30](https://github.com/hasura/ndc-sdk-typescript/pull/30))
 
-## 4.5.0
+## [4.5.0] - 2024-04-17
 - Support [b3](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-propagator-b3#b3-formats) (zipkin) OpenTelemetry trace propagation headers ([#28](https://github.com/hasura/ndc-sdk-typescript/pull/28))
 
-## 4.4.0
+## [4.4.0] - 2024-04-05
 - Updated to support [v0.1.2 of the NDC Spec](https://hasura.github.io/ndc-spec/specification/changelog.html#012)
   - More precise [type representations](https://hasura.github.io/ndc-spec/specification/schema/scalar-types.html#type-representations) of scalar types were added and the general numeric ones were deprecated (`number` and `integer`)
 
-## 4.3.0
+## [4.3.0] - 2024-03-26
 - Updated to support [v0.1.1 of the NDC Spec](https://hasura.github.io/ndc-spec/specification/changelog.html#011)
   - A more [precise definition of equality operators](https://hasura.github.io/ndc-spec/specification/schema/scalar-types.html#note-syntactic-equality)
   - Scalar types can now [specify a representation](https://hasura.github.io/ndc-spec/specification/schema/scalar-types.html#type-representations), including an enum representation
 
-## 4.2.1
+## [4.2.1] - 2024-02-28
 - Add `main` and `types` properties to the `package.json` to enable `node10` module resolution to be used by projects using legacy TypeScript compiler settings
 
-## 4.2.0
+## [4.2.0] - 2024-02-23
 - OpenTelemetry spans are now attributed with `internal.visibility: "user"` so that they show up in the Hasura Console
 - `@hasura/ndc-sdk-typescript/instrumentation` now exports `withActiveSpan` to wrap a span around a function and `withInternalActiveSpan` which does the same but without the `internal.visibility: "user"` attribute.
 - Automatic OpenTelemetry instrumentation for fetch requests has been added
 
-## 4.1.0
+## [4.1.0] - 2024-02-21
 - Add OpenTelemetry support
   - Set env var `OTEL_EXPORTER_OTLP_ENDPOINT` to the endpoint to send OpenTelemetry to
   - `OTEL_SERVICE_NAME` overrides the service name
   - Command line arguments `--otlp-endpoint` and `--service-name` have been removed in favour of the environment variables
   - Import `@hasura/ndc-sdk-typescript/instrumentation` to use `initTelemetry` to initialize OpenTelemetry earlier in your startup, if necessary
 
-## 1.3.0
+## [1.3.0] - 2024-02-21
 - Add OpenTelemetry support
   - Set env var `OTEL_EXPORTER_OTLP_ENDPOINT` to the endpoint to send OpenTelemetry to
   - `OTEL_SERVICE_NAME` overrides the service name
   - Command line arguments `--otlp_endpoint` and `--service-name` have been removed in favour of the environment variables
   - Import `@hasura/ndc-sdk-typescript/instrumentation` to use `initTelemetry` to initialize OpenTelemetry earlier in your startup, if necessary
 
-## 4.0.0
+## [4.0.0] - 2024-02-19
 Breaking change: support for the [Connector Deployment Spec](https://github.com/hasura/ndc-hub/blob/main/rfcs/0000-deployment.md).
 
 - The connector configuration server has been removed
@@ -69,14 +71,14 @@ Breaking change: support for the [Connector Deployment Spec](https://github.com/
   - The `LOG_LEVEL` environment variable has changed to `HASURA_LOG_LEVEL`
   - The `PRETTY_PRINT_LOGS` environment variable has changed to `HASURA_PRETTY_PRINT_LOGS`
 
-## 3.0.0
+## [3.0.0] - 2024-02-13
 Breaking change: support for the [v0.1.0-rc.15 of NDC Spec](https://github.com/hasura/ndc-spec/compare/v0.1.0-rc.14...v0.1.0-rc.15).
 
 - The [mutation request/response format has changed](https://github.com/hasura/ndc-spec/pull/90).
   - `MutationOperation` fields are now defined as a `NestedField`
   - `MutationOperationResponse` now returns a single value rather than a rowset
 
-## 2.0.0
+## [2.0.0] - 2024-02-05
 Breaking change: support for the [v0.1.0-rc.14 of NDC Spec](https://github.com/hasura/ndc-spec/compare/v0.1.0-rc.13...v0.1.0-rc.14).
 
 - Function name formatting is now standard JavaScript `camelCase`. NDC types used for wire-transmission match the spec (snake_cased).
@@ -93,18 +95,16 @@ Breaking change: support for the [v0.1.0-rc.14 of NDC Spec](https://github.com/h
   - `explain` capability moved to `query.explain`. `mutation.explain` capability added.
 - `ComparisonOperatorDefinition` now has `equal` and `in` as [two standard definitions](https://github.com/hasura/ndc-spec/pull/79/files) and custom operators can be defined. The equality operator is no longer required to be defined and must be explicitly defined.
 
-## 1.2.8
+## [1.2.8] - 2024-01-18
 - Add new `ConnectorError` types:
   - `UnprocessableContent`: The request could not be handled because, while the request was well-formed, it was not semantically correct. For example, a value for a custom scalar type was provided, but with an incorrect type
   - `BadGateway`: The request could not be handled because an upstream service was unavailable or returned an unexpected response, e.g., a connection to a database server failed
 - Generate TypeScript declaration maps for better "go to definition" tooling
 
-## 1.2.7
-
+## [1.2.7] - 2023-12-21
 - `get_serve_command` and `get_serve_configuration_command` now support creation without
   automatically starting servers. This allows usage in scenarios where a customized server startup
   is desired.
 
-## 1.2.6
-
+## [1.2.6] - 2023-12-15
 - added auth hook using secret token
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@hasura/ndc-sdk-typescript",
-  "version": "5.1.0",
+  "version": "5.2.0",
   "description": "",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

diff --git a/typegen/Cargo.toml b/typegen/Cargo.toml
@@ -6,7 +6,7 @@ edition = "2021"
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
 
 [dependencies]
-ndc-models = { git = "http://github.com/hasura/ndc-spec.git", tag = "v0.1.4" }
+ndc-models = { git = "http://github.com/hasura/ndc-spec.git", tag = "v0.1.5" }
 schemars = "0.8.15"
 serde = "^1.0"
 serde_json = "1.0.107"