Releases: getsentry/relay
Releases · getsentry/relay
0.4.3
For users of relay, nothing changed at all. This is a release to test embedding
some Rust code in Sentry itself.
0.4.2
For users of relay, nothing changed at all. This is a release to test embedding
some Rust code in Sentry itself.
0.4.1
For users of relay, nothing changed at all. This is a release to test embedding
some Rust code in Sentry itself.
0.4.0
Introducing Relay modes:
proxy
: A simple proxy for all requests and events without configuration.
static
: Static configuration for known projects in the file system.
managed
: Fetch configurations dynamically from Sentry and update them.
The default Relay mode is managed
. Users upgrading from previous versions will
automatically transition to the managed
mode. To change this setting, add
relay.mode
to config.yml
or run semaphore config init
from the command
line.
Breaking Change: If Relay was used without credentials, the mode needs to be
set to proxy
. The default managed
mode requires credentials.
For more information on Relay modes, see the documentation page.
0.3.5
- store: Drop internal attributes during normalization (
metadata
, hashes
)
- store: Write more stuff into
event.errors
- store: Fix
frame.filename
truncation to match python limits
0.3.4
This release was primarily done because publishing 0.3.3 failed.
0.3.2
- Fix bug in store that would throw away all context lines.
0.3.1
- No longer check required attributes in relay, only in store.
- store: Minor fixes to be closer to Python. Ability to disable trimming of
objects, arrays and strings.
0.3.0
- Changed PII stripping rule format to permit path selectors when applying
rules. This means that now $string
refers to strings for instance and
user.id
refers to the id
field in the user
attribute of the event.
Temporarily support for old rules is retained.
0.2.7
- store: Minor fixes to be closer to Python. Ability to disable trimming of
objects, arrays and strings.