Allelefinder

Release Notes

Features

- Updated the package name in the GitHub Actions workflow. The placeholder 'my_package' has been replaced with the actual package name 'allelefinder'. This change ensures that the correct package is targeted during the workflow execution.

Improvements

- Added empty lines at the end of several files for better POSIX compliance. This change improves the readability and manipulation of the files, and aligns with common coding style guidelines.

Features
- Bumped version to 0.2.8. Updated the version in `allele_tools/version.py` from 0.2.7 to 0.2.8.

Fixes
- Updated `asset_path` in publish workflow. Replaced wildcard character in `asset_path` with specific file paths stored in environment variables to fix the `upload-release-asset` action.

Release Notes

Features
- Bumped version to 0.2.7. Updated the version in `allele_tools/version.py` from 0.2.6 to 0.2.7.

Refactors
- Updated Conda environment setup in GitHub Actions workflow. Changed the Conda environment name from 'my_env' to 'allelefinder_env' and removed the unnecessary 'environment-file' line.

Release Notes

Feature: Added sha256 to meta.yaml
- A sha256 placeholder has been added to the source section in the meta.yaml file for the allelefinder package. This will be used to specify the sha256 hash of the package source code.

Feature: Updated publish workflow
- The GitHub Actions workflow for publishing the package has been modified. Changes include calculating the hash of the package, uploading the hash as an artifact, updating the paths for the release assets, and removing the Conda package section, which is now handled in a separate workflow.

Feature: Added Conda package workflow
- A new GitHub Actions workflow for building and releasing the Conda package has been added. This workflow is triggered on release publication, and it builds the Conda package using the hash of the PyPI package.

Chore: Version Bump
- The version of the package has been increased to 0.2.6.

These changes improve the package building and publishing process by separating the workflows for PyPI and Conda packages, adding a sha256 hash to the package metadata, and updating the package version.

Release Notes for AlleleFinder

New Features

- **Conda package setup in GitHub Actions workflow**: Added steps to the GitHub Actions workflow to setup Conda, install Conda dependencies, update the `meta.yaml` file, build the Conda package, convert the Conda package for all platforms, and upload the Conda package using the `ANACONDA_TOKEN` secret. (Commit `54fe965`)

- **Console_scripts entry points in setup.py**: Added `console_scripts` entry points for `allele_updater`, `allele_translate_reduce`, `profile_reduce`, and `stec` scripts in the `setup.py` file. This allows the scripts to be run from the command line without the `.py` extension. (Commit `c41cf6a`)

- **Meta.yaml for AlleleFinder package**: Added a new `meta.yaml` file for the AlleleFinder package. This file includes information about the package such as its name, version, dependencies, and more. It also includes test commands and information about the package's license. (Commit `9931fbd`)

Chores

- **Bump version to 0.2.4**: Updated the version number of the AlleleFinder package from 0.2.1 to 0.2.4 in the `version.py` file. This was done after a previous downgrade of AlleleFinder to test GitHub actions. (Commit `e81baa7`)

New Features

- **Automate Asset Naming**: We've updated our GitHub Actions workflow to automate the naming of release assets. This ensures that the correct asset files are uploaded, regardless of their names. (Commit: 68a7e8b by Adam Koziol)

- **Update Version Badge**: The version badge in README.md now uses shields.io for dynamic versioning. This allows the version badge to automatically reflect the latest release version. (Commit: 6cf5bfb by Adam Koziol)