- Added --locked flag for the install subcommand (#119)
- Added private field to package manifest (#9)(#76)
- Improved lockfile generation lockfiles will change (#130)
- Improved package installation to download packages in parallel (#133)
- Support for directly providing token to
wally login(#105) - Fixed dev dependency resolution (#75)
- Fixed multi-realm dependency resolution (#80)
- Fixed dev dependency link generation (#131)
- Reclaiming of scopes is now disallowed (#102)
- Improved manifest generation on
wally init(#84) - Added S3 storage backend option (#90)
- Frontend improvements (#109)(#110)(#112)
- Publishing packages >2MB now bails at the cli (#121)
- Other small misc changes related to repo upkeep
- Support for dev dependencies ([#63][63])
- Clarified upgrade response for outdated cli clients
- Clarified feedback on failure to resolve package
- Fixed Windows generating invalid zip archives. (#15)
- Support for registry fallback chains (#35)
- Generate cross realm package links (#38)
- Support include/exclude lists in manifest (#44)
- Backend API for package metadata and search (#46)
- Arch users can now use vendored-libgit2 btw (#52)
- Frontend can search packages and display package info (#55)
- Minimum Wally version enforcement by registry (#57)
- First iteration of wally frontend. (#32)
- Fixed package links between sibling packages. (#17)
- Fixed invalid package names being generated from
wally init. (#19) - Added public authentication strategy via GitHub. (#20)
- Improved readability of package name errors. (#23)
- Renames rojo projects when the name given in
default.project.jsondoesn't match the name given inwally.toml. (#25) - More efficient use of reqwest. (#27)
- Enforce a max length on package names. (#28)
- Fixed
wally installfailing due to a "file not found" error. (#11)
- Initial release