Release 2.0.0 Alpha 63

• Added support for SSO (internal Vimeo use only) to the Authenticator via Authenticator.fetchSsoDomain, Authenticator.createSsoAuthorizationUri, and Authenticator.authenticateWithSso.
• Renamed some Authenticator functions for consistency
  • clientCredentials -> authenticateWithClientCredentials
  • google -> authenticateWithGoogle
  • facebook -> authenticateWithFacebook
  • emailJoin -> authenticateWithEmailJoin
  • emailLogin -> authenticateWithEmailLogin
  • exchangeOAuthOneToken -> exchangeOAuth1Token

Release 2.0.0 Alpha 62

• Removed old V1 networking library, new V2 networking library is now the only way to use the library.
• Removed old examples
• Wrote new example demonstrating basic auth, client credentials, code grant authorization, fetching staff picks, and fetching a logged in user's videos.
• Added support for authentication via code grant and pincode in the Authenticator.
• Improved documentation around authentication.

Note: README has not been updated yet with the new library.

Release 2.0.0 Alpha 61

Introducing an all new Authenticator and VimeoApiClient. Use the request module to use the new client. Old client is still accessible in the vimeo-networking module. Documentation and full release to come later.

Release 2.0.0 Alpha 60

Adding support for exposing and reading Folders.

Release 2.0.0-alpha.59

• Adds new models artifacts for Serializable and Parcelable support.
• Models are no longer a transitive dependency so going forward consumers will need to explicitly declare which models they want to use: models, models-serializable or models-parcelable.

Release 2.0.0-alpha.58

Adding client id to the creation of connected apps.

Release 2.0.0-alpha.57

• Added support for /vidoes/{id}/status endpoint and the VideoStatus type that it returns.

Release 2.0.0-alpha.56

• Changed type variance of VimeoResponse from in to out.

Release 2.0.0-alpha.55

• Added new VimeoResponse.Error type, InvalidToken. This fatal error type is used to indicate when the token the consumer is using has been invalidated, either by logging out or by the server. This is to distinguish between ApiError instances that have an errorCode or 8000 or 8003 that may occasionally occur when the token is still valid.

Release 2.0.0-alpha.54

Added two new entries to the ErrorCodeType enum.

• INVALID_INPUT_PASSWORD_TOO_COMMON - 3127
• INVALID_INPUT_PASSWORD_REUSED - 3128