Skip to content

Releases: getsentry/sentry

25.8.0

15 Aug 18:53
Compare
Choose a tag to compare

Various fixes & improvements

  • fix(ci): Push docker image on release branches (#97936) by @hubertdeng123
  • fix(explore): Insert group bys before visualizes if possible (#97923) by @Zylphrex
  • feat(logs): Support multiple visualizes and groupbys in logs (#97912) by @Zylphrex
  • ref(dashboards): make WidgetCardChart functional (#97885) by @lzhao-sentry
  • feat(summarization): Route s4s traffic to new pod (#97926) by @Mihir-Mavalankar
  • aci(feat): Use propagated timestamp to track triggering latency (#97612) by @kcons
  • feat(detectors): Update detection algorithm for MN+1 Experimental Detector (#97533) by @roggenkemper
  • fix(aci): Make rule/workflow redis buffer interactions non-transactional (#97917) by @kcons
  • ref: remove coreapi, use ParseError in sentry_app logic (#97913) by @JoshFerge
  • chore(cell-actions): use popper strategy fixed instead of portalling (#97593) by @lzhao-sentry
  • ref(replay): Refactor how we refresh bulk delete notifications (#97893) by @ryan953
  • feat(replay): Add a dropdown to make it easier to select replays inside stories (#97713) by @ryan953
  • feat(otlp): Collapse Trace Waterfall spans based on span name (#97706) by @gggritso
  • feat(otlp): Use name attribute in more spaces in the span waterfall (#97704) by @gggritso
  • ref: move codeowners endpoints into issues module (#97916) by @JoshFerge
  • ref(groupingInfo): Hide client fingerprint in Contributing Values view if it doesn't contribute (#97904) by @shayna-ch
  • ref(groupingInfo): add highlight to contributing values when All Values is set (#97812) by @shayna-ch
  • ref(issues): improve similar issues stacktrace diff (#97645) by @shayna-ch
  • chore: add good example of SENTRY_DISALLOWED_IPS (#97847) by @oioki
  • feat(trace-eap-waterfall): Exclude missing instrumentation nodes from FE traces (#97879) by @Abdkhan14
  • ref(cell-actions): better interactions for ID and clearer menu indication (#97888) by @lzhao-sentry
  • 🏃 perf(aci): measure trigger action execution time (#97918) by @iamrajjoshi
  • chore(autofix): add more copy button content (#97891) by @roaga
  • feat(autofix): Show error message when drafting PR (#97867) by @roaga

Plus 1946 more

25.7.0

15 Jul 17:30
Compare
Choose a tag to compare

Various fixes & improvements

Plus 670 more

25.6.2

30 Jun 22:00
Compare
Choose a tag to compare

Various fixes & improvements

Plus 519 more

25.6.1

20 Jun 21:56
Compare
Choose a tag to compare

Various fixes & improvements

Plus 105 more

25.6.0

18 Jun 16:31
Compare
Choose a tag to compare

Various fixes & improvements

Plus 1454 more

25.5.1

21 May 15:27
Compare
Choose a tag to compare

Various fixes & improvements

Plus 231 more

25.5.0

15 May 18:32
Compare
Choose a tag to compare

Various fixes & improvements

  • chore(perf-issues): Add a flag and check it to allow customer to disable detectors (#91734) by @leeandher
  • feat(trace-tabs-ui): Adding ops to search on click and hiding trace level ops breakdown (#91684) by @Abdkhan14
  • build(ui): Add rspack as webpack alternative (#77077) by @scttcper
  • fix(taskworker) Fix async notification parameter serialization (#91720) by @markstory
  • fix(profiles): Set the proper span entity to insert data to in tests (#91736) by @phacops
  • fix(insights): line of code not working with db module on eap (#91654) by @DominikB2014
  • ref(reserved budgets): Update types + constants (#91606) by @isabellaenriquez
  • feat(taskworker) Check 2% of tasks for pickle (#91624) by @markstory
  • chore(github): Only support pagination for getting labels (#91570) by @armenzg
  • Skip test_queries_profile_candidates_from_spans (#91724) by @armenzg
  • fix(issue-details): Avoid persisting stacktrace folding behaviour (#91719) by @leeandher
  • feat(dashboards): Newly added widgets should scroll into view (#91721) by @narsaynorath
  • ref(crons): Use dateAdded over dateCreated (#91667) by @evanpurkhiser
  • fix(utils): return 0% for null and undefined values in formatpercentage (#91710) by @shellmayr
  • ref: fix nullability of requires_org_level_access (#91694) by @asottile-sentry
  • feat(explore): Flatten visualize yaxes into multiple (#91664) by @Zylphrex
  • fix(widget-library): Hide filters at top of panel if not small screen (#91716) by @narsaynorath
  • feat(attachments): Include all attachment with screenshot in name (#91602) by @armenzg
  • fix(insights): show - instead of null when metric value is null (#91656) by @DominikB2014
  • feat(ourlogs): Add a "new" badge for logs in the sidebar (#91674) by @colin-sentry
  • fix(nextjs-insights): remove project icon from rage/dead click widget (#91711) by @shellmayr
  • fix(nextjs-insights): show 0% for failure_rate()==0 instead of <0% (#91709) by @shellmayr
  • feat(nextjs-insights): add avg & p95 duration to navigations table (#91708) by @shellmayr
  • fix(sandbox): for debugging add telex org to exclude from redirect (#91704) by @constantinius

Plus 1819 more

25.4.0

15 Apr 22:00
Compare
Choose a tag to compare

Automate Code Mappings & In-App Stack Trace Rules for Java projects (ongoing)

Currently, we ask developers to set up their Java code mappings manually (because the SDK cannot determine it):
https://docs.sentry.io/platforms/java/source-context/#setting-up-code-mappings

Unfortunately, many stack traces do not contain in-app frames, thus, many Sentry features are not available (e.g. SCM linking, suspect commit).

This tracks using the code mappings derivation system to automatically add the code mappings and stack trace rules to mark in-app frames as such.

This will automatically enable the following Sentry features :

  • Suspect Commits
  • GitHub pull request comments
  • Auto-assignments (if Codeowners imported)
  • Stack trace linking
  • Code coverage (if the customer also has an account)

This will only be available to customers with the GitHub integration installed.

You can read more about the system here:
https://blog.sentry.io/code-mappings-and-why-they-matter/

By: @armenzg (#89389, #89302, #89211, #88952, #88787, #88676, #88673, #88557, #88475, #88440, #88372, #88251, #88087, #88073, #87842, #87915, #87912, #87776, #87630, #87581, #87437, #87498, #87399, #86598)

Various fixes & improvements

Plus 2007 more

25.3.0

17 Mar 17:13
Compare
Choose a tag to compare

Automate Code Mappings & In-App Stack Trace Rules for Java projects (ongoing)

Currently, we ask developers to set up their Java code mappings manually (because the SDK cannot determine it):
https://docs.sentry.io/platforms/java/source-context/&#35;setting-up-code-mappings

Unfortunately, many stack traces do not contain in-app frames, thus, many Sentry features are not available (e.g. SCM linking, suspect commit).

This tracks using the code mappings derivation system to automatically add the code mappings and stack trace rules to mark in-app frames as such.

This will automatically enable the following Sentry features :

  • Suspect Commits
  • GitHub pull request comments
  • Auto-assignments (if Codeowners imported)
  • Stack trace linking
  • Code coverage (if the customer also has an account)

This will only be available to customers with the GitHub integration installed.

You can read more about the system here:
https://blog.sentry.io/code-mappings-and-why-they-matter/

By: @armenzg (#86283, #86327, #86280, #86196, #86188, #86189, #86109, #86026, #85981, #85976, #85931, #85742)

Various fixes & improvements

Plus 1390 more

25.2.0

18 Feb 19:23
Compare
Choose a tag to compare

Automate Code Mappings & In-App Stack Trace Rules for Java projects (ongoing)

Currently, we ask developers to set up their Java code mappings manually (because the SDK cannot determine it):
https://docs.sentry.io/platforms/java/source-context/&#35;setting-up-code-mappings

Unfortunately, many stack traces do not contain in-app frames, thus, many Sentry features are not available (e.g. SCM linking, suspect commit).

This tracks using the code mappings derivation system to automatically add the code mappings and stack trace rules to mark in-app frames as such.

This will automatically enable the following Sentry features :

  • Suspect Commits
  • GitHub pull request comments
  • Auto-assignments (if Codeowners imported)
  • Stack trace linking
  • Code coverage (if the customer also has an account)

This will only be available to customers with the GitHub integration installed.

You can read more about the system here:
https://blog.sentry.io/code-mappings-and-why-they-matter/

By: @armenzg (#85174, #85065)

Various fixes & improvements

Plus 1429 more