v1.1.0

What's Changed

• Conda Lock Upgrades - Part 2 by @jbouder in #49

Full Changelog: v1.0.5...v1.1.0

v1.0.5

What's Changed

• Conda Lock Upgrades - Part 1 by @jbouder in #47

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• fix: include virtual packages during cross platform vendoring by @RR-USAF in #42
• Fix Dependency Issues by @jbouder in #45
• Release: 1.0.4 by @jbouder in #46

New Contributors

• @RR-USAF made their first contribution in #42
• @jbouder made their first contribution in #45

Full Changelog: v1.0.3...v1.0.4

v1.0.3

• update pypi release workfow
• increment version number in the code

v1.0.2

• fixes relative path issue in repodata.json

v1.0.1

Previously the --ironbank-gen flag would output the generated manifest to stdout. This was causing issues when capturing standard output for automated workflows, because informational messages would also be captured.

This change makes the manifest output to a file called ib_manifest.yaml in the current working directory instead.

v1.0.0

• Remove meta-manifest intermediary step in favor of conda-lock's new 1.0.x API and lockfile format
• Make vendor the primary command
• Add flag for different solvers: conda, mamba, micromamba based on conda-lock's new 1.0.x API for solve_specs_for_arch
• Add a --dry-run option to generate formatted JSON of conda-lock's solved FetchActions object. This replaces the old meta-manifest generation intermediary step and can be piped to other SBOM tools that accept JSON.
• IronBank hardening_manifest.yaml resources formatted text output, using filtered + merged FETCH actions in conda-lock's FetchActions object
• click cli integration tests
• update test fixtures to use conda-lock's FetchActions, LockSpecification, and VersionedDependency objects
• Update GitHub Actions to include dependencies for integration tests

New Usage for version 1.0.0:

# use conda as the solver for linux-64
conda-vendor vendor --file environment.yaml --solver conda --platform linux-64

# use mamba as the solver for osx-64
conda-vendor vendor --file environment.yaml --solver mamba --platform osx-64

# use micromamba as the solver for the host platform
conda-vendor vendor --file environment.yaml --solver micromamba

# dry-run outputs formatted JSON 
conda-vendor vendor --file environment.yaml --solver mamba --platform linux-64 --dry-run True

Screenshots:

Conda-vendor Improved UX:

repodata.json hotfix progress bar and package download progress bar:

Dry-Run formatted JSON output:

ironbank-gen subcommand (returns formatted text that can be copied into Ironbank's hardening manifest):

Example IronBank Workflow:

1) Generate the vendored channel and output the IronBank Hardening Manifest resources to stdout:

conda-vendor vendor --file my-environment.yaml --solver micromamba --platform linux-64 --ironbank-gen True

2) Copy the output resources block to your IronBank hardening_manifest.yaml:

- url: https://conda.anaconda.org/conda-forge/linux-64/micromamba-0.22.0-0.tar.bz2
  filename: micromamba-0.22.0-0.tar.bz2
  validation:
    type: sha256
    value: f8d6d9ab832401f8f32e161d5043b28fd7f043d8f0829ab5388f6e4a4256524a
- url: https://conda.anaconda.org/conda-forge/linux-64/_libgcc_mutex-0.1-conda_forge.tar.bz2
  filename: _libgcc_mutex-0.1-conda_forge.tar.bz2
  validation:
    type: sha256
    value: fe51de6107f9edc7aa4f786a70f4a883943bc9d39b3bb7307c04c41410990726
- url: https://conda.anaconda.org/conda-forge/linux-64/libstdcxx-ng-11.2.0-he4da1e4_15.tar.bz2
  filename: libstdcxx-ng-11.2.0-he4da1e4_15.tar.bz2
  validation:
    type: sha256
    value: cc84f71bb9dbecde453a25ba8c5aefc9773da5d619633c103eb8bac1ab4afda0

3) Copy over your patched repodata.json files from your vendored channel to the appropriate directory in your IronBank Project

v0.1.15

• change dependency from pyyaml to ruamel. Code will now throw an error when passed yaml files that have duplicate keys.

v0.1.14

• Fixes bug where pip wasn't actually being added as dependency when python was present

v0.1.13

• Fix bug where combine function wasn't writing out yaml