keystonejs/keystone

Field can be editable when `graphql.omit.update` is set

Open

#9665 opened on Jul 22, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (14,870 stars) (2,386 forks)batch import
help wanted

Description

Regression introduced in https://github.com/keystonejs/keystone/pull/9663 and https://github.com/keystonejs/keystone/pull/9664

Contributor guide

Tech stack
javascriptnodejsgraphql
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js basicsGraphQL basicsKeystone framework basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate the changes in PRs #9663 and #9664 that introduced the regression. Examine the GraphQL schema generation code, particularly where the 'update' omit option is handled. The fix likely involves ensuring that when `graphql.omit.update` is set, the field is not editable in update mutations. Look at the files changed in those PRs, typically located in the `packages` directory related to GraphQL field configuration.