Skip to content

Release notes for 26/05#267

Open
chris-absmartly wants to merge 5 commits into
masterfrom
26/05-2
Open

Release notes for 26/05#267
chris-absmartly wants to merge 5 commits into
masterfrom
26/05-2

Conversation

@chris-absmartly
Copy link
Copy Markdown
Collaborator

@chris-absmartly chris-absmartly commented May 22, 2026

Summary by CodeRabbit

Release Notes

  • New Features

    • Metric Changelog: Complete audit trail with field-level diffs per metric
    • Activity per Period metric type for frequency measurement normalised to configurable time windows
    • Keyboard navigation enhancement for Event Details dialog
    • Custom Assignments (exclusion rules) in early beta for JavaScript SDK
  • Documentation

    • Added Warehouse-native deployment glossary term
    • New Activity per Period metric documentation with configurable options and usage guidance

Review Change Stack

@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for absmartly-docs ready!

Name Link
🔨 Latest commit e23acb6
🔍 Latest deploy log https://app.netlify.com/projects/absmartly-docs/deploys/6a104b4340fe2f00089bab90
😎 Deploy Preview https://deploy-preview-267--absmartly-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 22, 2026

Warning

Rate limit exceeded

@chris-absmartly has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 38 minutes and 57 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e79ee0dd-b532-418b-9799-6a19ac1dc0d1

📥 Commits

Reviewing files that changed from the base of the PR and between 10489fe and e23acb6.

⛔ Files ignored due to path filters (1)
  • static/img/release-notes/metric-changelog.png is excluded by !**/*.png
📒 Files selected for processing (2)
  • docs/platform-release-notes/2026/05.mdx
  • docs/web-console-docs/experiments/creating-an-experiment.mdx

Walkthrough

This pull request adds comprehensive documentation for ABsmartly's May 2026 product updates. It introduces a new Activity per Period metric type with standalone documentation, publishes release notes covering multiple features including Metric Changelog (audit trail with field-level diffs), improved metrics discoverability, keyboard navigation in Event Details, and early-beta Custom Assignments for the JavaScript SDK. The PR updates existing feature guidance to clarify the limited beta status and enablement requirements for Custom Assignments, and expands the glossary with a Warehouse-native entry describing warehouse-native deployment architecture.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • absmartly/docs#266: Adds comprehensive Warehouse Native overview, getting started, and category pages that complement the Warehouse-native glossary term introduced in this PR.

Suggested reviewers

  • bmsilva
  • mario-silva
  • calthejuggler
  • marcio-absmartly

Poem

📚 A glossary grows, features find their page,
May's release notes shine through the docs we engage,
Metrics find periods, assignments take flight,
Warehouses native—our data held tight! 🐰✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title "Release notes for 26/05" is directly related to the primary changes in the pull request, which consist entirely of release notes documentation updates for May 2026.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 26/05-2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/platform-release-notes/2026/05.mdx (1)

88-88: ⚡ Quick win

Add missing final newline.

The file should end with a newline character for POSIX compliance and better Git diffs.

📝 Proposed fix
 We're always happy to help, so reach out if you have any questions or want to explore how to make the most of these new capabilities.
+
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/platform-release-notes/2026/05.mdx` at line 88, The MDX release notes
file is missing a final newline character at EOF; open the 05.mdx document and
add a single trailing newline character at the end of the file so it ends with a
newline (POSIX-compliant), then save and commit the change.
docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx (1)

58-58: ⚡ Quick win

Add missing final newline.

The file should end with a newline character for POSIX compliance and better Git diffs.

📝 Proposed fix
 - Ideal for experiments aimed at **engagement, habit formation, or retention frequency** — onboarding flows, notifications, recommendation systems, or loyalty mechanics.
+
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx`
at line 58, The file is missing a trailing newline at EOF; open the "Activity
per Period" metric page source and ensure the document ends with a single POSIX
newline character (add an empty line after the last content) so the file
terminates with '\n' to satisfy POSIX/Git expectations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/platform-release-notes/2026/05.mdx`:
- Line 23: The list item containing "**Identity**, **Details**, **Definition**
**Goal**" is missing proper punctuation between "Definition" and "Goal"; update
the text in that list entry so the section names are unambiguous—either insert a
comma to make "**Definition**, **Goal**" if they are separate sections, or
collapse them into a single section name like "**Definition Goal**" (or adjust
bolding to reflect the intended single-section string); edit the same list line
to ensure consistent comma separation for all items such as "**Identity**,
**Details**, **Definition**, **Goal**" if there are four sections.

---

Nitpick comments:
In `@docs/platform-release-notes/2026/05.mdx`:
- Line 88: The MDX release notes file is missing a final newline character at
EOF; open the 05.mdx document and add a single trailing newline character at the
end of the file so it ends with a newline (POSIX-compliant), then save and
commit the change.

In
`@docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx`:
- Line 58: The file is missing a trailing newline at EOF; open the "Activity per
Period" metric page source and ensure the document ends with a single POSIX
newline character (add an empty line after the last content) so the file
terminates with '\n' to satisfy POSIX/Git expectations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8cb1b4ab-487d-41e8-8d8e-f89a7dcd07a5

📥 Commits

Reviewing files that changed from the base of the PR and between a2ba37e and 10489fe.

⛔ Files ignored due to path filters (1)
  • static/img/release-notes/metric-changelog.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • docs/glossary.mdx
  • docs/platform-release-notes/2026/05.mdx
  • docs/web-console-docs/experiments/creating-an-experiment.mdx
  • docs/web-console-docs/goals-and-metrics/metrics/metric-types/activity-per-period.mdx

- **When** it happened (relative time, with the exact timestamp on hover)
- **Which metric version** the change produced
- **A short summary** of the change (e.g. _Changed owners_, _Added metadata_)
- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify the section list formatting.

The list of collapsible sections appears to be missing proper punctuation or formatting between "Definition" and "Goal". This should likely be either:

  • "Definition, Goal" (if these are separate sections), or
  • Verify if "Definition Goal" is a single section name
📝 Proposed fix (if separate sections)
-- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators
+- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition**, **Goal**, with clear add/remove indicators
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition** **Goal**, with clear add/remove indicators
- **Field-level before/after diffs**, grouped into collapsible sections such as **Identity**, **Details**, **Definition**, **Goal**, with clear add/remove indicators
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/platform-release-notes/2026/05.mdx` at line 23, The list item containing
"**Identity**, **Details**, **Definition** **Goal**" is missing proper
punctuation between "Definition" and "Goal"; update the text in that list entry
so the section names are unambiguous—either insert a comma to make
"**Definition**, **Goal**" if they are separate sections, or collapse them into
a single section name like "**Definition Goal**" (or adjust bolding to reflect
the intended single-section string); edit the same list line to ensure
consistent comma separation for all items such as "**Identity**, **Details**,
**Definition**, **Goal**" if there are four sections.

Demote Custom Assignments (Exclusion Rules) from H2 to H3 so it lives
inside the Audiences section instead of being a peer to it.
Replace with the latest version showing teams/tags/category/applications diff.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant