> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Channel notices
export const GCell = ({children, className}) =>
{children}
;
export const GTH = ({children, className}) =>
{children}
;
export const GRow = ({children}) => {children}
;
export const GBody = ({children}) => {children}
;
export const GHead = ({children}) => {children}
;
export const GTable = ({children, className, cols}) =>
{children}
;
export const Comments = ({children}) => {
return ;
};
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`](/docs/cli-reference/anaconda-client/commands/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//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](/docs/cli-reference/anaconda-client/getting-started) version 1.15.0 or later
* Owner or administrator access to the channel
To verify your anaconda-client version:
```sh theme={null}
anaconda --version
```
To update your anaconda-client version:
```sh theme={null}
conda install --name base anaconda-client=1.15.0
```
## 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.
```sh theme={null}
anaconda channel notice create --message "" --level --expires-after
```
Replace \ with your channel name (your username or organization name).
Replace \ with your notice text (max 600 characters).
Replace \ with the severity level for your message.
Replace \ with the number of days until the notice expires.
### Options
Option
Description
`--message `
The notice text to display (max 600 characters). Can include a URL.
`--level `
Notice severity: `info` (default) for general announcements, `warning` for deprecations or breaking changes, `critical` for security issues or urgent actions
`--expires-at `
Expiration date in ISO 8601 format (for example, `2026-12-31T00:00:00Z`)
`--expires-after `
Number of days until expiration (minimum 1, alternative to `--expires-at`)
`-n, --namespace `
Channel owner (user or organization). Alternative to the positional `` argument.
### Example
Create a warning notice that expires in 30 days:
```sh theme={null}
anaconda channel notice create my-channel --message "Version 2.0 removes deprecated API. Migrate by Jan 2027." --level warning --expires-after 30
```
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`.
```sh Command theme={null}
anaconda channel notice list --status
```
```sh Example theme={null}
anaconda channel notice list my-channel --status published
```
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)
```sh theme={null}
anaconda channel notice list my-channel --offset 5 --limit 10
```
## 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.
```sh Command theme={null}
anaconda channel notice publish [--force]
```
```sh Example theme={null}
anaconda channel notice publish my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force
```
## Getting notice details
View the full details of a specific notice, including status, level, message, expiration date, and timestamps.
```sh Command theme={null}
anaconda channel notice get
```
```sh Example theme={null}
anaconda channel notice get my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3
```
## 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.
```sh Command theme={null}
anaconda channel notice update --message --level --expires-after
```
```sh Example theme={null}
anaconda channel notice update my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --message "Updated migration deadline: Feb 2027"
```
## 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.
```sh Command theme={null}
anaconda channel notice archive [--force]
```
```sh Example theme={null}
anaconda channel notice archive my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force
```
## 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.
```sh Command theme={null}
anaconda channel notice delete [--force]
```
```sh Example theme={null}
anaconda channel notice delete my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force
```
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.
```sh Command theme={null}
anaconda channel notice --namespace
```
```sh Example theme={null}
anaconda channel notice list --namespace my-org --status published
```
## 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.