{"version":"2.1.248","anchor":"more-publishes-treated-as-artifact-type-instances","canonical_anchor":"more-publishes-treated-as-artifact-type-instances","heading":"More publishes treated as artifact-type instances","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/more-publishes-treated-as-artifact-type-instances","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### More publishes treated as artifact-type instances\n\nMore publishes are now recognised as instances of an artifact type.\n\n**What**\n\nThe check for whether a publish targets an instance of an artifact type no longer requires the session's types flag or a tracked file list. It now says yes if the file was created from a type, or if its frame URL parses as an artifact slug at all.\n\n**Evidence**\n\n`createdFromType`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}