Releases: nickesc/modpack-lock
Releases · nickesc/modpack-lock
modpack-lock 0.8.1
modpack-lock v0.8.0
What's Changed
- Converts
modpack.jsondependencies format to include version information by @nickesc in #33 - This update contains breaking changes to the
Jsonfileandmodpack.jsonshapes.
Full Changelog: 0.7.0...0.8.0
modpack-lock 0.7.0
What's Changed
- Migrate codebase to TypeScript by @nickesc in #32
- This release should not contain any breaking changes, but please report any issues if you encounter them in your utilizations of the library.
Full Changelog: 0.6.2...0.7.0
modpack-lock v0.6.2
modpack-lock v0.6.1
modpack-lock v0.6.0
What's Changed
- Add User-Agent headers for API calls and dependency columns in READMEs by @nickesc in #26
- Add logger class, rewrite and cleanup logging calls, and refactor generation workflow by @nickesc in #27
Full Changelog: 0.5.0...0.6.0
modpack-lock v0.5.0
What's Changed
- Adds license generation and improves prompting experience by @nickesc in #23
- Adds .gitignore writing, improves init prompts by @nickesc in #24
Full Changelog: 0.4.0...0.5.0
modpack-lock v0.4.0
Adds run command support with folder and debug options.
Lets you run scripts defined in modpack.json's scripts field from the CLI. Similar to scripts field in package.json
Features:
- run any bash script/command as defined in the modpack.json in the current or specified directory
- debug output option for troubleshooting
- pass all args and options after
--to the script - spawns the process the current shell
modpack-lock v0.3.2
Refactors the way that default values for modpack.json fields are determined, including respecting existing configurations.
modpack-lock v0.3.1
Fixes prompts so that if the user inputs a modpack name, the ID will be a slugified version of that string instead of the default string (based on the directory name).