v0.7.1

What's Changed

• Fixed the issue when DEM couldn't find the existing repositories. by @janosmurai in #208
• README updated. by @janosmurai in #209
• Default registry config updated. by @janosmurai in #219
• Registry management commands have been updated to handle namespaces. by @janosmurai in #220
• 🔨 [tuning] Added continuous deployment workflow for PyPI by @hitblast in #222

New Contributors

• @hitblast made their first contribution in #222

Full Changelog: v0.7.0...v0.7.1

v0.7.0

When obtaining the available repositories from a DockerHub namespace, the Container
Engine's search functionality had been used. This search function had changed, so
filtering for the namespace didn't work anymore.
The new solution is to use the DockerHub's API directly.

To be able to manage the registries properly the config file got extended so
the registry config has a new field called 'namespace'. This breaks backward
compatibility.

Fixes

• Communication with DockerHub

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

v0.6.0

The goal of this release was to create a new functionality for the run command:
The user can assign tasks for a Dev Env. These tasks can be executed with the dem run command.

New features

• The set-default command implemented.
• The add-task command implemented.
• The del-task command implemented.
• Dev Env's assigned tasks are printed with the info command.
• New functionality for the run command: DEM runs the selected one from the Dev Env's assigned tasks
• Output of the list command improved: the first column aligned to the left, the others aligned to the middle.

Fixes

• DEM now presents a warning if the user tries to uninstall an installed Dev Env that requires an unavailable tool image.

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

v0.5.0

New features

• The dem list and dem info commands are redesigned.
• The list-tools command is implemented.
• The dem load command is renamed to dem import.

Documentation

• Documentation is updated with UI/UX improvements and the content is revised.

Full Changelog: v0.4.0...v0.5.0

v0.4.0

New features

• Dev Env Settings Window has been created.

Fixes

• Missing uninstall call added to the clone command.
• Autocompletion error fixed.
• Unhandled exception fixed when a not existing Dev Env name is supplied for the info command.
• Error message presented when the user tries to create an empty Dev Env.

Documentation

• Docs and README updated.

Full Changelog: v0.3.1...v0.4.0

Bugfix

Release notes

Bug fixes

• The user was able to install Dev Envs with missing images
• The output of the export command was invalid.
• The dem cp command also copied the installation status.
• The `dem create˙ command checked the image availability, but it shouldn't have.
• The dem create command was able to overwrite an already installed Dev Env.
• Missing exception handling added.

Improvements

• Updates in the help texts, the README, and the docs.

New workflow

Release notes

New features

• Introducing the new workflow: First, the user needs to add the Dev Env descriptor to their local catalog. This can be achieved by cloning a catalog Dev Env, initializing a project, importing the Dev Env descriptor shared by someone, or creating a new one. As a next step, the user can further tune the Dev Env. Finally, the Dev Env installation can be done with a single command.
• A Dev Env's required tool images can be removed with the uninstall command. The local Dev Env descriptor can be deleted from the local catalog with the delete command.
• CLI autocomplete added.
• A single tool in a Dev Env can be modified directly with the modify command without opening the Dev Env settings panel.
• Timeout value for the HTTP requests is coming from the config file.
• A Dev Env can be assigned to a project with the assign command.
• If a project already has a Dev Env assigned, the assigned Dev Env can be initialized with the `init˙ command.
• The clone command now can be used to create a local clone of a catalog Dev Env descriptor. The original functionality, creating a local copy of a local Dev Env, is now available under the cp command.
• Host management added.

Documentation

• README updated.
• Contribution guide updated.
• PR template updated.
• Documentation for the new workflow added.

Disclaimer

After upgrading your DEM from v0.2.X or earlier, the dem install command must be issued for all the locally available Dev Envs. The command will simply set the installed state of these Dev Envs to true.

Documentation updated

Release notes

Documentation

• Issue and PR templates added.
• Hacktoberfest-specific and other minor improvements in the README.
• Contribution guide added.
• Code of Conduct added.
• Codeowners file added.

Registry and catalog management

Release notes

New features

• Organization changed to catalog
• Support of 3rd party registries and catalogs
• Catalog and registry management
• Offline usage
• New commands for directly sharing Dev Envs: dem export and dem load
• New commands to manage the Dev Env Catalogs: dem list-cat, dem add-cat, `dem del-cat˙
• New commands to manage the Registries: dem list-reg, dem add-reg, `dem del-reg˙
• New experimental command to run a docker container in the context of a Dev Env: dem run

Bug fixes

• dem modify saving and image pulling issues
• dem run command handling
• Typo fixes

Documentation

• Dev Env, Tool Image, Registry, Dev Env Catalog, Dev Platform terminology clarified
• Documentation added for the new commands

Bugfix and UX improvements.

Release notes

UI/UX improvements

• Redesigned TUI panels for the create and modify commands.
• More feedback for the user about background processes

Bug fixes

• The DEM handles the docker engine's problems.
• The DEM handles the invalid dev_env.json.
• Typos fixed in the help texts.
• Single source for the version number.

Documentation

• Improvements of the Introduction page.
• Minor design changes.