2.2.0

Release 2.2.0

- Various improvements to how certificate problems are communicated
  - Adds new warning boxes on the plugin options page when your
    certificate is invalid or nearing expiry.
  - Also adds new warning boxes on the plugin options page when
    your certificate isn't generated with the latest standards
    that Obsidian Local REST API uses.
  - Includes information about upcoming certificate expiries
    and standard compliance in `/` route output when
    incoming connection is authenticated, too, so other tools
    like Obsidian Web might be able to warn you when your
    certificate is nearing expiry.
- Moves some settings that really should be considered "Advanced"
  into "Advanced Settings" including both port settings.
- Some minor copy changes for clarity.

2.1.1

Release 2.1.1

- Fixes a bug that would cause generated certificates to be set such
  that their subjectAlternativeName (SAN) matched the binding host, if
  set. If you set your binding host to 0.0.0.0, but that doesn't make
  sense from your browser's perspective. Instead: the SAN should be set
  to the actual hostname...probably 127.0.0.1.
- Adds logging for incoming requests.  I'd been intending to add this
  for a very long time, but just now finally made that effort.

2.1.0

Release 2.1.0

- Advanced Settings:
  - Adds support for specifying 'subjectAltName' hostnames for use in
    generating certificates.  This can be useful if you are accessing
    Obsidian (via Obsidian Local REST API) on a host other than the
    one on which you are running it.  For example, say you are trying to
    configure the 'Obsidian Web' Chrome Extension on your work computer
    to connect to your running Obsidian instance on your personal one.
    If your personal computer can be accessed via 'sweedishfish.local',
    you could convince Chrome into counting your certificate as valid
    if you have added 'sweedishfish.local' to the aforementioned field.

2.0.6

Release 2.0.6

- Repackaging with an updated package-lock.json

2.0.4

Release 2.0.4

- Fixes a bug in which some operations around daily notes were not
  working.  This was resolved by reverting an esbuild upgrade from
  0.17.3 back to the version we were using previously: 0.13.2.

2.0.3

New Features:

• Increases maximum incoming payload size to 1GB from the
  express-defined default of 100kB.
• Fixes handling of incoming binary content such that you can PUT binary
  files into your vault -- just be sure to set an appropriate
  Content-Type header.

Backward-incompatible Changes:

• Removes /search/gui/ endpoint -- this endpoint was brittle and relied
  on private/undocumented behavior (see #71). This functionality was
  removed due to not being maintanable long-term.

Note: this is a re-release of 2.0.0 following a handful of release build process fixes.

1.6.1

Release 1.6.1

- Fixes a bug in which modifications to the field labeled "Private Key"
  in the UI would instead update the public key.

1.6.0

Release 1.6.0

- Adds support for allowing 'PATCH' request to ignore trailing newlines
  when calculating content insertion position.  Thanks to @cdloh for
  putting this together! (#55)
- Adds support for automatically creating missing directory segments in
  a POST or PUT path.  Thanks @SettingDust for bearing through the PR
  review process! (#44)
- Adds functionality allowing you to bind the API service to a host of
  your choice. This might be useful for users who know what they're
  doing and would like to, for example, run Obsidian in a container like
  obsidian-remote (which I personally use, too -- thanks @sytone for
  making that available!).  (#18)
- Allows you to specify the header in which to look for the
  Authorization tokens.  By default, this is 'Authorization', but
  perhaps you're running Obsidian behind Nginx or some other service,
  and you'd like that tool to look for _its_ authorization tokens in
  the 'Authorization' header.  Now you can tell this plugin to look for
  the token in whatever header you'd like.  Thanks, @derekantrican for
  putting this together as a feature! (#61)
- Significant updates to the plugin settings panel including:
    - Improvements in wording around how we describe the non-encrypted
      HTTP server.
    - Change how we present the buttons used for resetting settings and
      resetting crypogaphy.
    - A new 'Advanced Settings' section in which you can:
        - Directly set your API key (maybe you want all of your Obsidian
          instances to use the same one?)
        - Directly setting your certificate, private key, and public key
          (possibly for the same reason)
        - Configuring the name of the header we'll look in to find your
          authorization token (see above).
        - Configuring the hostname the server binds to.

1.5.2

Release 1.5.2

- Fixes bug preventing downloading of binary files. (Fixes #48)

1.5.1

Release 1.5.1

- Adds /active/ endpoint supporting GET/POST/PUT/PATCH/DELETE-ing
  content of file opened in currently-focused editor pane.

Note: This is a re-release of 1.5.0 that has corrected a couple
packaging and test problems; I clearly was rushing a bit.