v1.4.0

What's Changed

• Simplify package search by @atteggiani in #8
• Added output to preserve the paths of the built packages by @atteggiani in #9

New Contributors

• @atteggiani made their first contribution in #8

Full Changelog: v1.3.0...v1.4.0

v1.3.0

A new option was added by @aidanheerdegen to choose whether or not the final package will be uploaded (useful for CI testing).

v1.2.0

Adding a new option to build with boa.

v1.1.0

This is the first not-beta released version. Nothing changed from v1.1-beta.1.

Option to produce the package for the host platform

When the package is not pure python, when the package contains code to be compiled, conda convert does not work.
In this case, the os and architecture of the host need to be changed to produce and upload native packages. Changes were made in this action to work also in this scenario.

Input Python version overrides the meta.yaml file

No matter the Python version found in the metadata file with the conda-build instructions, the python version given as input argument for this GitHub Action is used to build the new packages.

First beta version released

The GitHub Action does the following:

• The action checks if the meta.yaml file exists in the directory specified by the user.
• It compiles then the list of packages to the platform and Python version specified by the user.
• Finally, the action uploads all packages built to the Anaconda user or organization specified by the user, with the label specified by the user (the option auto sets the value of the label as 'main' for releases and 'dev' to prereleases).