Merge pull request #2056 from nhost/changeset-release/main

chore: update versions

dashboard/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @nhost/dashboard
 
+## 0.17.14
+
+### Patch Changes
+
+- 80b22724d: chore(deps): bump `@types/react` to `v18.2.13`, `@types/react-dom` to `v18.2.6` and `@storybook/testing-library` to `v0.2.0`
+
+## 0.17.13
+
+### Patch Changes
+
+- cc02902cb: chore(docs): update environment variable documentation
+
 ## 0.17.12
 
 ### Patch Changes

dashboard/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nhost/dashboard",
-  "version": "0.17.12",
+  "version": "0.17.14",
   "private": true,
   "scripts": {
     "preinstall": "npx only-allow pnpm",
@@ -96,7 +96,7 @@
     "@storybook/builder-webpack5": "^6.5.14",
     "@storybook/manager-webpack5": "^6.5.14",
     "@storybook/react": "^6.5.14",
-    "@storybook/testing-library": "^0.0.13",
+    "@storybook/testing-library": "^0.2.0",
     "@testing-library/dom": "^9.0.0",
     "@testing-library/jest-dom": "^5.16.5",
     "@testing-library/react": "^14.0.0",
@@ -104,8 +104,8 @@
     "@types/lodash.debounce": "^4.0.7",
     "@types/node": "^16.11.7",
     "@types/pluralize": "^0.0.29",
-    "@types/react": "18.2.12",
+    "@types/react": "18.2.13",
-    "@types/react-dom": "18.2.5",
+    "@types/react-dom": "18.2.6",
     "@types/react-table": "^7.7.12",
     "@types/testing-library__jest-dom": "^5.14.5",
     "@types/validator": "^13.7.10",

dashboard/src/features/projects/environmentVariables/settings/components/SystemEnvironmentVariableSettings/SystemEnvironmentVariableSettings.tsx

@@ -123,7 +123,7 @@ export default function SystemEnvironmentVariableSettings() {
   return (
     <SettingsContainer
       title="System Environment Variables"
-      description="Environment Variables are key-value pairs configured outside your source code. They are used to store environment-specific values such as API keys."
+      description="System environment variables are automatically generated from the configuration file and your project's subdomain and region."
       docsLink="https://docs.nhost.io/platform/environment-variables#system-environment-variables"
       rootClassName="gap-0"
       className="mt-2 mb-2.5 px-0"

docs/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @nhost/docs
 
+## 0.3.3
+
+### Patch Changes
+
+- cc02902cb: chore(docs): update environment variable documentation
+
 ## 0.3.2
 
 ### Patch Changes

docs/docs/graphql/remote-schemas/stripe.mdx

@@ -138,13 +138,21 @@ export default server
 
 Add `STRIPE_SECRET_KEY` as an environment variable.
 
-If you're using Nhost, add `STRIPE_SECRET_KEY` to `.env.development` like this:
+If you're using Nhost, add `STRIPE_SECRET_KEY` to `nhost.toml` like this:
+
+```
+[[ global.environment ]]
+name=STRIPE_SECRET_KEY
+value='{{ secrets.STRIPE_SECRET_KEY }}'
+```
+
+And then add to your `.secrets` file:
 
 ```
 STRIPE_SECRET_KEY=sk_test_***
 ```
 
-And add the production key (`sk_live_***`) to [environment variables](/platform/environment-variables) in the Nhost dashboard.
+In production set your secret with your stripe production key (`sk_live_***`) in the Nhost dashboard.
 
 Learn more about [Stripe API keys](https://stripe.com/docs/keys#obtain-api-keys).
 

docs/docs/platform/environment-variables.mdx

@@ -6,10 +6,6 @@ image: /img/og/platform/environment-variables.png
 
 Environment Variables are key-value pairs configured outside your source code. They are used to store environment-specific values such as API keys.
 
-You can manage your project's Environment Variables in Nhost Dashboard under **Variables**. When you define a new variable, you can set one value for **production** and one for **development**.
-
-![Environment Variables](/img/platform/environment-variables/environment-variables.png)
-
 Environment Variables are available for:
 
 - [Hasura GraphQL Engine](/graphql)
@@ -17,13 +13,44 @@ Environment Variables are available for:
 
 When an Environment Variable has updated the changes happen immediately for Hasura GraphQL Engine. For Serverless Functions, a new deployment via [Git](/platform/git) is required.
 
+## Custom Environment Variables
+
+You can manage your project's Environment Variables in the Nhost Dashboard or by using the configuration file.
+
+### Dashboard
+
+![Environment Variables](/img/platform/environment-variables/environment-variables.png)
+
+Environment Variables can be managed in the Nhost Dashboard under **Settings** → **Environment Variables**.
+
+### Configuration File
+
+Environment Variables can also be managed by adding new `[[global.environment]]` sections to the `nhost.toml` file.
+
+```toml
+[global]
+[[global.environment]]
+name = 'MY_ENV_VAR'
+value = '<first-value>'
+
+[[global.environment]]
+name = 'MY_OTHER_ENV_VAR'
+value = '<second-value>'
+
+# ... omitted for brevity
+```
+
+These environment variables will also be available on the Nhost Dashboard after committing and pushing the changes to your Git repository.
+
 ## System Environment Variables
 
-System Environment Variables are automatically available in production and during local development. The following system Environment Variables are available:
+System environment variables are automatically generated from the configuration file and your project's subdomain and region.
+
+The following system environment variables are available:
 
 - `NHOST_ADMIN_SECRET`
 - `NHOST_WEBHOOK_SECRET`
-- `NHOST_BACKEND_URL` ([deprecated](https://github.com/nhost/nhost/discussions/1319))
+- ~~`NHOST_BACKEND_URL`~~ ([deprecated](https://github.com/nhost/nhost/discussions/1319))
 - `NHOST_SUBDOMAIN`
 - `NHOST_REGION`
 - `NHOST_HASURA_URL`
@@ -33,7 +60,9 @@ System Environment Variables are automatically available in production and durin
 - `NHOST_FUNCTIONS_URL`
 - `NHOST_JWT_SECRET`
 
-Example values:
+`NHOST_ADMIN_SECRET`, `NHOST_WEBHOOK_SECRET` and `NHOST_JWT_SECRET` are populated with values from the configuration file. The rest of the system environment variables are populated with values from your project's subdomain and region.
+
+**Example values**:
 
 ```text
 NHOST_ADMIN_SECRET=e7w36ag287qn5qry795f6ymm57qgvqup
@@ -58,10 +87,3 @@ NHOST_FUNCTIONS_URL=https://abc123abc.functions.eu-central-1.nhost.run/v1
 
 NHOST_JWT_SECRET={"type": "HS256", "key": "vumpbe2w2mgaqj5yqfp7dvxu6kywtvsgb68ejpdaqxerea8jwrsszdp2dhkjxsh4df69pzm3ja6ukedx8ja43zdt6q9kgbgg2w9vh2sedeppukud9a2qzy29v3afdn7m"}
 ```
-
-## Development Environment Variables
-
-When developing locally using the [CLI](/cli), Environment Variables set in `.env.development` are available in your local environment. There are two ways to manage them:
-
-1. Edit the `.env.development` file manually.
-2. Add development Environment Variables in the Nhost Dashboard and use `nhost env pull` to sync them. This way, your team members will also have access to the same Environment Variables.

docs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nhost/docs",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",

packages/docgen/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @nhost/docgen
 
+## 0.1.11
+
+### Patch Changes
+
+- 5ef0b3157: chore(deps): bump `commander` to `v11`
+
 ## 0.1.10
 
 ### Patch Changes

packages/docgen/package.json

@@ -2,7 +2,7 @@
   "name": "@nhost/docgen",
   "description": "Documentation generator for classes and functions",
   "private": true,
-  "version": "0.1.10",
+  "version": "0.1.11",
   "license": "MIT",
   "main": "dist/index.cjs.js",
   "types": "dist/index.d.ts",
@@ -40,7 +40,7 @@
   },
   "dependencies": {
     "chalk": "4",
-    "commander": "^10.0.0",
+    "commander": "^11.0.0",
     "just-kebab-case": "^4.1.1",
     "prettier": "^2.7.1",
     "valtio": "^1.6.4"