Skip to main content
Channel notices allow channel administrators to communicate important information to users who install packages from their channel. When users run conda install or conda update from a channel with active notices, conda displays these messages in the terminal. Use channel notices to announce:
  • Breaking changes in upcoming releases
  • Deprecation warnings
  • Security advisories
  • Migration instructions
  • Maintenance windows
For more information on anaconda channel notice command options, see anaconda channel notice.

​
How notices work

When you publish a notice to your channel, conda clients automatically fetch and display it to users during package operations. Each notice has a unique ID, and once a user has seen a notice, it won’t be shown again. Conda fetches notices from https://conda.anaconda.org/<CHANNEL>/notices.json. Users must have the channel configured in their .condarc file to receive notices.

​
Notice lifecycle

Notices follow a three-stage lifecycle:
  1. Draft: Created but not visible to channel users. Use drafts to prepare notices before publishing.
  2. Published: Active and visible to channel users until the expiration date.
  3. Archived/Deleted: No longer visible to users. Archive notices to stop showing them before their expiration date or to preserve them for records. Delete records to remove them from the notice list.
Archived notices can be restored by applying the publish status to them again. Deleted notices can still be viewed with anaconda channel list by specifying --status deleted, but cannot be restored.

​
Prerequisites

  • anaconda-client version 1.15.0 or later
  • Owner or administrator access to the channel
To verify your anaconda-client version:
To update your anaconda-client version:

​
Creating a notice

Create a notice with the anaconda channel notice create command.
Notices are created as drafts by default and must belong to a specific channel, even if you are not publishing them yet.

​
Options

​
Example

Create a warning notice that expires in 30 days:
If you omit --message or expiration options, the CLI prompts you interactively (with a default expiration of 30 days). After creation, the CLI displays the notice ID and a hint showing how to list notices. You’re then prompted to publish immediately—if you decline, the notice remains in draft status.

​
Finding a notice ID

When you create a notice, the command outputs the notice ID (a UUID). If you didn’t save it, use list to find it. Use --status to filter by draft, published, archived, or deleted.
The output displays a table with each notice’s ID, status, level, message, and expiration date. Copy the ID from the Notice ID column to use with other commands like get, update, publish, archive, or delete.

​
Pagination

For channels with many notices, use pagination to limit the number of notices you are seeing:
  • --offset — Number of notices to skip (default: 0)
  • --limit — Maximum notices to return (default: 20)

​
Publishing a notice

To make a draft or archived notice visible to channel users, use the publish command. Use the --force flag to skip the confirmation prompt.

​
Getting notice details

View the full details of a specific notice, including status, level, message, expiration date, and timestamps.

​
Updating a notice

Modify an existing notice’s message, level, status, or expiration. If you do not add all required information to the initial command, you will be prompted for each piece of information.

​
Archiving a notice

Archive a notice to stop showing it to users before its expiration date. Archived notices can be republished later using the publish command. Use the --force flag to skip the confirmation prompt.

​
Deleting a notice

Delete a notice to remove it from the default notice list. Deleted notices can still be viewed with --status deleted but cannot be restored.
Deleted notices cannot be restored. Consider archiving notices instead if you might need to republish them later.

​
Organization channels

For organization channels, use the --namespace or -n flag to specify the organization. You must be an owner or administrator of the organization to manage its channel notices.

​
Best practices

  • Keep messages concise: Use clear, actionable messages. Include a URL for additional details.
  • Set appropriate expiration dates: Choose expiration dates that give users enough time to see and act on the notice.
  • Use meaningful notice levels: Reserve critical for genuinely urgent issues to avoid alert fatigue.
  • Test with drafts: Create notices as drafts first, review them, and then publish when ready.
  • Archive instead of delete: Archive old notices for record-keeping rather than deleting them permanently.