pagerduty-overlap-checker - npm Package Compare versions

Comparing version 1.1.0 to 1.1.1

lib/pagerduty.js

@@ -203,7 +203,7 @@ // Generated by CoffeeScript 1.10.0
                 exclusionStartDate = new Date(myStart);
-                exclusionStartDate.setHours(exclusionStartTime[0]);
-                exclusionStartDate.setMinutes(exclusionStartTime[1]);
+                exclusionStartDate.setUTCHours(exclusionStartTime[0]);
+                exclusionStartDate.setUTCMinutes(exclusionStartTime[1]);
                 exclusionEndDate = new Date(myStart);
-                exclusionEndDate.setHours(exclusionEndTime[0]);
-                exclusionEndDate.setMinutes(exclusionEndTime[1]);
+                exclusionEndDate.setUTCHours(exclusionEndTime[0]);
+                exclusionEndDate.setUTCMinutes(exclusionEndTime[1]);
                 if ((exclusionStartDate <= startDate && startDate < exclusionEndDate)) {
@@ -210,0 +210,0 @@ debug('excluded:', message);

package.json

 {
   "name": "pagerduty-overlap-checker",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "PagerDuty Overlap Duties Checker",
@@ -5,0 +5,0 @@ "main": "lib/",

README.md

@@ -19,4 +19,4 @@ [![Build Status](https://travis-ci.org/apiaryio/pagerduty-overlap-checker.svg?branch=master)](https://travis-ci.org/apiaryio/pagerduty-overlap-checker)
 - every `SCHEDULE` should have a `NOTIFICATIONS` to create incident or send message if overlap is found
-- `SCHEDULE` can contain a `EXCLUSION_DAYS` key, which specifies days (3 letter abb.) in form of object with optional `start` and `end` time (`hh:mm` format). If `start` or `end` is omitted, whole day is considered excluded. 
-Example below represents current weekend on-call setup. All datetimes are translated to UTC, so feel free to use a local time.
+- `SCHEDULE` can contain a `EXCLUSION_DAYS` key, which specifies days (3 letter abb.) in form of object with optional `start` and `end` time (`hh:mm` format **UTC TIMEZONE**).If `start` or `end` is omitted, whole day is considered excluded. 
+Example below represents current weekend on-call setup.
 
@@ -44,3 +44,3 @@ Currently, we only support Slack (`SLACK` with `SLACK_WEBHOOK_URL` and `CHANNEL`) or shorthanded `SLACK_WEBHOOK_URL` and PagerDuty (`PAGERDUTY_TOKEN`) notifications.
 		},
-		"EXCLUSION_DAYS": {"Fri": {"start": "16:00", "end": "23:59"}, "Sat": {}, "Sun": {"start": "00:00", "end": "16:00"}}
+		"EXCLUSION_DAYS": {"Fri": {"start": "14:00", "end": "23:59"}, "Sat": {}, "Sun": {"start": "00:00", "end": "14:00"}}
 	}]
@@ -65,2 +65,2 @@ }
 
-Alternatively, you can include the `DEBUG` variable in the `config.json` file (esp. for debugging on AWS Lambda).
+Alternatively, you can include the `DEBUG` variable in the `config.json` file (esp. for debugging on AWS Lambda).

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Number of lines in readme file

64

increased by1.59%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Total package byte prevSize

22443

decreased by-0.19%

No dependency changes