Releases: cognisent/gitlab-slack
Releases · cognisent/gitlab-slack
2.1.3
2.1.2
2.1.1
2.1.0
2.1.0 / 2019-03-27
- Remove the use of global
_
,path
,config
and thePromise
override- Switch to using relative path requires for everything
- Remove strange
Object.defineProperty
thing from handlers - Remove
WeakMap
"privates" pattern; I don't think I like it - Update all NPM dependencies to latest versions
- Fix all package vulnerabilities
- Update ESLint rules to a 5.15.x set
- Update branch name parsing to allow for branches with a
/
character in the name - Update all notifications to refer to the project by its
path_with_namespace
(Fixes #26) - Normalize GitLab webhook and API result property uses in several cases
- Change to present tense in changelog (!)
- Change all Bluebird coroutines to
async
/await
and default to native promises- Some Bluebird helper functions are still used
- Change failure during initialization to exit with
1
(Fixes #24)- Improve error reporting for various failures of GitLab API configuration
- Change how source/target branch links are built in merge request notifications (Fixes #23)
- Change the commit notification that accompanies a new branch notification to only include any initial, contiguous block of commits made by the user who pushed. If no commits are left after this filtering, no notification is made. (Fixes #28)
- Change uses of
util.inspect
to only print colors if supports-color says it should - Add local ngrok configuration and NPM script for local development
- Add more settings to the .editorconfig
- Add tag notification for moved tags
- Add commit summary of mentioned merge requests as
/!\d+/
(Fixes #25) - Add comprehensive JSDoc for config
- Add systemd unit script example
2.0.1
2.0.0
2.0.0 / 2017-07-21
I wrote this service only a few months after I had started writing Node.js for the first time. The more time went by, the more what I had written distressed me and became harder to maintain. I finally got some time to rewrite the whole thing, fixing some bugs and adding features in the process. While I'm not willing to send this release to the Ivory Tower, I'm still significantly happier with it.
Enjoy.
Project Changes
- Complete re-write of the whole service from the ground up using ES6 syntax, coroutines, and other delightful, modern things
- Now targeting Node.js 6.x LTS and NPM 5.x
- Added
package-lock.json
- Added
- Designed to work with the v4 GitLab API and other features from GitLab 9.x
- Added
.editorconfig
to enforce line endings and help with Markdown (more info) - Switched from JSHint to ESLint (4.2.0)
- Switched from underscore to lodash (4.17.x)
- Switched to debug for logging and dropped my special logger (Fixes #15)
- In supported terminals, logging output is colored for improved readability
- Updated the
package.json
with some more information and marked the package as private - Updated the
README.md
with new features, up-to-date screenshots and more details- Added a Limitations section that hopefully will cover the constraints of the project
Service Changes
- Added handling for
SIGINT
andSIGTERM
for more graceful exits - Where appropriate, Bluebird coroutines using generator functions are used to simplify asynchronous code
- All code is strict-mode ES6, taking advantage of fun language features where appropriate
- Significant modularization applied to split components into small working parts
- Issue and label caching system slimmed and improved
- Only watched labels are cached rather than all labels of qualifying issues
- All handler code is appropriately connected through uninterrupted promise chains
- Fixes some phantom, unhandled promise return issues and allows Bluebird warnings to remain on 🎉
- Tried using the
WeakMap
"privates" pattern with ES6 classes; I'm still on the fence on this one - Added an attempt at intellingent resolution of GitLab project ID from available information
- When
project_id
is present in webhook objects is inconsistent and this service needs it to look up the project configuration
- When
- Significantly cleaned up and improved HTTP server code
Notification Changes
- Significant simplification and reduction in GitLab API calls due to GitLab increasing what is available in webhook messages
- Added support for merge request notifications
- Added support for wiki page notifications
- When a new-branch message is processed, if it includes any commits, those are also notified (Fixes #14)
- When a tag includes a message, it is notified as well
- Re-ordered first line of issue notification to match data-point order of other notification types
- Issue links no longer duplicate issue mentions found in the first line of commit messages
- Improved Markdown-to-Slack-formatting converter
- Headings that are already bolded will be left as such
- Simplification and tightening up of issue handling and label tracking
1.7.2
1.7.1
1.7.1 / 2016-08-08
- Updated dependencies
- bluebird -> 3.4.1
- request-promise -> 4.1.1 (added request as peer dependency)
- Updated bullet regex to make sure it doesn't match initial bold text (Fixes #18)
- Added unique filter for detected issue mentions (Fixes #17)
- Changed cacheIssueLabels to use map->each with concurrency (Fixes #10)
- Refactored initial loading promise chain error handling to actually work properly
1.7.0
1.7.0 / 2015-12-11
- Fixed some issues with missing configuration not falling back to defaults caused by label tracking changes.
- Fixed image link formatting translation (Fixes #12).
- Reversed the commit list in commit notifications for a more useful display order (Fixes #6).
- Added milestone to issue notification header (Fixes #11).
- Updated README and screenshots for changes and to remove init-flavor-specific instructions.
- Updated bluebird to 3.0.x.
- Changed promisified request out for request-promise.
1.6.0: Added issue label tracking and restructured config file
1.6.0 / 2015-10-19
- Added feature information to the README file. See this file for more information on this version's changes.
- Added issue label tracking (Fixes #7).
- Significantly changed the structure of the config.json file.
- Fixed issue with user resolution of similarly-named users (Fixes #5).
- Removed remaining hard-coded URLs (Fixes #8).