{"version":"2.1.267","anchor":"artifact-create-from-type-now-also-rejects-a-deadline-fiel","canonical_anchor":"artifact-create-from-type-now-also-rejects-a-deadline-fiel","heading":"Artifact create-from-type now also rejects a deadline field","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-create-from-type-now-also-rejects-a-deadline-fiel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact create-from-type now also rejects a `deadline` field\n\nCreating an Artifact from a type_url now also rejects a stray deadline field\n\n**What**\n\nWhen an Artifact is created from a `type_url` (a type-based template), Claude Code already stripped out several fields that don't belong on that kind of creation, such as `url`, `pr_review`, `capabilities`, `contract`, `lang`, and `force`. Now `deadline` is rejected the same way.\n\n**Why**\n\nA type-based Artifact always gets its settings from its type, so a `deadline` value supplied alongside it would be meaningless or conflicting. Rejecting it keeps creation requests consistent and catches a mistake early instead of silently ignoring it.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}