{"version":"2.1.232","anchor":"one-consistent-message-when-artifact-commands-need-you-to-lo","canonical_anchor":"one-consistent-message-when-artifact-commands-need-you-to-lo","heading":"One consistent message when artifact commands need you to log in","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/one-consistent-message-when-artifact-commands-need-you-to-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### One consistent message when artifact commands need you to log in\n\nPublishing and listing artifacts now share one \"Not authenticated, run \/login\" message.\n\n**What**\n\nPublishing an artifact and listing artifacts now report authentication failures with the same wording, which starts with \"Not authenticated\", tells you to run `\/login`, and puts the underlying detail in parentheses. The older separate phrasings for each command are gone.\n\n**Details**\n\n- Failures that are not about authentication still read \"publish unavailable: \" and \"artifact listing unavailable: \" with the detail appended.\n\n**Evidence**\n\n`artifact listing unavailable: `\n\n- Area: Artifacts\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}