@respond-framework/react@0.1.1-test.5

0.1.1-test.5 (2019-10-23)

Code Refactoring

• remove flow from builds (332e730)

BREAKING CHANGES

• flow types are no longer available in published
  packages

@respond-framework/middleware-change-page-title@1.0.1-test.3

1.0.1-test.3 (2019-10-23)

Code Refactoring

• remove flow from builds (332e730)

BREAKING CHANGES

• flow types are no longer available in published
  packages

@respond-framework/boilerplate@0.1.1-test.6

0.1.1-test.6 (2019-10-23)

Note: Version bump only for package @respond-framework/boilerplate

integration-tests@1.0.1-test.5

1.0.1-test.5 (2019-10-16)

Bug Fixes

• history: store index of current history stack entry in the browser location state (#61) (3abd2b1)

BREAKING CHANGES

• history: browsers that don't support the history API or session storage are no longer supported at all. In practice this means IE9 is no longer supported.
• history: future entries in the history stack remain even if the user has since navigated from a previous entry to an external site (because they are no longer removed when they are potentially still the future entries in the browser stack)

Fixes #59

@respond-framework/utils@0.1.1-test.2

0.1.1-test.2 (2019-10-16)

Note: Version bump only for package @respond-framework/utils

@respond-framework/rudy@0.1.1-test.5

0.1.1-test.5 (2019-10-16)

Bug Fixes

• history: delete console.log from BrowserHistory (#58) (4d1a4e4), closes #46
• history: store index of current history stack entry in the browser location state (#61) (3abd2b1)

BREAKING CHANGES

• history: browsers that don't support the history API or session storage are no longer supported at all. In practice this means IE9 is no longer supported.
• history: future entries in the history stack remain even if the user has since navigated from a previous entry to an external site (because they are no longer removed when they are potentially still the future entries in the browser stack)

Fixes #59

@respond-framework/react@0.1.1-test.4

0.1.1-test.4 (2019-10-16)

Bug Fixes

• history: store index of current history stack entry in the browser location state (#61) (3abd2b1)

BREAKING CHANGES

• history: browsers that don't support the history API or session storage are no longer supported at all. In practice this means IE9 is no longer supported.
• history: future entries in the history stack remain even if the user has since navigated from a previous entry to an external site (because they are no longer removed when they are potentially still the future entries in the browser stack)

Fixes #59

@respond-framework/middleware-change-page-title@1.0.1-test.2

1.0.1-test.2 (2019-10-16)

Note: Version bump only for package @respond-framework/middleware-change-page-title

@respond-framework/boilerplate@0.1.1-test.5

0.1.1-test.5 (2019-10-16)

Note: Version bump only for package @respond-framework/boilerplate

integration-tests@1.0.1-test.4

1.0.1-test.4 (2019-09-10)

Bug Fixes

• update dependencies with security vulnerabilities (#47) (3c18480)
• history: pushing/replacing a route sometimes resulted in a back/next action (#56) (f6e06ad)

BREAKING CHANGES

• history: dispatching a route that matches the previous/next route in the history stack is no longer reinterpreted as a back/next action
• history: history functions set/setParams/setState/setQuery/setHash/setBasename no longer accept a function as an argument
• history: history functions set/setParams/setState/setQuery no longer merge their arguments with the existing params/state/query
• history: history functions back/next/jump no longer accept a state argument

Fixes #48