Skip to content

feat(inbound-filters): Hint at release version comparisons in custom filters - #125878

Draft
shellmayr wants to merge 3 commits into
masterfrom
shellmayr/feat/semver-inbound-filter-frontend
Draft

shellmayr wants to merge 3 commits into
masterfrom
shellmayr/feat/semver-inbound-filter-frontend

Conversation

@shellmayr

@shellmayr shellmayr commented Sep 29, 2026 •

Copy link
Copy Markdown
Member
  • The release placeholder and the modal hint in the custom filter modal now say that a plain version such as 2.41.0, or a value with a leading comparator such as >=2.41.0, compares versions instead of matching the text.
  • The hint says a comparison applies to every package in the project unless the value names one, e.g. >=myapp@2.0.
  • No behavior change in the UI. The API detects the comparison, see feat(inbound-filters): Add semver based inbound filters for releases #125877, which lands first.

…filters

The custom filter API now compares versions for a release value that starts
with a comparator such as >=2.41.0. Say so in the modal hint and in the
release placeholder, next to the glob syntax.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Sep 29, 2026
…risons

A comparison without a package applies to every package in the project. Say
so in the modal hint, and show how to name one.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

This branch was successfully deployed

1 active deployment
Preview — c25e630b Deployed Sep 29, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant