Releases: conda-forge/conda-smithy
Releases · conda-forge/conda-smithy
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
v3.10.1
v3.10.0
Added:
- Added
clone_depth
parameter for use in conda-forge.yml that sets the feedstock git clone depth for all providers (except CircleCI). By default (clone_depth: none
), current behavior is maintained by using the provider's default checkout/clone settings. A full clone with no depth limit can be specified by settingclone_depth: 0
. - Log groups support for GitHub Actions
- Added support for Github Actions as a CI provider. Provider name to use in conda-forge.yml
isgithub_actions
. Note that Github Actions cannot be enabled as a CI provider for conda-forge
github organization to prevent a denial of service for other infrastructure. - Add instructions to feedstock README template for configuring strict channel priority.
Changed:
- The
ci-skeleton
command now creates a default conda-forge.yml that setsclone_depth: 0
for full depth clones on all providers. This default supports expected behavior when usingGIT_DESCRIBE_*
to set version and build numbers in the recipe by ensuring that tags are present. This effectively changes the default clone behavior for the Github Action and Travis providers, as all other providers do a full clone by default.
Fixed:
- Prevent duplicated log group tags when
set -x
is enabled. - Fix run_osx_build not failing early on setup error.
- Fix too long filenames for build done canary files.
Authors:
- Isuru Fernando
- Jaime Rodríguez-Guerra
- Ryan Volz
- Marcel Bargull
- Philippe Blain
- Matthew R. Becker
- Marcel Bargull
v3.9.0
Added:
- Enabled multiple entries for
key_add
operations. - Define Bash functions
startgroup()
andendgroup()
that provide a
provider-agnostic way to group or fold log lines for quicker visual inspection.
In principle, this only affects Linux and MacOS, since Windows pipelines
use CI native steps. So far, only Azure and Travis support this. In the other
providers a fallbackecho "<group name>"
statement is supplied. - Support
os_version
inconda-forge.yml
- Add use_local option to use the migrator from the feedstock
Changed:
- To cross compile for
win-32
fromwin-64
, usingtarget_platform
is no longer supported. Usebuild_platform: win_32: win64
inconda-forge.yml
. run_osx_build.sh
had hardcoded handlers for Travis log folding. These have
been replaced with the now equivalent Bash functions.- A lower bound on python version for noarch python is now required
Fixed:
- Fix "File name too long" error for many zip keys
Replace config filenames by their short versions if filesystem limits
are approached. - Fix running
./build-locally.py --debug
with cross-compilation - Fixed dead conda-docs link to the
build/number
explanation in the README template. - Fixed rendering error where the recipe's
conda_build_config.yaml
is
applied again, removing some variants. - Fixed list formatting in the README.
- migration_ts and migrator_ts were both used in conda-smithy and migration_ts was removed in favour of migrator_ts
Authors:
- Isuru Fernando
- Matthew R. Becker
- Jaime Rodríguez-Guerra
- Chris Burr
- Leo Fang
- Marcel Bargull
- Wolf Vollprecht
- Hugo Slepicka
- Bastian Zimmermann
v3.8.6
Changed:
- Run docker builds using
delegated
volume mounts.
Fixed:
- All keys zipped with
docker_image
are now handled properly. - Changed CI configuration to not run tests on
push
events to branches that
are notmaster
. - CI runs on PRs from forks now.
#
is not a valid comment symbol on Windows and using it as part of a pipeline Batch step will cause a (harmless) error in the logs. It has been replaced by::
instead.
Security:
- Use latest
conda-incubator/setup-miniconda
version to circumvent the GH Actions deprecations on Nov 16th
Authors:
- Isuru Fernando
- Matthew R Becker
- Matthew R. Becker
- Uwe L. Korn
- John Kirkham
- Jaime Rodríguez-Guerra
v3.8.5
Changed:
- Moved CI to GitHub actions and removed travis-ci
- Use the shorter build ID instead of job ID to name Azure artifacts when they are stored. This helps prevent the artifact name from being too long, which would result in being unable to download it.
- Replaced travis-ci status badge w/ GitHub actions one.
Fixed:
- Faulty
migrator_ts
type check prevented manual migrations from happening (those that are not yet merged toconda-forge-pinning
). - Previous release accidentally included a commit that made noarch: python
recipes without a lower bound error. This was changed to a hint
Authors:
- Isuru Fernando
- Matthew R. Becker
- Ryan Volz
- Marius van Niekerk
- Jaime Rodríguez-Guerra