2.5.4

Release 2.5.4

- Adds new Extension API allowing folks to define their own routes
  and API functionality via separate Obsidian Plugins.
  - Want to expose REST API routes as part of your existing plugin?  Now
    you can!
  - Need an API feature that doesn't quite fit the scope of what
    Obsidian Local REST API intends to provide?
    Now you can add your own routes in your own plugin,
    but let them be served by Obsidian Local REST API.

2.4.3

Release 2.4.3

- Fixes (speculatively) a bug which might prevent any search
  operations from succeeding if a `null` tag was found on any
  note.
- Minor clean-up and word changes in the configuration panel UI
  including:
  - Automatically re-fresh the server status when toggling
    the HTTP or HTTPs servers on or off.
  - Include certificate installation notice & instructions
    in the table showing the HTTPs server status.
  - Show all subjectAltName options in server status table.
  - Include 'copy' link for API key.

2.4.1

Release 2.4.1

Note: This is a re-release of 2.4.0, with an updated package-lock.json.

- Updating settings panel to:
  - Provide direct access to the API connection URL.
  - Rephrasing things and giving better insight into where folks can
    find docs and what requests look like.

2.3.0

Release 2.3.0

- Adds toggle allowing user to enable/disable HTTPs server (under
  'Advanced Settings').  This toggle is not likely to be useful
  in cases outside of troubleshooting connection-related problems.

2.2.2

Release 2.2.2

- Fixes a bug in which we'd show that you needed to regenerate your
  certificate...only when you didn't.  And, vice-versa, of course,
  as things always go.

2.2.1

Release 2.2.1

- 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.

This is a re-release of 2.2.0.

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