Under the hood
Publishing an artifact now checks its file path for disguised or lookalike spelling
What
When the artifacts tool resolves the file path for something being published, its result now includes a new unverifiedSpelling field alongside the existing pin and redirect information. This points to the same check for obfuscated or disguised path names already used elsewhere (such as when registering a repository root) now also being applied to files being published as artifacts.
Why
This helps catch cases where a published artifact's path looks legitimate but uses a disguised spelling, closing a gap between two features that previously applied this check inconsistently.