Skip to content

Fold the custom-alert follow-ups (tag scope, range operators, last-fired) into the changelog - #3374

Merged
erikdarlingdata merged 1 commit into
devfrom
chore/custom-alert-followups-changelog
Sep 12, 2026
Merged

Fold the custom-alert follow-ups (tag scope, range operators, last-fired) into the changelog#3374
erikdarlingdata merged 1 commit into
devfrom
chore/custom-alert-followups-changelog

Conversation

@erikdarlingdata

Copy link
Copy Markdown
Owner

Documentation only. Consolidated update to the #3285 [Unreleased] Added bullet now that the three follow-up slices shipped (one post-wave splice per the changelog batching rule):

Byte-precise edit, CRLF preserved (3677 → 3677, 0 bare CR), one line changed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WejwpgWF5Xfm3fAmoEbFz4

…red) into the changelog

The #3285 [Unreleased] "Added" bullet now reflects the three slices that
shipped after the initial entry: tag scope (#3350/#3366 -> "a fleet tag"),
the between/outside range operators (#3351/#3371 -> "or a range, within or
outside a band"), and the last-fired time on the rule cards (#3360/#3370).
Documentation only; one line changed, CRLF preserved.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WejwpgWF5Xfm3fAmoEbFz4
@claude

claude Bot commented Sep 12, 2026

Copy link
Copy Markdown

Reviewed. This is a documentation-only edit (1 line changed in CHANGELOG.md, no code) that folds three follow-up features into the existing #3285 Added bullet in [Unreleased].

Verified:

No correctness, parity, security, or performance concerns — there's no code in this diff to affect Lite/Darling parity. Nothing to flag.

@erikdarlingdata
erikdarlingdata merged commit 339a88a into dev Sep 12, 2026
8 checks passed
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