Release 12.0.0 · spacetelescope/crds

New features

CRDS_CONTEXT environment variable, and any functions that accept a symbolic mapping name, can now be set to "latest" or "build".
Setting environment variable CRDS_CONTEXT=latest automatically sets the effective context to the latest operational context found on the CRDS Server.
For JWST, if CRDS_CONTEXT env var is not set, it will default to the BUILD context (as determined by locally installed jwst software version). For Roman and HST, it will default to LATEST (the default context, formerly known as "operational").
crds.client.api.get_build_context() checks for locally installed calibration software (which software depends on which observatory the CRDS environment is configured for) and retrieves the appropriate "build context" associated with the installed "cal_ver".
client.api.get_default_context() by default returns build context for jwst; latest context for Roman and HST. This can still be overridden by explicitly passing a value into the newly added optional arg state.

Default context "operational" is now "latest". E.g. for symbolic mapping names use --hst-latest instead of --hst-operational