0.11.0

Added "FlattenModules" configuration option to control whether or not Prism should flatten a module's directory
structure when installing, i.e. preserve the versioned directory PowerShell installs a module to by default.

0.10.0

Changed

Reducing directory depth for all modules not just internal, private, nested modules.

Fixed

Fixed: if the latest non-prerelease version of a module matches the wildcard in the "prism.json" file and the latest
version is a prerelease version and the AllowPrerelease flag is true in the "prism.json" file, Prism fails to pin
to the prerelease version.

0.9.0

Turns out, the 10 directory nesting limit for nested modules is a scope stack limit, not a directory limit. This version
of Prism now installs nested modules into a "Modules" directory instead of directly in the module directory. You can
preserve the old behavior and install modules directly in the module directory by setting the "PSModulesDirectoryName"
configuration property in the prism.json file to ..

0.8.1

Fixed: Prism fails to install new versions of nested modules if old versions are installed.

0.8.0

Nesting Improvements

PowerShell has a 10 directory nesting limit for nested modules.In order to prvent this nesting limit, Prism now:

• installs nested modules directly in the module directory instead of a "PSModules" directory.
• moves modules out of the versioned directory where PowerShell installs them by default (unless a module depends on
  multiple versions of the same module).

Prism determines if it is installing nested modules by looking for a .psd1 or .psm1 file in the same directory as the
prism.json file.

Changes

• The "PSModulesDirectoryName" configuration option can no longer be a path.
• The prism install command now only returns objects for modules that were actually installed.
• The prism update command now only returns objects for modules whose version changed/updated.
• Prism now saves modules to the lock file in alphabetical order.
• The prism update command now shows the previous version number a module was pinned to.
• The prism update command no longer changes the repository location a module is locked to. Previously, if a module
  was found in multiple repositories, the lock file could sometimes change the repository location.

0.7.0

Added the ability to install or update a subset of the modules listed in the prism.json file. Specify the subset of modules by passing it to the Name parameter when invoking prism.

0.6.1

Fixed: Prism fails to find modules that only have prerelease versions.

0.6.0

Adding an init.ps1 script that can be used to install Prism's dependencies (PackageManagement and PowerShellGet modules) and install Prism.

0.6.0-alpha1

• Adding an init.ps1 script that can be used to bootstrap Prism pre-requisites on a server. Currently, it installs PackageManagement and PowerShellGet modules into the current user's scope.

0.5.2

Adding support for PackageManagement 1.4.8.1.