2.35.0

Added

• Snakemake
  • Remote register support
  • download field for file inputs
  • config field for file inputs
  • Blanket support for parameters of any type via the SnakemakeParameter class
  • Support for generating a latch_metadata directory from a config.yaml with latch generate-metadata
  • Support for default values for parameters

Changed

• Snakemake
  • JIT register step no longer downloads input files by default
  • latch_metadata should now be a module (directory containing an __init__.py file), as opposed to just being a file

Latch 2.19.4

Enhancements/Bug Fixes

• Conda template registration issue and run in correct environment issue
• Tasks stuck initializing on nodes that ran multiple tasks before

Latch 2.19.2

Dependencies

• Upgrade lytekit to 0.14.10

Latch 2.15.1

New Features

• Verified MAFFT alignment workflow stub

Enhancements/Bug Fixes

• Parameter flow forks should preserve the order of branches
• Custom tasks with less than 32 cores receive correct toleration

Latch 2.14.1

New Features

• SampleSheet metadata to LatchParameter -- allows for importing samples from Registry

Enhancements/Bug Fixes

• latch commands which require authentication prompt user for token when no browser is present on machine

Latch 2.13.5

Enhancements/Bug Fixes

• latch register ssh-keygen bug when .latch folder does not exist

Dependencies

• lytekit upgraded to version 0.14.9

Latch 2.13.3

New Features

• latch init: Docker in Docker template workflow
• latch init: Docker base image
• Small, medium, and large tasks use the Sysbox runtime to run Docker and other system software within task containers

Enhancements/Bug Fixes

• Internal state file should be automatically created when running latch register and latch develop

Latch 2.13.1

Latch 2.13.1

New Features

• The latch dockerfile command which auto-generates a Dockerfile from files in the workflow directory.
• The latch init command can use base images with hardware acceleration using the --cuda and the --opencl flags
• The latch init command does not populate the workflow directory with a Dockerfile by default
• The latch init command will populate the workflow directory with a Dockerfile if passed --dockerfile
• The latch register and latch develop commands auto-generate a dockerfile from files in the workflow directory if no Dockerfile is present
• Documentation for the auto-generated Dockerfile feature

Enhancements/Bug Fixes

• Quickstart tutorial is written factually
• Getting started docs are written factually
• Add latch/latch_cli/services/init/common to pypi release

Latch 2.12.1

Enhancements/Bug Fixes

• latch develop documentation updates
• latch develop throws error if user does not have rsync installed
• pip install latch installs the watchfiles package for latch develop

Latch 2.12.0

Enhancements/Bug Fixes

• latch develop drops users directly into a shell in their docker environment. Local changes in the workflow directory and any subdirectories are automatically synced into the environment. Deleted local files are not deleted in the environment. However, any additions or modifications to files and directories are propagated.