1.6.0 (#248)

* #199 - move from rest to enterprise task-forms variables api (#234)

* [ADF-684] added query parameter to retrieve related content for task and process (#235)

* [ADF-684] Added optional parameter to filter proper related contents

* Updated changelog, fixed documentation

* [ADF-680] fixed default value parameter

* [ADF-622] Complete TypeScript definitions for JS-API (#236)

* new definition for core

* move to node 8

* change log update

* update typescript 2.4.0

* [ADF-793] The ability to retrieve a rendition's url from the content API (#238)

* add getRenditionUrl method

* [ADF-793] getRenditionUrl

* CHANGELOG update

* Update CHANGELOG.md

* updating declarations (#239)

* PathElementEntity md

* fix constructor probpme d.ts

* Fixing tslint error (#241)

* add package-lock file

* index.d.ts fix tslint (#242)

* update typings

* Added isRelatedContent option to create related content on process in… (#243)

* Added isRelatedContent option to create related content on process instance

* Fix error on createRelated content - added change to changelog

* Update CHANGELOG.md

* 1.6.0 (#247)

* Update CHANGELOG.md

Author: eromano

.travis.yml

@@ -1,6 +1,6 @@
 language: node_js
 node_js:
-  - "5.0.0"
+  - "8.0.0"
 before_install: npm install -g grunt-cli
 install: npm install
 sudo: false

CHANGELOG.md

@@ -4,6 +4,17 @@
 
 # Alfresco JS API
 
+<a name="1.6.0"></a>
+# [1.6.0](https://github.com/Alfresco/alfresco-js-api/releases/tag/1.6.0) (29-06-2017)
+## Fix
+- [Move /task-forms/{task-id}/variables from rest to enterprise](https://github.com/Alfresco/alfresco-js-api/issues/199)
+- [Added query param for get related contents](https://issues.alfresco.com/jira/browse/ADF-684)
+- [Added query param for create related contents on task and process instance](https://github.com/Alfresco/alfresco-js-api/issues/244)
+
+## Features
+- [Complete TypeScript definitions for JS-API](https://github.com/Alfresco/alfresco-js-api/issues/228)
+- [Get rendition URL for a given nodeId from content API](https://github.com/Alfresco/alfresco-js-api/issues/237)
+
 <a name="1.5.0"></a>
 # [1.5.0](https://github.com/Alfresco/alfresco-js-api/releases/tag/1.5.0) (25-05-2017)
 ## Features

definitions/alfresco-auth.yaml

@@ -0,0 +1,184 @@
+swagger: '2.0'
+info:
+  description: |
+    **Authentication API**
+
+    Provides access to the authentication features of Alfresco Content Services.
+  version: '1'
+  title: Alfresco Content Services REST API
+basePath: /alfresco/api/-default-/public/authentication/versions/1
+securityDefinitions:
+  basicAuth:
+    type: basic
+    description: HTTP Basic Authentication
+security:
+  - basicAuth: []
+consumes:
+  - application/json
+produces:
+  - application/json
+paths:
+  '/tickets':
+    post:
+      x-alfresco-since: "5.2"
+      tags:
+        - authentication
+      summary: Create ticket (login)
+      description: |
+        **Note:** this endpoint is available in Alfresco 5.2 and newer versions.
+
+        Logs in and returns the new authentication ticket.
+
+        The userId and password properties are mandatory in the request body. For example:
+        ```JSON
+        {
+            "userId": "jbloggs",
+            "password": "password"
+        }
+        ```
+        To use the ticket in future requests you should pass it in the request header.
+        For example using Javascript:
+          ```Javascript
+            request.setRequestHeader ("Authorization", "Basic " + btoa(ticket));
+          ```
+      operationId: createTicket
+      parameters:
+        - in: body
+          name: ticketBodyCreate
+          description: The user credential.
+          required: true
+          schema:
+            $ref: '#/definitions/TicketBody'
+      consumes:
+        - application/json
+      produces:
+        - application/json
+      responses:
+        '201':
+          description: Successful response
+          schema:
+            $ref: '#/definitions/TicketEntry'
+        '400':
+          description: |
+            **userId** or **password** is not provided
+        '403':
+          description: Login failed
+        default:
+          description: Unexpected error
+          schema:
+            $ref: '#/definitions/Error'
+  '/tickets/-me-':
+    get:
+      x-alfresco-since: "5.2"
+      tags:
+        - authentication
+      summary: Validate ticket
+      description: |
+        **Note:** this endpoint is available in Alfresco 5.2 and newer versions.
+
+        Validates the specified ticket (derived from Authorization header) is still valid.
+
+        For example, you can pass the Authorization request header using Javascript:
+          ```Javascript
+            request.setRequestHeader ("Authorization", "Basic " + btoa(ticket));
+          ```
+      operationId: validateTicket
+      produces:
+        - application/json
+      responses:
+        '200':
+          description: Successful response
+          schema:
+            $ref: '#/definitions/ValidTicketEntry'
+        '400':
+          description: URL path does not include **-me-** or the ticket is not provided by the Authorization header
+        '401':
+          description: Authentication failed
+        '404':
+          description: The request is authorized correctly but the status of the user (of the supplied ticket) has
+            changed (for example, the user is locked or the account is disabled) or the ticket has expired
+        default:
+          description: Unexpected error
+          schema:
+            $ref: '#/definitions/Error'
+    delete:
+      x-alfresco-since: "5.2"
+      tags:
+        - authentication
+      summary: Delete ticket (logout)
+      description: |
+        **Note:** this endpoint is available in Alfresco 5.2 and newer versions.
+
+        Deletes logged in ticket (logout).
+      operationId: deleteTicket
+      responses:
+        '204':
+          description: Successful response
+        '400':
+          description: URL path does not include **-me-** or the ticket is not provided by the Authorization header
+        '404':
+          description: Status of the user has changed (for example, the user is locked or the account is disabled) or the ticket has expired
+        default:
+          description: Unexpected error
+          schema:
+            $ref: '#/definitions/Error'
+definitions:
+  Error:
+    type: object
+    required:
+      - error
+    properties:
+      error:
+        type: object
+        required:
+          - statusCode
+          - briefSummary
+          - stackTrace
+          - descriptionURL
+        properties:
+          errorKey:
+            type: string
+          statusCode:
+            type: integer
+            format: int32
+          briefSummary:
+            type: string
+          stackTrace:
+            type: string
+          descriptionURL:
+            type: string
+          logId:
+            type: string
+  TicketBody:
+    type: object
+    properties:
+      userId:
+        type: string
+      password:
+        type: string
+  TicketEntry:
+    type: object
+    required:
+      - entry
+    properties:
+      entry:
+        $ref: '#/definitions/Ticket'
+  Ticket:
+    type: object
+    properties:
+      id:
+        type: string
+      userId:
+        type: string
+  ValidTicketEntry:
+    type: object
+    required:
+      - entry
+    properties:
+      entry:
+        $ref: '#/definitions/ValidTicket'
+  ValidTicket:
+    type: object
+    properties:
+      id:
+        type: string