Release OSRM 5.4.2

Changes from 5.4.1
- Bugfixes
  - #3032 Fixed a bug that could result in emitting `invalid` as an instruction type on sliproads with mode changes
  - #3085 Fixed an outdated assertion that could throw without a cause for concern
  - #3037 Fixed omitting the last coordinate for overview=simplified
  - #3176 Fixed exposing wrong OSM ids in matching
  - Fixes splitting logic in map matching

Release OSRM 5.4.1

- Bugfixes
  - #3016: Fixes shared memory updates while queries are running

Release 5.4.0

  - Chages from 5.4.0-rc.6
    - Bugfixes re-introduce space between two entries in summaries

  - Changes from 5.4.0-rc.5
    - Bugfixes
      - fixed a bug where polyline decoding on a defective polyline could end up in out-of-bound access on a vector
    - Guidance
      - Summaries have been improved to consider references as well

  - Changes from 5.4.0-rc.4
    - Guidance
      - Improved detection of obvious name changes
    - Profiles
      - The default profile for car now excludes HOV-only routes in navigation by default
    - Bugfixes
      - Fixed a bug that could result in endless loops in combination with sliproads

  - Changes from 5.4.0-rc.3
    - Bugfixes
      - Fixed a bug where roundabout intersections could result in breaking assertions when immediately exited

  - Changes from 5.4.0-rc.2
    - Bugfixes
      - BREAKING: Fixed a bug where some roads could be falsly identified as sliproadsi This change requires reprocessing datasets with osrm-extract and osrm-contract
      - BREAKING: Fixed a bug that resulted in false names/ref/destination/pronunciation This change requires reprocessing datasets with osrm-extract and osrm-contract
      - `restrictions` is now used for namespaced restrictions and restriction exceptions (e.g. `restriction:motorcar=` as well as `except=motorcar`)
      - replaced lhs/rhs profiles by using test defined profiles
    - Trip Plugin
      - changed internal behaviour to prefer the smallest lexicographic result over the largest one

  - Changes from 5.3.0
    - Profiles
      - includes library guidance.lua that offers preliminary configuration on guidance.
      - added left_hand_driving flag in global profile properties
      - modified turn penalty function for car profile - better fit to real data
      - return `ref` and `name` as separate fields. Do no use ref or destination as fallback for name value
    - Guidance
      - Handle Access tags for lanes, only considering valid lanes in lane-guidance (think car | car | bike | car)
    - API:
      - `annotations=true` now returns the data source id for each segment as `datasources`
      - Reduced semantic of merge to refer only to merges from a lane onto a motorway-like road
      - new `ref` field in the `RouteStep` object. It contains the reference code or name of a way. Previously merged into the `name` property like `name (ref)` and are now separate fields.
    - Bugfixes
      - Fixed an issue that would result in segfaults for viaroutes with an invalid intermediate segment when u-turns were allowed at the via-location
      - Invalid only_* restrictions could result in loss of connectivity. As a fallback, we assume all turns allowed when the restriction is not valid
      - Fixed a bug that could result in an infinite loop when finding information about an upcoming intersection
      - Fixed a bug that led to not discovering if a road simply looses a considered prefix
      - BREAKING: Fixed a bug that could crash postprocessing of instructions on invalid roundabout taggings. This change requires reprocessing datasets with osrm-extract and osrm-contract
      - Fixed an issue that could emit `invalid` as instruction when ending on a sliproad after a traffic-light
      - Fixed an issue that would detect turning circles as sliproads
      - Fixed a bug where post-processing instructions (e.g. left + left -> uturn) could result in false pronunciations
      - Fixes a bug where a bearing range of zero would cause exhaustive graph traversals
      - Fixes a bug where certain looped geometries could cause an infinite loop during extraction

    - Infrastructure:
      - Adds a feature to limit results in nearest service with a default of 100 in `osrm-routed`

5.4.0-rc.7
  - Chages from 5.4.0-rc.6
    - Bugfixes re-introduce space between two entries in summaries

5.4.0-rc.6
  - Changes from 5.4.0-rc.5
    - Bugfixes
      - fixed a bug where polyline decoding on a defective polyline could end up in out-of-bound access on a vector
    - Guidance
      - Summaries have been improved to consider references as well

  - Changes from 5.4.0-rc.4
    - Guidance
      - Improved detection of obvious name changes
    - Profiles
      - The default profile for car now excludes HOV-only routes in navigation by default
    - Bugfixes
      - Fixed a bug that could result in endless loops in combination with sliproads

5.4.0-rc.4
  Changes from 5.4.0-rc.3
    - Bugfixes
      - Fixed a bug where roundabout intersections could result in breaking assertions when immediately exited

Changes from 5.4.0-rc.2
  - Bugfixes
    - BREAKING: Fixed a bug where some roads could be falsly identified as sliproadsi This change requires reprocessing datasets with osrm-extract and osrm-contract
    - BREAKING: Fixed a bug that resulted in false names/ref/destination/pronunciation This change requires reprocessing datasets with osrm-extract and osrm-contract

5.4.0-rc.2
    - Bugfixes
        - Fixes a bug where certain looped geometries could cause an infinite loop during extraction

5.4.0-rc.1
  Changes from 5.3.0
    - Profiles
      - includes library guidance.lua that offers preliminary configuration on guidance.
      - added left_hand_driving flag in global profile properties
      - modified turn penalty function for car profile - better fit to real data
      - return `ref` and `name` as separate fields. Do no use ref or destination as fallback for name value
    - Guidance
      - Handle Access tags for lanes, only considering valid lanes in lane-guidance (think car | car | bike | car)
    - API:
      - `annotations=true` now returns the data source id for each segment as `datasources`
      - Reduced semantic of merge to refer only to merges from a lane onto a motorway-like road
      - new `ref` field in the `RouteStep` object. It contains the reference code or name of a way. Previously merged into the `name` property like `name (ref)` and are now separa
    - Bugfixes
      - Fixed an issue that would result in segfaults for viaroutes with an invalid intermediate segment when u-turns were allowed at the via-location
      - Invalid only_* restrictions could result in loss of connectivity. As a fallback, we assume all turns allowed when the restriction is not valid
      - Fixed a bug that could result in an infinite loop when finding information about an upcoming intersection
      - Fixed a bug that led to not discovering if a road simply looses a considered prefix
      - BREAKING: Fixed a bug that could crash postprocessing of instructions on invalid roundabout taggings. This change requires reprocessing datasets with osrm-extract and osrm
      - Fixed an issue that could emit `invalid` as instruction when ending on a sliproad after a traffic-light
      - Fixed an issue that would detect turning circles as sliproads
      - Fixed a bug where post-processing instructions (e.g. left + left -> uturn) could result in false pronunciations
      - Fixes a bug where a bearing range of zero would cause exhaustive graph traversals

Release 5.3.0

Changes from 5.3.0-rc.3
  - Guidance
    - Only announce `use lane` on required turns (not using all lanes to go straight)
    - Moved `lanes` to the intersection objects. This is BREAKING in relation to other Release Candidates but not with respect to other releases.
  - Bugfixes
    - Fix BREAKING: bug that could result in failure to load 'osrm.icd' files. This breaks the dataformat
    - Fix: bug that results in segfaults when `use lane` instructions are suppressed

Changes form 5.2.7
  - API
    - Introduces new `TurnType` in the form of `use lane`. The type indicates that you have to stick to a lane without turning
    - Introduces `lanes` to the `Intersection` object. The lane data contains both the markings at the intersection and a flag indicating if they can be chosen for the next turn
    - Removed unused `-s` from `osrm-datastore`
  - Guidance
    - Only announce `use lane` on required turns (not using all lanes to go straight)
    - Improved detection of obvious turns
    - Improved turn lane detection
    - Reduce the number of end-of-road instructions in obvious cases
  - Profile:
    - bicycle.lua: Surface speeds never increase the actual speed
  - Infrastructure
    - Add 32bit support
    - Add ARM NEON/VFP support
    - Fix Windows builds
    - Optimize speed file updates using mmap
    - Add option to disable LTO for older compilers
    - BREAKING: The new turn type changes the turn-type order. This breaks the **data format**.
    - BREAKING: Turn lane data introduces two new files (osrm.tld,osrm.tls). This breaks the fileformat for older versions.
  - Bugfixes:
    - Fix devide by zero on updating speed data using osrm-contract

Release 5.3.0 RC3

Changes from RC2:
- Guidance
  - Improved detection of obvious turns
  - Improved turn lane detection
- Bugfixes
  - Fix bug that didn't chose minimal weights on overlapping edges

Changes from 5.3.0-rc.1
    - Bugfixes
        - Fixes invalid checks in the lane-extraction part of the car profile

Release 5.3.0 RC1
- API
 - Introduces new `TurnType` in the form of `use lane`. The type indicates that you have to stick to a lane without turning
 - Introduces lanes to the route response. The lane data contains both the markings at the intersection and a flag indicating their involvement in the turn

- Infrastructure
 - BREAKING: The new turn type changes the turn-type order. This breaks the **data format**.
 - BREAKING: Turn lane data introduces a new file (osrm.tld). This breaks the fileformat for older versions.