v0.5.0: Align `podman` experience

A lot of work has been done on expanding the testing, but the main feature that has been included here is removing the issue with podman that kept the user as root within the denv.

What's Changed

• Auto Man Page Update by @github-actions in #55
• align podman experience with other runners by @tomeichlersmith in #56
• remove symlink of denv to backslash by @tomeichlersmith in #58
• expand manual into separate pages by @tomeichlersmith in #59
• Auto Man Page Update by @github-actions in #60
• cleanup after podman fix by @tomeichlersmith in #61
• don't set the HOME environment variable for singularity/apptainer by @tomeichlersmith in #62
• try to create prefix if it doesn't exist as a directory yet by @tomeichlersmith in #63
• Bump actions/upload-pages-artifact from 2 to 3 by @dependabot in #65
• Bump actions/deploy-pages from 3 to 4 by @dependabot in #64
• Manual install singularity from deb by @tomeichlersmith in #66
• add first set of notes on vm development by @tomeichlersmith in #68
• test support for singularity ce and document by @tomeichlersmith in #69
• Auto Runner Version Update by @github-actions in #70
• switch to bats for testing by @tomeichlersmith in #74
• Auto Man Page Update by @github-actions in #75

Full Changelog: v0.4.1...v0.5.0

v0.4.1 : `--clean-env` flag for `denv init`

This is just a patch release since it doesn't break backwards compatibility. I just added a more understandable flag that disables copying all host environment variables into the denv and updated the manual to reflect this change.

What's Changed

• Auto Man Page Update by @github-actions in #54

Full Changelog: v0.4.0...v0.4.1

v0.4.0 : enhance configuration of environment variables

While there are some house-keeping PRs, the main feature improvement that triggered this release is #51 introducing a CLI for allowing the user to decide which environment variables are copied into the denv when launched. This supports the full range from all possible variables (past behavior) to only the necessary variables and any selection in-between.

What's Changed

• Bump actions/configure-pages from 3 to 4 by @dependabot in #50
• Bump actions/deploy-pages from 2 to 3 by @dependabot in #49
• enhance configuration of environment variables by @tomeichlersmith in #51
• Auto Man Page Update by @github-actions in #52

Full Changelog: v0.3.0...v0.4.0

v0.3.0 : non-interactive running of local installs

Besides some aesthetic updates, the main motivation for this release is using sh -lc to run the command within the denv. This gives users access to some files within the denv image as well as the .profile file in the workspace where they can update environment variables before any command is run within the denv. This means we could, for example, install programs to ~/.local within the denv and then run those programs interactively (denv...program) or non-interactively (denv program).

What's Changed

• revert directory-based mounting of entrypoint by @tomeichlersmith in #43
• use full path to PWD for working directory by @tomeichlersmith in #45
• use sh -lc to run the command in denv by @tomeichlersmith in #46

Full Changelog: v0.2.2...v0.3.0

v0.2.2 : more patches after a few weeks of testing

The full list of changes are below as usual, but I want to highlight a few patches that alter the inner-workings of denv.

• #35 updates how the workspace directory is deduced in order to avoid symlinks. This helps keep the denv stable no matter how a user gets to the workspace.
• #36 implemented a basic method for supporting unpacked images on apptainer/singularity runners. These unpacked images are not supported by docker/podman #37
• Thanks to @tamasgal for giving denv a try on MacOS - we were able to find and patch a few issues with the install script since MacOS's programs (like cp, install, and ln) do not have identical flags as the GNU versions and remove the use of realpath in denv which is not installed by default in MacOS.
  • Note: I tried testing denv in GitHub actions on MacOS, but it was failing due to a permissions issue. I do not currently have access to a MacOS on which I could check if this is an issue with how I've configured the GitHub action or if its an issue with denv so I'm leaving that test commented-out right now.

What's Changed

• set version script by @tomeichlersmith in #33
• use pwd -P instead of $PWD to avoid symlinks by @tomeichlersmith in #35
• first draft of supporting unpacked images on cvmfs by @tomeichlersmith in #36
• Auto Man Page Update by @github-actions in #38
• Bump actions/checkout from 3 to 4 by @dependabot in #41
• support macos installation in zsh by @tomeichlersmith and @tamasgal in #40
• Auto Man Page Update by @github-actions in #42

Full Changelog: v0.2.1...v0.2.2

v0.2.1 - patch prompt for apptainer/singularity runners

This looks like a lot of changes but besides #23 it is mostly doc updates and fixing up (and testing) the man-gen github action which broke when I put in a branch protection rule on main.

What's Changed

• need to unset PROMPT_COMMAND for either singularit or apptainer by @tomeichlersmith in #23
• Bump actions/upload-pages-artifact from 1 to 2 by @dependabot in #24
• update man page updater to create a PR by @tomeichlersmith in #25
• make github action that generates manual work by @tomeichlersmith in #27
• Auto Man Page Update by @github-actions in #29
• Docs update by @tomeichlersmith in #30
• Auto Man Page Update by @github-actions in #31

New Contributors

• @dependabot made their first contribution in #24
• @github-actions made their first contribution in #29

Full Changelog: v0.2.0...v0.2.1

v0.2.0 : Minor Improvements and Patches

Besides a whole pile of documentation, the minor feature improvements are related to network interaction so users can access the host network from within a denv. More administrative things were added as well like shellcheckrc, code of conduct, contributing, issue, and pr templates.

Breaking Changes

#15 moved the denv_name parameter into the .denv/config file and so users who initialized a denv with v0.1.0 will not be able to run that denv with v0.2.0. There are a few ways around this:

1. Add a denv_name=<name> line to the .denv/config file.
2. Delete the denv rm -r .denv and re-initialize with the newer denv version.

What's Changed

• Check for existence of destination dir in install script by @omar-moreno in #14
• 12 setting denv name by @tomeichlersmith in #15
• 16 remove set denv runner from config by @tomeichlersmith in #17
• 11 add shellcheckrc by @tomeichlersmith in #18
• documents to write by @tomeichlersmith in #20
• docker/podman requires runtime flag to connect network by @tomeichlersmith in #21

New Contributors

• @omar-moreno made their first contribution in #14
• @tomeichlersmith made their first contribution in #15

Full Changelog: v0.1.0...v0.2.0

v0.1.0: Initial Functional Release

The development leading up to this point was under a v0.0.0 tag and kept the GitHub repository private (alpha-stage). Now that the four major runners are functional¹ I feel it is time to make the GitHub public and enter a beta-stage of development. Major release v1.0.0 will occur to signal stability of denv.

Full Changelog: https://github.com/tomeichlersmith/denv/commits/v0.1.0

1. podman is "functional" in the sense that I am leaving the in-container user as the in-container root which is mapped to the user which executed podman. I would like to not do this and unify the experience of using podman compared to the other runners, but I am not as familiar with podman at this time. #9 ↩