2.0.3 (MrRefactoring#107)

* endpoint types changed

* type definition changed

* version 2.0.1

* changelog added

* issueTypeIds fixed

* models types changed

* - `Buffer.from` replaced to raw JS code in Basic authorization
- Telemetry config type fixed
- `noCheckAtlassianToken` flag added to config
- Typing improves

* tests added

* The principles of running linter have been changed

* 2.0.2 RC

* API updates

* Add attachment API fixed (MrRefactoring#106)

* Error with attachment fixed

* Max one github action in parallel

* GitHub actions: create .env file

* Action syntax fix

* linter fixes

* 2.0.3

Author: MrRefactoring

.env.example

@@ -0,0 +1,3 @@
+HOST=
+EMAIL=
+API_TOKEN=

.github/workflows/ci.yaml

@@ -8,6 +8,7 @@ jobs:
     runs-on: ubuntu-latest
 
     strategy:
+      max-parallel: 1
       matrix:
         node-version: [10.x, 12.x, 14.x]
 
@@ -19,6 +20,12 @@ jobs:
           node-version: ${{ matrix.node-version }}
       - run: npm ci
       - run: npm install
+      - name: Create .env file
+        run: |
+          touch .env
+          echo HOST=${{ secrets.HOST }} >> .env
+          echo EMAIL=${{ secrets.EMAIL }} >> .env
+          echo API_TOKEN=${{ secrets.API_TOKEN }} >> .env
       - run: npm run build
       - run: npm test
       - run: npm run lint

.gitignore

@@ -8,3 +8,4 @@ coverage/
 yarn.lock
 yarn-error.log
 .DS_Store
+.env

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Jira.js changelog
 
+### 2.0.3
+
+- Improved typing
+- Fixed the bug that it was impossible to attach an attachment to an issue
+- Other small improvements
+
 ### 2.0.2
 
 - `Buffer.from` replaced to raw JS code in Basic authorization

README.md

@@ -51,7 +51,7 @@ yarn add jira.js
 
 ## Telemetry information collection agreement
 
-The use of this library may collect, record and transmit data about the operation of the library and related data, as well as potentially personal data, including ip address from which the request is made, user agent from the device from which the request is made, version of the library used, version of the telemetry sending library, name of the invoked method, authorization type information (can be configured), base configuration request usage information, callback information, onResponse middleware usage information, onError middleware usage information, queries usage information, body usage information in request, headers usage information in request, strict GDPR flag enabling information, HTTP response code (can be configured), request start date and time and response receipt date and time (can be configured).
+The use of this library may collect, record and transmit data about the operation of the library and related data, as well as potentially personal data, including ip address from which the request is made, user agent from the device from which the request is made, version of the library used, version of the telemetry sending library, name of the invoked method, authorization type information (can be configured), base configuration request usage information, callback information, onResponse middleware usage information, onError middleware usage information, queries usage information, body usage information in request, headers usage information in request, strict GDPR flag enabling information, HTTP response code (can be configured), request start date and time and response receipt date and time (can be configured), No check atlassian token flag enabling information.
 
 The type and amount of data may vary with the version of the libraries and can be changed at any time without notice.