1.2.1

Release 1.2.1 -- Fix for /search/ endpoint

- Adds 4xx error message when search query is invalid.
  If you provided an invalid search query, the error was previously
  uncaught, and you wouldn't have a way of knowing what you did
  wrong.  This corrects that oversight.

1.2.0

Release 1.2.0 -- Adds new /search/ endpoints.

- Adds new /search/ endpoints including:
  - /search/: Accepts a JsonLogic request body for finding notes
  matching your provided query.
  - /search/gui/: Accepts search strings as you'd enter them into the UI
  to search for mathching documents.  Note that, unlike other methods,
  this one does interact with the UI directly; so you will see the
  search panel open!
  - /search/simple/: Accepts a simple string query and returns notes
  having this string.
- Adds new "metadata" output for /vault/ `GET` requests which:
  - Will return, as a JSON object, your note's content as well as
  filesystem metadata (modification time, etc) and parsed tags and
  frontmatter.
  - You must send an `Accept` header of
  `application/vnd.olrapi.note+json` to receive this content.
- Changes behavior of /vault/ `POST` endpoint such that, if the file you
  have requested does not exist, it will be created for you instead of
  returning a 404 error.  This is intended to allow for easier
  automation by creating a single-request create-or-append method.

1.1.0

Release 1.1.0 -- Adds optionally-enablable HTTP server.

- Note: your API Key is still required for all interactions!
- The utility of an HTTPS server on something bound to just localhost is
a little dubious, and after consulting with a colleague of mine, he
confirmed my beliefs that as long as the service was not exposed to the
internet in any way, there was no likely possiblity of connection
snooping.  There are no avenues for an XSS attack in any case given that
this is using header-based auth.
- Additionally, Chrome will not allow you to connect to sites with
self-signed certificates unless you upload your certificate as a valid
Certificate Authority.  Although _I_ know that's safe, I imagine that's
even scarier for a user than just running on HTTP alone; so, this will
reduce friction at the expense of only very theoretical security.

1.0.12

Release 1.0.12: Fix PATCH header boundary identification.

1.0.11

Release 1.0.11; fixes a bug in positioning content underneath a heade…

1.0.10

Release 1.0.10; adds versioning information to root API endpoint.

1.0.9

Release 1.0.9; fixing minor bug in inferring status code from error c…

1.0.8

Release 1.0.8; just build process fixes.

1.0.5

Bumping version to 1.0.5.

1.0.4

Bumping version to 1.0.4.