TinaCMS V0.68.14

July 21, 2022

By Logan Anderson

TinaCMS Version 0.68.14 brings some extensive improvements to Tina. Here is a short list of a few of the major features:

  1. New unified client that can be used on the frontend and backend.
  2. Data layer is enabled by default
  3. Better support for read only tokens
  4. Clearer and more concise way of working with TinaCMS in CI

To update to the latest version run:

yarn add tinacms@latest
yarn add --dev @tinacms/cli@latest

New Unified client

TinaCMS has always been missing a "unified way" to query and fetch content. Previously, there was `StaticRequest`, "Read only token client", "Experimental Generated client" and "just using fetch". Now all of these have been reduced to a single client that can be used on both the frontend and backend.

There are only a couple of small changes to be made in order to update.

Updates in .tina/schema.{ts,js}

Instead of passing an apiURL into defineConfig, now the clientId, branch and read only token (NEW) are all configured in the schema. The generated client must be passed to defineConfig.

Instead of needing to configure localhost as the apiURL, the local graphql api is now used by default with yarn dev.

This requires a change to the schema and the scripts:

// .tina/schema.ts
+ import { client } from "./__generated__/client";
// ...
const schema = defineSchema({
+ config: {
+ branch: "***",
+ clientId: "***",
+ token: "***",
collections: [
// ...
// ...
- const branch = "***"
- const clientId = "***"
- const apiURL =
- process.env.NODE_ENV == 'development'
- ? 'http://localhost:4001/graphql'
- : `https://content.tinajs.io/content/${clientId}/github/${branch}`
export const tinaConfig = defineConfig({
+ client,
- apiURl,
// ...
export default schema

The token must be a wildcard token (*) and can be generated from the Tina dashboard. Read more about read only tokens here

For more information about where to get these values, see the "going to production" docs.

Updates to scripts in package.json

We now recommend using the content API in CI and using our new dev and build commands. The dev command starts the local GraphQL server and runs your subscript (next dev). The build command compiles the client with the production URL and builds the GraphQL schema.

The scripts should look like this:

"scripts": {
"dev": "tinacms dev -c \"next dev\"",
"build": "tinacms build && next build"
// ... Other Scripts

When developing, run yarn dev which starts the dev server and next dev process in the same terminal.

Updates to generated files (optional)

We now recommend ignoring most of the generated files. This is because client.ts and types.ts will be generated in CI when tinacms build runs.

To remove them from your repository, run git rm --cached .tina/__generated__/* and then yarn tinacms build to update the generated files that need to stay.

Once these updates have been made, the new client should be configured and ready to be used for querying.

Migrating data fetching

To migrate data fetching, all uses of staticRequest, or GetExperimentalClient can be replaced with client.request or client.queries.<QueryName> respectively.

For example, to migrate usage of the staticRequest function:

// pages/home.js
- import { staticRequest } from 'tinacms'
+ import { client } from '../[pathToTina]/.tina/__generated__/client'
const getStaticProps = async () => {
const query = `
query Post($relativePath: String!) {
post(relativePath: $relativePath) {
const variables = {
relativePath: 'hello-world.md',
let data = {}
try {
- data = await staticRequest({
- query,
- variables,
- })
+ data = await client.request({
+ query,
+ variables,
+ })
} catch {
// swallow errors related to document creation
return {
props: {
//myOtherProp: 'some-other-data',

Alternatively to client.request, you can also request content with the client's auto-generated queries property.

// fetch a post, without writing GraphQL
const { data, query, variables } = await client.queries.post({
relativePath: 'home.mdx',

For more information, see the new data fetching docs.

Data layer is enabled by default

The data layer is now enabled by default. With this feature your repository is cached, allowing the content to be queried without using GitHub's API. This makes data fetching faster and it also allows us to bypass GitHub's api limits.

There is no action required for this change besides updating to the latest version of @tinacms/cli.

For a full set of changes please see the changelog for this version.

Last Edited: July 21, 2022