v1.0.2: patch env var restrictions (again)

What's Changed

• patch overly strict env var names by @tomeichlersmith in #137
• warn if denv init inside denv by @tomeichlersmith in #138

Full Changelog: v1.0.1...v1.0.2

v1.0.1 : Patch Copy-able Environment Variables

While I worked on some stuff that is helpful for quicker testing and the like, the main motivation for this patch release is including a new exclusion of environment variable names so that denv can run within screen (which creates a variable that was currently passing through our sieve and then causing issues within the container).

What's Changed

• switch to using alpine images to make testing faster by @tomeichlersmith in #129
• 128 man page render by @tomeichlersmith in #130
• Auto Runner Version Update by @github-actions in #131
• Auto Runner Version Update by @github-actions in #133
• patch invalid var name when using screen by @tomeichlersmith in #134

Full Changelog: v1.0.0...v1.0.1

v1.0.0 : Stable and Ready for Use

After a lot of testing (#124) and a few more patches, I feel ready mark denv as ready for stable use. While it is certainly not perfect (issues remain), I am ready to make a promise of stability fixing denv's configuration syntax and CLI so that future users can commit to using it for a long time.

👩‍💻 Human Updates

• Various CI updates for stability and usability by @tomeichlersmith in #121
• Enable MacOS GUI Connection by @tomeichlersmith in #120

🤖 Bot Changes

• Auto Runner Version Update by @github-actions in #119
• Bump docker/build-push-action from 3 to 6 by @dependabot in #122
• Bump actions/checkout from 3 to 4 by @dependabot in #123
• Auto Man Page Update by @github-actions in #127

Full Changelog: v0.8.2...v1.0.0

v0.8.2 : require GUI-necessary env vars

In the last few commits on main, I've tweaked how the environment variables are handled and which ones are allowed in order to make the GUI connection a bit smoother. In short,

• DISPLAY is promoted to required so it is always shared (even in --clean-env)
• Environment variables starting with X are not shared to prevent confusion (e.g. about XAUTHORITY) which could be confusing for programs since the HOME directory is changing

🤖 Bot Changes

• Auto Runner Version Update by @github-actions in #115
• Auto Runner Version Update by @github-actions in #116
• Auto Man Page Update by @github-actions in #118

Full Changelog: v0.8.1...v0.8.2

v0.8.1 : patch `PATH` sharing and tab complete default

What's Changed

• restrict more *PATH variables and document bad-name regex by @tomeichlersmith in #111
  • This prevents more clashes between environment variables inside and outside the denv.
• add trailing else block to catch everything else by @tomeichlersmith in #113
  • This ensures that the bash-default filepath completion is restored for all unknown arguments

🤖 Bot Updates

• Auto Runner Version Update by @github-actions in #109
• Auto Runner Version Update by @github-actions in #112
• Auto Man Page Update by @github-actions in #114

Full Changelog: v0.8.0...v0.8.1

v0.8.0: shebang support

This is a new minor release for the shebang support feature introduced by #106 and documented in the SCRIPTING section of the manual (website copy linked). Besides this feature introduction various cleaning chores have been done to try to help the debug and info logs be more helpful (and less cluttered) as well as fix up some typos and leftovers from development.

What's Changed

• shebang support by @tomeichlersmith in #106
• disable xtrace for commands with bloated outputs by @tomeichlersmith in #108

🤖 Bot Changes 🤖

• Auto Runner Version Update by @github-actions in #101
• Bump actions/configure-pages from 4 to 5 by @dependabot in #103
• Auto Runner Version Update by @github-actions in #105
• Auto Man Page Update by @github-actions in #107

Full Changelog: v0.7.0...v0.8.0

v0.7.0 : more thorough checking and covering of pit falls

Updating denv check to help it be more usable by a wider audience and give more information to the user is a good step towards stability. More testing on non-normal systems (e.g. NixOS and clusters with multiple runners) revealed some other pit-falls that can be avoided.

💥 Breaking Change

#96 and #98 re-order the list of runners that denv checks when trying to deduce which runner to use at start-up if DENV_RUNNER is not defined. This means that on systems with multiple runners available, the runner chosen to be used by denv may change which may cause some discomfort if not breaking a setup. Both of the order changes were motivated by usability: promoting runners that are more likely to be usable for denv (in my experience). All in all, I'd recommend to define DENV_RUNNER in your host environment if you have multiple runners installed. I've added this recommendation to the manual pages as well.

What's Changed

• enter the workspace whether or not it needs creation by @tomeichlersmith in #91
• update denv check with emulation testing and workspace search by @tomeichlersmith in #96
• re-order runner deduction to prefer apptainer/singularity by @tomeichlersmith in #98

🤖 bot changes 🤖

• Auto Runner Version Update by @github-actions in #89
• Auto Runner Version Update by @github-actions in #90
• Auto Runner Version Update by @github-actions in #95
• Auto Man Page Update by @github-actions in #97
• Auto Man Page Update by @github-actions in #99
• Auto Man Page Update by @github-actions in #100

We've reached 💯 PRs and Issues 🎉

Full Changelog: v0.6.0...v0.7.0

v0.6.0 : `check` and `config network` command additions

The addition of a check sub-command to insure denv functionality upon installation and a config network flag to enable/disable network connection introduced two changes to the command line interface for denv which necesitates a new version. Moreover, denv check is specifically referenced in the quick-start area so it should be available for new users immediate upon installation.

What's Changed

• Auto Runner Version Update by @github-actions in #76
• Auto Man Page Update by @github-actions in #78
• 79 sub command to check if a supported runner is available by @tomeichlersmith in #82
• Auto Man Page Update by @github-actions in #83
• 81 disable network connection when running by @tomeichlersmith in #84
• Auto Man Page Update by @github-actions in #85
• Auto Man Page Update by @github-actions in #88

Full Changelog: v0.5.0...v0.6.0

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