Skip to content

Commit cdeffd0

Browse files
authored
Update entrypoint.sh variables and bump Node.js version (#25)
* chore: update Dockerfile to use Node.js version 20 * chore: update environment variable names in entrypoint.sh
1 parent acd8afc commit cdeffd0

File tree

3 files changed

+8
-3
lines changed

3 files changed

+8
-3
lines changed

Dockerfile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
FROM node:18
1+
FROM node:20
22

33
LABEL version="1.1.0"
44
LABEL repository="http://github.com/sanity-io/actions-sanity-io"

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,11 @@ Below are two examples of usage. Do you use this GitHub Action for a different p
88

99
Depending on your use case, you will need to [generate a read or write token](https://www.sanity.io/docs/http-auth#robot-tokens-4c21d7b829fe) from your project's management console and then [add it as a secret](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository) in the Studio GitHub repository. In the examples below, the secret was named `SANITY_AUTH_TOKEN`.
1010

11+
### Environment variables
12+
13+
- `SANITY_AUTH_TOKEN` - **Required**. The token to authenticate with the Sanity API.
14+
- `SANITY_STUDIO_CONFIG_PATH` - **Optional**. The path to the studio in your repository.
15+
1116
### Studio deployment on push requests
1217

1318
_This workflow requires a read token._

entrypoint.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ if [ -z "$SANITY_AUTH_TOKEN" ]; then
77
exit 126
88
fi
99

10-
if [ -n "$STUDIO_CONFIG_PATH" ]; then
11-
cd "$STUDIO_CONFIG_PATH"
10+
if [ -n "$SANITY_STUDIO_CONFIG_PATH" ]; then
11+
cd "$SANITY_STUDIO_CONFIG_PATH"
1212
fi
1313

1414
sh -c "SANITY_AUTH_TOKEN='$SANITY_AUTH_TOKEN' sanity $*"

0 commit comments

Comments
 (0)