v7.2.0

• #395: relative uris in embedded hal documents are now resolved using the
  'self' link in the embedded document, instead of the parent. although not
  explicitly said in the hal standards, i feel this is the right behavior.
  most users will not see a difference, but if you relied on the old behavior
  this could cause some subtle bc breaks.

v7.1.1

• #392: The action() function on State classes would only return the default
  action (@reda-alaoui).
• Changed how Cache classes are exported, as an experiment to see if IDE docs
  are more complete.

v7.1.0

• Support for the inv-by Link relationship type from the [Linked Cache
  Invalidation draft][2]. This link lets a resource tell the client that
  it's cache should expire when the linked resource's cache also expires.
• The 'prompt' field in HAL Forms for properties with 'options' set was
  ignored.

v7.0.1

• No longer testing Node 10 and Node 15. Added Node 16.
• Actions are now retained when caching. Before this, action information was
  dropped which meant that any actions in embedded resources were not
  accessible. (@hugothomas)

v7.0.0

New major version!

Changes since 7.0.0-beta.5

• The title header is now considered to be an 'entity' / 'content'-header.

Changes since Ketting 6

• Support for most of the new HAL-Forms features, which got a major refresh in 2021. New features include dropdowns and most field types and field attributes that exist in the HTML5 specification.
• Ketting actions got a major refresh, in part to support HAL-Forms. (The type changes might be a BC break)
• Remove support for Prefer-Push. Browsers are basically dropping HTTP/2
  Push, and not enough work is done to make this very interesting.
  (More info).
• Support for Deprecation and Sunset HTTP headers. (More info)
• If any HTTP response includes a Content-Location header, Ketting will automatically place the response body in the state cache. This means you could for example do a POST request to create a new resource, and have your server respond with the newly created entity body + a Content-Location header for the new resource location, and Ketting will pre-populate the cache for that new resource, potentially saving a round-trip.
• State objects (which are returned from .get()) now have a synchronous .follow() and .followAll().
• Better support for application/problem+json
• Support for title property on Siren fields.
• We're now telling the browser to ignore the browser cache if Resource.refresh() is used.
• The 'parsing API' had a bit of a refresh and was simplified. If you wrote a custom format parser, this will affect you.

v7.0.0-beta.5

• label and value were parsed in reverse.

v7.0.0-beta.4

• Added renderAs 'checkbox' to multi-select fields in actions.
• Export OptionDataSource.

v7.0.0-beta.3

• Support for HAL Forms version 2021-02-20, which adds the 'options'
  property.
• Kettings now has support for 'dropdown' fields, allowing users to provide
  lists of possible options in 3 different ways:
  1. An inline list
  2. An external HTTP resource (JSON body or CSV body)
  3. Provided as links from a hypermedia source.
     Only 1 and 2 are supported by HAL Forms, 3 is just an internal feature until
     there is a format that has first-class support for this.
• A bit of a rewrite of 'fields' again. Only a single type is exported, and
  all the types are cleaned up.

v7.0.0-beta.2

• Support for Siren 'title' on fields. This was an oversight.

v7.0.0-beta.1

• Remove support for Prefer-Push. Browsers are basically dropping HTTP/2
  Push, and not enough work is done to make this very interesting.
  More background.
• Revert 'unifiying URLs' PR, we're back to using url.resolve in node.