Skip to content

v0.0.28

Choose a tag to compare

@adamkoziol adamkoziol released this 02 Sep 14:27
· 5 commits to main since this release

v0.0.28

This patch release fixes local Conda channel indexing during post-build package validation.

Fixed

  • Fixed the post-build installation test failing because the conda-index command was unavailable in the build environment.
  • Added conda-index as an explicitly pinned build-tool dependency.
  • Updated local channel indexing to use the documented Python module entry point.
  • Ensured that the newly built AzureBatch package is added to the local channel metadata before installation testing.

Changed

The automated release environment now installs:

Python 3.12
conda-build 25.1.1
conda-index 0.12.1
anaconda-client 1.14.1

Local channel metadata is now generated using:

python -m conda_index <local-channel-root>

The workflow continues to derive the local channel root from the generated package path.

For a generated package such as:

/usr/share/miniconda/envs/azure_batch_build/conda-bld/noarch/azure_batch-0.0.28-py_0.conda

the local channel root is:

/usr/share/miniconda/envs/azure_batch_build/conda-bld

and the channel URL is:

file:///usr/share/miniconda/envs/azure_batch_build/conda-bld

Validation

The release workflow now performs the following post-build checks:

  1. Confirms that the expected .conda package exists.
  2. Displays the package path and SHA-256 checksum.
  3. Determines the local package directory and channel root.
  4. Displays available package and channel metadata files.
  5. Regenerates local channel metadata using conda-index.
  6. Confirms that the requested AzureBatch version is visible through conda search.
  7. Creates a clean Python 3.12 test environment.
  8. Installs the locally built package with full dependency resolution.
  9. Confirms that the azure_batch module can be imported.
  10. Runs AzureBatch -h.
  11. Displays the installed AzureBatch package record.

Channel configuration

The post-build installation test uses the following channel order:

explicit local build channel
conda-forge
bioconda
olcbioinformatics

The locally built AzureBatch package is selected from the explicit file channel, while its runtime dependencies are resolved from the configured remote channels.

Network resilience

The workflow retains timeout and retry handling for transient failures involving:

  • Conda build-tool installation
  • recipe rendering
  • package output-path calculation
  • package building and recipe tests
  • dependency resolution
  • local package installation
  • source archive downloads
  • package publication

Conda index caches are cleared between applicable retry attempts.

Test status

The complete AzureBatch source test suite passes using Python 3.12:

43 passed

The Conda recipe also validates:

  • package dependency resolution
  • wheel generation
  • Conda package creation
  • package installation
  • Python module imports
  • command-line help
  • packaged unit tests

Compatibility

  • No AzureBatch API changes are included in this release.
  • No Azure Batch pool, job, or task behavior is changed.
  • No Azure Storage runtime behavior is changed.
  • No deployment configuration changes are required.
  • Existing AzureBatch workflows remain compatible.
  • The Conda package continues to support Python 3.12 and Python 3.13.
  • Automated package builds and installation tests use Python 3.12.

Upgrade notes

No application configuration changes are required when upgrading from v0.0.27.

This release supersedes v0.0.27 for automated Conda publication. Version 0.0.27 included explicit local-channel testing, but the build environment did not include the separate conda-index package required to regenerate that channel's metadata.