Releases: conda-forge/conda-smithy
v3.15.0
Added:
- Conda smithy will now detect if a recipe uses
compiler('cuda')
and set theCF_CUDA_ENABLED
environment variable toTrue
if
so. This can for example be useful to distinguish different options
for builds with or without GPUs inconda_build_config.yaml
. - Introduce utility function to facilitate the use case of running conda smithy
commands from any sub-directory in the git repo checkout of a feedstock.
Fixed:
- Fixed typo in GitHub Actions template, where
DOCKERIMAGE
was wrongly specified in the matrix configuration. The CI step and its corresponding script expectDOCKER_IMAGE
.
Authors:
- Isuru Fernando
- Jaime Rodríguez-Guerra
- H. Vetinari
- Nehal J Wani
v3.14.3
v3.14.2
Authors:
- Isuru Fernando
v3.14.1
v3.14.0
Added:
test
option inconda-forge.yml
can now be used to configure testing.
By default testing is done for all platforms.native_and_emulated
value
will do testing only if native or if there is an emulator.native
value
will do testing only if native.
Deprecated:
test_on_native_only
is deprecated. This is mapped to
test: native_and_emulated
.
Fixed:
- Always pull a new version of the image used in a build
- Add workaround for Travis CI network issues (courtesy of @pkgw)
Authors:
- Isuru Fernando
- Marcel Bargull
- Matthew W. Thompson
v3.13.0
Added:
-
Added the ability to store conda build artifacts using the Github Actions provider. To enable, set
github_actions: {store_build_artifacts: true}
in conda-forge.yml. -
It is possible to set the lifetime of the Github Actions artifacts by setting the the
github_actions: {artifact_retention_days: 14}
setting in conda-forge.yml to the desired value. The default is 14 days. -
Support for ppc64le on drone CI has been added
-
Added support for registering at a custom drone server by adding --drone-endpoint cli argument
-
Added explicit check to not upload packages on PR builds.
-
Added key
github:tooling_branch_name
toconda-forge.yml
to enable
setting the default branch for tooling repos. -
The linter will now warn if allowed
pyXY
selectors are used (e.g.py27
,py34
,py35
,py36
). For other versions (e.g. Python 3.8 would bepy38
), these selectors are silently ignored byconda-build
, so the linter will throw an error to prevent situations that might be tricky to debug. We recommend usingpy
and integer comparison instead. Note thatpy2k
andpy3k
are still allowed. -
Added support for self-hosted github actions runners
In conda-forge.yml, add
github_actions: self_hosted: true
to
enable self-hosted github actions runner. Note that self-hosted
runners are currently configured to run only on push events
and pull requests will not be built. -
Allow multiple providers per platform
In conda-forge.yml, add
provider: <platform>: ['ci_1', 'ci_2']
to configure multiple providers per platform.
Changed:
- Uploads are now allowed when building with
mambabuild
! - Azure build artifacts are now zipped before being uploaded, with some cache directories and the conda build/host/test environments removed, to make user download smaller and faster.
- A separate Azure build artifact, including only the conda build/host/test environments, is additionally created for failed builds.
- Azure artifact names are now only shortened (uniquely) when necessary to keep the name below 80 characters.
- Updated CircleCI xcode version to 13.0.0 to prevent failures.
- The conda-smithy git repo now uses
main
as the default branch. - conda mambabuild is now the default build mode. To opt out of this change set
build_with_mambabuild
to false in yourconda-forge.yml
. - Bump Windows
base
environment Python version to 3.9 - Support using
build-locally.py
natively onosx-arm64
.
Fixed:
- Azure artifact names are now unique when a job needs to be restarted (#1430).
- Azure artifact uploads for failed builds that failed because of broken symbolic links have now been fixed.
- Test suite now runs correctly on pyyaml 6
- Remove the miniforge installation before building with
./build-locally.py
on MacOS so that
./build-locally.py
can be run more than once without an error regarding an exisiting miniforge installation.
Authors:
- Isuru Fernando
- Matthew R. Becker
- Jaime Rodríguez-Guerra
- Uwe L. Korn
- Ryan Volz
- John Kirkham
- Wolf Vollprecht
- Marius van Niekerk
- Matthias Diener
v3.12
Authors:
- Marius van Niekerk
v3.11.0
Added:
- The maximum number of parallel jobs a feedstock can run at once will be limited
to50
. This will ensure that all projects have a fair access to CI resources
without job-hungry feedstocks hogging the build queue.
Fixed:
- Add --suppress-variables flag to conda-build command in Windows template
Authors:
- Jaime Rodríguez-Guerra
- Billy K. Poon
v3.10.3
v3.10.2
Added:
- Add a "--feedstock_config" option to the regenerate/rerender, update-anaconda-token, azure-buildid subcommands for providing an alternative path to the feedstock configuration file (normally "conda-forge.yml"). This allows different names or to put the configuration outside the feedstock root.
- Linter will now check for duplicates of conda packages using pypi name
- Validate the value of
noarch
. (Should bepython
orgeneric
.)
Changed:
- Use
ubuntu-latest
instead ofubuntu-16
in the Azure pipeline template.
Fixed:
short_config_name
is used at azure pipelines artifact publishing step.- Duplicate feedstocks with only '-' vs '_' difference is now correctly checked.
- correctly detect use of
test/script
in outputs
Authors:
- Isuru Fernando
- Uwe L. Korn
- Ryan Volz
- Duncan Macleod
- fhoehle
- Ben Mares