Skip to content

Commit

Permalink
Bump to version 2.5.0
Browse files Browse the repository at this point in the history
  • Loading branch information
OsamaSayegh committed Dec 12, 2019
1 parent 24d6cc9 commit 94e4808
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 3 deletions.
8 changes: 8 additions & 0 deletions CHANGELOG.md
@@ -1,5 +1,13 @@
# CHANGELOG

- 2019-12-12: 2.5.0

- DEV: Update to latest version of gems
- FIX: when rate limiting return an object responding to each
- FEATURE: Expose the search phrase in query params
- DEV: Update minor frontend dependencies
- FEATURE: Custom grouping patterns

- 2019-10-28: 2.4.2

- FIX: wrong number of arguments when adding message using a block (#98)
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -43,7 +43,7 @@ Logster can be configured using `Logster.config`:
- `Logster.config.enable_js_error_reporting` : enable js error reporting from clients
- `Logster.config.rate_limit_error_reporting` : controls automatic 1 minute rate limiting for JS error reporting.
- `Logster.config.web_title` : `<title>` tag for logster error page.
- `Logster.config.enable_custom_patterns_via_ui` : enables a setting page that allows adding suppression patterns via the UI.
- `Logster.config.enable_custom_patterns_via_ui` : enable the settings page (`/settings`) where you can add suppression and grouping patterns.
- `Logster.config.maximum_message_size_bytes` : specifiy a size in bytes that a message cannot exceed. Note this isn't 100% accurate, meaning a message may still grow above the limit, but it shouldn't grow by more tha, say, 2000 bytes.

### Tracking Error Rate
Expand Down
2 changes: 1 addition & 1 deletion assets/javascript/client-app.js

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion lib/logster/version.rb
@@ -1,5 +1,5 @@
# frozen_string_literal: true

module Logster
VERSION = "2.4.2"
VERSION = "2.5.0"
end

0 comments on commit 94e4808

Please sign in to comment.