Notable

Latest version: v0.4.2

Safety actively analyzes 621706 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.2.0

* Be more disciplined about semver ;)
* Add confirmation prior to deletion [93](https://github.com/jmcfarlane/notable/issues/93)
* Fix decryption of notes with Unicode characters [96](https://github.com/jmcfarlane/notable/issues/96)
* This **is** backwards compatible with notes saved by Notable
prior to v0.1.2. Newer versions automatically migrate notes to a
more modern encryption mechanism that fully supports Unicode.
Please upgrade :)
* Support for this older encryption mechism will be removed in the
future
* Add builds for Arm7 [95](https://github.com/jmcfarlane/notable/issues/95)
* Add builds for Arm6

0.1.3

* Prevent `./scripts/release.sh` from being called directly
* Migrate from bindata to rice
* Add support for go 1.10
* Add note auto save feature (specific and persistable per note) [92](https://github.com/jmcfarlane/notable/issues/92)

0.1.2

* Fix Docker tags on release (was not updating the docker.io tags)
* Improve encryption by using AES-GCM [via cryptopasta](https://github.com/gtank/cryptopasta)
* Migrate to [Dep](https://github.com/golang/dep) for dependency management
* Drop support for Go <= 1.7 (Dep is worth it ;)
* Add integration with https://codecov.io
* Add `make coverage` build target for detail on test coverage
* Fix incorrect db path setup used by tests :/
* Initial tests for secondary nodes
* Minor clean up of version string calculations, add `pid`
* Reduce dead code
* Remove unnecessary `db.migrate()` call from tests :/
* Update dependencies
* Reduce global state (much more to be done here)
* Add `/api/stop` handler and make `/api/restart` require `msg`
* Reduce race conditions (credit: `-race`!)
* Ensure all tests persist to a temporary directory
* Fix defects related to http `handler` error handling (more to do)
* Fix duplicate args when using `-daemon=true -browser=true`

0.1.1

* Upgrade to Go 1.9.2
* Initial support for automatic client consumption of changes when
Notable is being ran in distributed mode. Currently this performs a
very basic reload of the notes table, but does not take into
consideration any notes currently open for edit. Reloading works on
both primary and secondary nodes (via different triggers).
* Upgrade runnable Docker container from Alpine to `scratch`
* Produce more release artifacts via Docker (less required on the host)
* Use `-race` when running tests
* Fix regression in tests (need to clean up from a stalled CLI effort)
* Ensure artifact copy from container to host is rootless ;)
* Update features list to include distributed writes
* Initial (successful) testing with Keybase!

0.1.0

* Initial (experimental) support for distributed writes.
* The idea is you can share your notes directory via a tool like
Syncthing, and then run a single primary and as many
`-secondary` instances as you like. All computers have write
access, and all changes get replicated through the primary back
to the secondary nodes. Current replication mechanisms (maybe)
known to work:
1. [Syncthing](https://syncthing.net/)
* Testing has only been performed on Linux
* UI is very much incomplete
* Remove sqlite
* Upgrade dependencies
* Purge the `vendor` folder before a build

0.0.10

* Add flag `bolt.timeout` for use with opening BoltDB.
* Move `init` logic into `main` to fix race conditions on startup.
* Open BoltDB before Bleve as the former supports a timeout :)
* Improve error messaging on startup.
* Enable line wrap.
* Enable vendoring via [Glide](https://glide.sh/).
* Ensure all released binaries are built with vendored dependencies.
* Initial work on a command line client [`notable-cli`](https://github.com/jmcfarlane/notable/tree/main/cmd/notable-cli).
* Fix case incorrect import of [logrus](https://github.com/sirupsen/logrus).

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.