Releases: koordinates/kart
v0.4.1
Overview
0.4.1 fixes some packaging issues in the 0.4.0 release
Packaging fix:
- packaging: Fix issue with broken git component paths in packages on macOS and Linux (#143)
- packaging: Exclude dev dependency in macOS package
Minor features / fixes:
- Added a
sno meta get
command for viewing dataset metadata (#136) merge
,commit
,init
,import
commands can now take commit messages as files with[email protected]
. This replaces thesno commit -F
option (#138)import
: Added--table-info
option to set dataset metadata, when it can't be autodetected from the source database (#139)pull
,push
,fetch
,clone
commands now show progress - disabled with--quiet
(#144)import
now works while on an empty branch (#149)
v0.4.0
Overview
0.4.0 adds basic support for resolving merge conflicts, imports from postgres databases, and a variety of other minor features
Major changes in this release
- Basic conflict resolution:
- Major improvements to
sno import
andsno init --import
: - Added
sno show
: shows a commit. With-o json
generates a patch (#48) - Added
sno apply
to apply the patches generated bysno show -o json
(#61)
Minor features / fixes:
- add a changelog (here!)
sno import
enhancements (in addition to major changes above):- GPKG database paths no longer need
GPKG:
prefix - now takes table names as separate arguments
- Added
--primary-key=FIELD
to override primary key field name - Added
--message
to customize the commit message --list
no longer requires a repository
- GPKG database paths no longer need
sno init --import
enhancements:- imports are much faster (#55)
- now imports all tables from database, doesn't allow table to be specified
- Many JSON output improvements:
- JSON output is specified with
-o json
instead of--json
(#98) - Added syntax highlighting to JSON output when viewed in a terminal (#54)
sno diff
JSON output layout has changed - features are now flat objects instead of GeoJSON objects. This is much more compact (#71)- Added JSON output option for most commands
- Added
--json-style
option to several commands to control JSON formatting (#70)
- JSON output is specified with
sno diff
:sno commit
:- can now commit some subset of the changes by supplying filter args, ie
[dataset[:pk]]
(#69)
- can now commit some subset of the changes by supplying filter args, ie
- removed
import-gpkg
command; useimport
instead (#85) - Error messages now go to stderr instead of stdout (#57)
- Error conditions now use exit codes to indicate different types of errors (#46)
Compatibility
Repositories created with Sno v0.2 onwards are compatible with v0.4. For assistance upgrading any v0.1 repositories, please read our upgrade guide.
v0.3.1
This is a minor update to v0.3.
Changes in this release
- Sno is now available on Windows 🎉. Download the .msi installer below for Windows 8.1+ / Server 2016+ (64-bit).
- Updates to continuous integration — installers/archives are now built and tested with every commit for every platform.
- For macOS users, a homebrew "tap" is now available:
brew cask install koordinates/sno/sno
- Several bug fixes
Upgrading
There are no upgrade requirements or compatibility issues from v0.3.0.
v0.3
Welcome to the first public preview release of Sno! Thanks to all our private testers who have given it a spin up until now.
Major changes in this release
- Sno is now publicly available under the GPL open source license.
- Sno now has a website at sno.earth
- Standalone builds and packaging for Linux and macOS. Windows won't be far behind
- Refactoring to support alternative database working copies
- Dependency upgrades (GDAL; Git; Pygit2; Proj; Libgit2; Sqlite; and others)
- Several bug fixes
Upgrading
If you were running a preview release, remove it before installing the new release:
$ brew uninstall sno
$ brew untap koordinates/sno
Repository Hosting
We have an initial preview available of our Sno repository hosting. This allows you & your team to push and pull Sno repositories. Please contact [email protected] with your Github username and we can get you set up. There is no cost for this service.
Compatibility
Please note that compatibility for 0.x releases (software or repositories) isn't guaranteed. Sno is evolving quickly and things will change. However, we aim to provide the means to upgrade existing repositories between 0.x versions and to 1.0
Repositories created with Sno v0.2 are compatible with v0.3. For assistance upgrading any v0.1 repositories, please read our upgrade guide.
v0.2
Welcome to the second preview release!
Major changes in this release
- First and foremost, the name — we're now called Sno!
- A new repository structure/layout, which has better performance and a smaller on-disk size
- Data imports are now orders of magnitude faster
- Support for multiple datasets in a single Sno repository
- Support for non-spatial datasets
- Increased test coverage including end-to-end tests
- Improved macOS Homebrew packaging with CI testing.
- Prototype support for spatial-indexing and a sno query command for spatial lookups.
- Diffs across branches/commits, and a GeoJSON diff format.
- Numerous bug fixes
Repository Hosting
We have an initial preview available of our Sno repository hosting. This allows you & your team to push and pull Sno repositories.
Please contact [email protected] with your Github username (even if you’re a Sno user already) and we’ll get you set up. There is no cost for this service.
Compatibility
Please note that compatibility for 0.x releases (software or repositories) isn't guaranteed. Sno is evolving quickly and things will change. However, we aim to provide the means to upgrade existing repositories between 0.x versions and to 1.0
Repositories created with older Sno versions are not compatible with v0.2. For assistance upgrading your repositories, please read our upgrade guide
Note that some command names and argument syntax have changed. Please consult the documentation for more information.