2.4.0

Release notes

🔒 Security SDK

• FEAT: New module to manage Application Trust

🚀 Voyager Client

• FEAT: Sequential offline data replication is now supported
• FEAT: Added ability to retry offline data over time
• FEAT: Minor bugfixes and improvements
• CHORE: Updates for the latest and greatest Apollo and related libraries

2.3.1

Release notes

🚀 Voyager Client

• FIX: Allow to pass cache update functions for mutations.
  See config.mutationCacheUpdates for more information

2.3.0

Release notes

🚀 Voyager Client

• BREAKING: Added new listener methods for offline queue events
• FEAT: Added retry operation for offline mutations that failed to contact the server
• FEAT: Added option to configure retry strategies
• FEAT: Enable offline processing when no optimistic response is passed
• FEAT: Network errors do not remove offline operations from the queue
• FEAT: Added sequential processing for offline mutations
• FIX: Offline queue is ignored when the application is online
• FIX: Conflict data is being updated for offline changes (users no longer can conflict with themselves)
• CHORE: Updates for the latest and greatest Apollo and related libraries

2.2.0

Release notes

• FIX: Updated to latest versions of Apollo Client and related libraries
• BREAKING: New way to configure conflict resolution using an object format:
  conflictStrategy: clientWins => conflictStrategy:{ default:clientWins }

2.2.0-rc1

Release notes

• FIX: Updated to latest versions of Apollo Client and related libraries
• BREAKING: New way to configure conflict resolution using an object format:
  conflictStrategy: clientWins => conflictStrategy:{ default:clientWins }

2.1.1

Release Notes

• BUG: Include voyager client dist folder in release

2.1.0

Release notes

• FEAT: Sync SDK
  Please follow Sync SDK documentation for more information
• FEAT: Auth SDK provides now method to refresh tokens.
  See auth.getAuthContextProvider method for more details
• BREAKING: New way to initialize SDK and work with config.
  Configuration is now passed directly to each individual SDK.
  For example:

const init  = require("@aerogear/app");
const app = init(config);
const Auth = require('@aerogear/auth').Auth;
const authService = new Auth(app.config);

Init method returns now app object that contains config:
https://docs.aerogear.org/api/cordova/latest/app/classes/aerogearapp.html
Please follow new initialization guides for individual SDK's

Changes

https://github.com/aerogear/aerogear-js-sdk/compare/2.0.0...2.1.0?expand=1

2.1.0-rc3

Changes: https://github.com/aerogear/aerogear-js-sdk/compare/2.1.0-rc2...2.1.0-rc3?expand=1

Note:
Breaking changes introduced in top level API.
Going to be covered in release notes.

2.1.0-rc2

Internal update to change structure of peerDependencies of Core package.
No changes for end users.

2.1.0-rc1

This prerelease updates the auth sdk to use keycloak-js@4.8.3 (was 4.0.0-beta.1).

keycloak-js@4.8.3 introduces a new cordova-native login flow that could potentially improve the user experience our Auth SDK provides for login/logout actions on Cordova.