v4.0.3

Changes

• Hide inaccessible projects in link command — Projects where the user doesn't have access permissions are no longer shown in the project selection list during datocms link

v4.0.2

Changes

• Allow re-login without requiring logout first — Running datocms login when already authenticated now replaces existing credentials instead of blocking
• Improve OAuth token resolution — Linked projects (via datocms link) now take priority over the DATOCMS_API_TOKEN environment variable, so OAuth-based authentication is not silently overridden
• Improve error messages — Better error message when a linked project cannot be accessed, mentioning possible OAuth permission changes

v4.0.0

Easier (and safer) project linking with OAuth

OAuth login is now the recommended way to authenticate. The new setup is fully guided: datocms login opens your browser, datocms link lets you search and select a project interactively — no tokens to copy, no environment variables to configure. Every API call is tied to your personal identity, giving teams clear visibility over who made which changes.

New commands

• datocms login — authenticate your DatoCMS account via OAuth
• datocms link — connect the current directory to a specific DatoCMS project
• datocms logout — remove stored credentials
• datocms whoami — check which account you're logged in as
• datocms unlink — disconnect a directory from a project

What changed for existing users

Nothing breaks. The old profile:set and profile:remove commands still work — they redirect to link and unlink under the hood. Existing scripts and CI/CD pipelines using DATOCMS_API_TOKEN or the --api-token flag are completely unaffected.

@datocms/cli v3.1.3

New Features

• New schema:generate command - Generate TypeScript schemas from DatoCMS models
• Enhanced migrations:new command - Added --schema option for schema-specific migrations

Bug Fixes

• Various fixes and stability improvements