{"version":"2.1.246","anchor":"artifact-publish-limits-symlinked-directories-and-type-owned","canonical_anchor":"artifact-publish-limits-symlinked-directories-and-type-owned","heading":"Artifact publish limits, symlinked directories, and type-owned file errors","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-publish-limits-symlinked-directories-and-type-owned","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact publish limits, symlinked directories, and type-owned file errors\n\nArtifact publishing counts file_path in its limit, handles symlinked directories, and names reserved-file errors.\n\n**What**\n\nPublishing a version of an artifact now counts the single `file_path` entry alongside the `files` list when it checks the per-version file limit, resolves paths correctly when your working directory is a symlink, and gives specific advice when you try to publish files the artifact type reserves for itself. The over-limit and reserved-file failures both name what went wrong instead of falling back to a generic retry message.\n\n**Details**\n\n- The over-limit error now reads \"`file_path` and `files` list N entries (removals included)\", where previously only the `files` list and removals were counted toward the total.\n- A typed path is resolved against both the working directory and its real path, so publishing from a symlinked directory no longer produces a wrong publish base.\n- When the server marks a file error with the kind `type_owned_path`, meaning the path is one the artifact type owns, the message names the offending files and tells you to leave them out of `file_path` and `files`, rather than reporting an unlabelled failure.\n- The reserved-file message depends entirely on the server reporting that kind on the publish response; without it the older generic error still shows.\n- Applies to every artifact publish with no flag, setting, or environment variable to gate it.\n\n**Evidence**\n\n`` `file_path` and `files` list ``, `type_owned_path`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}