Skip to content

Clarify GraphQL status args availability on all content types#3026

Open
pwizla wants to merge 1 commit intomainfrom
cms/graphql-status-args-update-non-d-and-p
Open

Clarify GraphQL status args availability on all content types#3026
pwizla wants to merge 1 commit intomainfrom
cms/graphql-status-args-update-non-d-and-p

Conversation

@pwizla
Copy link
Copy Markdown
Collaborator

@pwizla pwizla commented Mar 31, 2026

This PR documents strapi/strapi 25763.

@pwizla pwizla self-assigned this Mar 31, 2026
@pwizla pwizla added this to the 6.19.0 milestone Mar 31, 2026
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment Mar 31, 2026 4:24pm

Request Review

```

:::note
The `status` and `hasPublishedVersion` arguments appear in the GraphQL schema for all content types, including those without [Draft & Publish](/cms/features/draft-and-publish) enabled. This is because nested relations to D&P-enabled content types inherit these arguments from the root query. For example, querying a `User` type (which does not use Draft & Publish) with `status: PUBLISHED` ensures that any populated relation to a Draft & Publish-enabled type like `Article` returns the published version.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we haven't already documented hasPublishedVersion anywhere, we're going to immediately deprecate it for something different in the next few weeks, so I wouldn't publish this. Sorry for the confusion!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, of course, makes sense! I was so focused on status that I overlooked this part 🤦‍♂️
I'll close the PR, then

@pwizla pwizla removed this from the 6.19.0 milestone Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: merge pending release Pending Strapi Release internal PRs created by the Strapi core team pr: chore source: CMS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants