{"version":"2.1.280","anchor":"artifact-publish-now-refuses-declarations-that-silently-rese","canonical_anchor":"artifact-publish-now-refuses-declarations-that-silently-rese","heading":"Artifact publish now refuses declarations that silently reset db rules or user scopes","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/artifact-publish-now-refuses-declarations-that-silently-rese","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Artifact publish now refuses declarations that silently reset db rules or user scopes\n\nPublishing an artifact capability now gets refused if it would silently wipe out existing db rules or user scopes\n\n**What**\n\nWhen publishing capabilities for an artifact, Claude Code now checks whether a `db` (database) or `user` block is being resent without the `rules` or `scopes` that were previously stored for it. If so, the publish is refused with a message explaining that the stored rules or scopes would be reset to their defaults, which are open access.\n\n**Why**\n\nThis prevents accidentally opening up access by silently dropping existing security rules or scopes during a republish, catching what would otherwise be a dangerous, invisible change.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}