Releases: sergiitk/pagerbeauty
Releases · sergiitk/pagerbeauty
v1.1.1
1.1.1 (2020-07-12)
Cleanup
- 143 chore-dependencies Docker: Upgrade node to 12.18.2
- 145 chore-dependencies Major npm dependency upgrades
- 144 chore-dependencies Non-major dependencies upgrade
Security
- 139 CVE-2020-7597 Bump codecov from 3.6.1 to 3.6.5
- 140 CVE-2020-7598 Bump acorn from 6.4.0 to 6.4.1
- 141 GHSA-jmqm-f2gx-4fjv Bump npm-registry-fetch from 4.0.2 to 4.0.5
v1.1.0
v1.0.3
1.0.3 (2020-01-21)
Cleanup
- 130 chore-dependencies Major dependencies upgrade
- 128 chore-dependencies Major node upgrade node to the last LTE: 12.14.1
- 129 chore-dependencies Non-major dependencies upgrade
Security
- 115 CVE-2019-10744 Bump lodash from 4.17.11 to 4.17.14
- 114 CVE-2019-10744 Bump lodash.merge from 4.6.1 to 4.6.2
- 118 CVE-2019-10746 Bump mixin-deep from 1.3.1 to 1.3.2
- 117 CVE-2019-15657 Bump eslint-utils from 1.3.1 to 1.4.2
- 127 CVE-2019-19919 Bump handlebars from 4.1.2 to 4.7.2
v1.0.2
1.0.2 (2019-06-12)
Cleanup
- 109 chore-dependencies Dependencies upgrade
Documentation
Security
- 108 www.npmjs.com/advisories/813 Bump js-yaml from 3.12.2 to 3.13.1
- 106 www.npmjs.com/advisories/886 Bump fstream from 1.0.11 to 1.0.12
- 107 www.npmjs.com/advisories/755 Bump handlebars from 4.1.0 to 4.1.2
v1.0.1 April Fools': Wanted mode
What's this do?
- Changes on-call look to this:
You can see it live here: https://pagerbeauty.herokuapp.com/v1/schedules/PJ1P5JQ.html
(this will go back to the normal view after April 1st)
How to use it
Follow regular deployment instructions: https://github.com/sergiitk/pagerbeauty, with but deploy April Fools' version:
Docker
Use sergiitk/pagerbeauty:1.0.1-aprilfools:
docker run --rm -p 8080:8080 --env-file=.env -it sergiitk/pagerbeauty:1.0.1-aprilfools
Heroku / other git-based deployments
Deploy v1.0.1-aprilfools tag or april-fools-style branch.
FAQ
What about ongoing incident view?
It stays the same so you don't miss your alerts.
Is this stable?
Yes, it's based on v1.0.1 with minor style changes
How to turn it off?
Deploy the latest version: v1.0.1.
Why won't it turn off automatically after April 1st?
Figuring out when you want to run it is difficult because of different timezones, so we give you the full control through publishing it as a separate version.
Ref #97
v1.0.1
v1.0.0
1.0.0 (2019-02-07)
Bug Fixes
- 79 core Fix error handling on unknown schedules
- 80 ui-oncalls Handle one user in the rotation (no end date)
Cleanup
- 75 chore-dependencies Dependencies upgrade
- 64 chore-dependencies Dependencies upgrade
- 83 chore-dependencies Dependencies upgrade
- 87 circleci Move test key from secrets to allow exogenous PRs
- 70 core Load Schedules separately from OnCalls
- 69 core Move schedule loading out of web controller
- 65 misc-local-dev Acceptance tests in Docker
- 62 misc-release Automated Docker image builds with basic sanity checks
- 71 misc-release Improve Semantic Release
- 66 misc-release Run acceptance tests in CircleCI
- 68 tests Better test reports
- 67 tests Setup unit test tools and refactor acceptance tests
Documentation
- 78 deploy Document deploying PagerBeauty to Heroku
- 90 readme Add PagerBeauty on Grafana Dashboard screenshot
- 86 readme Fix minor typo
- 89 readme Update Adding to Datadog dashboard gif
- 85 readme Update caps on Datadog
Features
- 73 core-incidents Poll for active incidents
- 72 core-oncalls Removes implicit limit on how many on-calls can be loaded
- 77 core-web HTTP server can be started on custom port
- 82 core-web Support for Authentication Bearer access_token
- 88 grafana Support Grafana
- 74 ui-oncalls On-call active incident view: show incident info and make red