{"version":"2.1.232","anchor":"artifact-publish-rejects-bad-create-endpoint-option-combinat","canonical_anchor":"artifact-publish-rejects-bad-create-endpoint-option-combinat","heading":"Artifact publish rejects bad create-endpoint option combinations","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/artifact-publish-rejects-bad-create-endpoint-option-combinat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Artifact publish rejects bad create-endpoint option combinations\n\nBad artifact publish option combinations are rejected up front instead of failing at the server.\n\n**What**\n\nIn the gated artifact publishing path, passing a create path together with a url, force, baseVersion or files list is now rejected before any request is made, as `create_bad_combo` with the message \"invalid publish options\". A 404 from the create endpoint is now reported as `create_not_enabled` and says explicitly that nothing was created.\n\n**Evidence**\n\n`create endpoint not available (404) \u2014 nothing was created`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}