-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta(changelog): Update Changelog for 7.50.0 #7966
Conversation
[Gitflow] Merge master into develop
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
…es logger statements (#7908)
Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
) `stop()` will now flush the eventBuffer before clearing it, as well as removing the session from Session Storage. Due to the flushing, `stop()` is now async. Closes: #7738
Bumps [yaml](https://github.com/eemeli/yaml) from 2.1.1 to 2.2.2. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.1.1...v2.2.2) --- updated-dependencies: - dependency-name: yaml dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
Not sure where I got the `closed` stuff from, but this seems to be actually correct based on https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads#issues.
Now, a session will only expire & trigger a new session if no user activity happened for 15min. After 5min of inactivity, we will pause recording events. If the user resumes in the next 10 minutes, we'll resume the session, else re-create it if they resume later.
46e80b2
to
f2fc8f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This changelog seems pretty lengthy, could we shorten it - or create another doc that users can go read if they are interested?
33af9a1
to
7ceb4a3
Compare
I extracted some of it out into the readme of replay and linked there! |
7ceb4a3
to
b5acd75
Compare
* feat: Add `startBuffering()` API to begin replay buffering. This is useful if you turn off `replaysSessionSampleRate` and `replaysOnErrorSampleRate` and want to manually decide when to start replay buffering. You can then call `flush()` to save the replay. * fix: Sample at a per error rate instead of per session rate. Previously we were sampling at a per-session rather than per-error. This means the sampling decision happened prior to any error occurrence. The sampling rate was not accurate if you had sessions with many errors. This is now changed so that in the case of capturing replays only on error, we begin buffering the replay immediately and only run the sampling decision when an error occurs.
b5acd75
to
cd7bf97
Compare
cd7bf97
to
acbafce
Compare
|
size-limit report 📦
|
acbafce
to
4cfe834
Compare
Also one test was actually incorrect.
4cfe834
to
adf3bb0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the last-minute adjustments!
adf3bb0
to
33d044d
Compare
f2c95f9
to
da799e9
Compare
This is a big release!