jaimergp

Github Releases are mutable though. I can remove and reupload a new artifact with the same name. I think requiring the SHA256 or upload timestamp would be beneficial.

Yep, [this bit](https://github.com/pypa/pip/blob/7e49dca9277bf4e325b85cfb9ebe70401f194fb6/src/pip/_internal/network/session.py#L79-L105) particularly for CI detection heuristics. But that also would cover legitimate usage of CI in e.g. testing pipelines of other projects. What we want to say is...

Hm, true, I like that option too. And conda already has a headers plugin hook, [apparently](https://github.com/conda/conda/blob/6832c1853c481c37f07e28775632787364b607d9/conda/plugins/hookspec.py#L520-L574). So we "only" need to standardize some of those decisions there (e.g. the `;`...

@conda-bot check

I think it comes from the `mamba` side: https://github.com/conda/constructor/blob/7558141203ac998a873b25cb56614ccbc830d820/constructor/header.sh#L707-L710

Hm, I don't observe this in my local installation: ```bash bash-3.2$ eval "$(conda shell.bash hook)" (base) bash-3.2$ echo $CONDA_PREFIX /Users/jrodriguez/.local/conda (base) bash-3.2$ conda activate heavy (heavy) bash-3.2$ echo $CONDA_PREFIX /Users/jrodriguez/.local/conda/envs/heavy...

Can you try setting `auto_activate` to false? ``` conda config --set auto_activate false ```

PS1 being dropped is kind of expected because this var is not exported. We are looking into other ways of providing activation that would be more fitting to your use...

xref: conda-forge has RCs now https://github.com/conda-forge/python-feedstock/pull/805

That might be the only way forward, yes. But we need to take care of the timing so we merge this within the release window of whatever CLS version ships...