Zulip

Recent Commits

• Niloth P(14 Oct 26)

  webhooks/docs: Document how integrations support event filtering. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

• Niloth P(14 Oct 26)

  test_classes: Require webhooks with event types to pass them. For webhooks that support event filtering: - WebhookTestCase already checks that the event type is declared. - This new check ensures they respect it by including the event_type in every call to check_send_webhook_message. New Relic's warning on a misconfigured payload template isn’t event‑bound, so it now passes complete_event_type=None explicitly. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

• Niloth P(14 Oct 26)

  integration-docs: Add missing event-filtering sections. For the integrations that support event-filtering. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

• Niloth P(14 Oct 26)

  webhooks: Fix event filters being ignored. Fixes #40213. Co-Authored-By: Fadi Romdhan <[email protected]> Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

• Prakhar Pratyush(23 Oct 26)

  portico: Replace the word "logo" with "icon" for communities directory. The directory displays each organization's icon, which `communities_view` fetches with `get_realm_icon_url`, but calls it a "logo" everywhere when used in the template. An organization's logo is a different image, served by `get_realm_logo_url`. This commit replaces the term "logo" with "icon" for communities directory. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Prakhar Pratyush <[email protected]>

• Shubham Padia(13 Oct 26)

  skills: Add evals for the write-changelog skill. These let an agent check a change to the skill's wording, or a new model, against changelog entries the maintainers published. The README gives the cases, the procedure and the prompts. There is no runner script. An agent can write one from the README. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Shubham Padia(09 Oct 26)

  skills: Keep write-changelog maintenance entries short. Entries drafted for maintenance releases were longer than the published ones. They explained how a bug happened and how it was fixed, and named internals like migration numbers. Tell the skill to describe only the effect, in one clause of about ten words. Before finishing, it shortens entries that are clearly longer than those in the previous maintenance release. The rule is in the maintenance release section only. As a general style rule, it made the skill shorten existing major release bullets, which made some of them wrong. Evals on the same releases chose this rule. A model compared the old and new skill's entries with the published entry, and picked the new one about 60% of the time. Example entries and a subagent that edits the draft did not help. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Shubham Padia(09 Oct 26)

  skills: Check write-changelog entries against their commits. The skill wrote entries that sounded right but misstated a detail. For example, it wrote "Fixed a crash in the organization exports UI" for a bug where the data exports panel failed to load. Add a step where a fresh subagent reads the diffs and tries to refute each new entry. Also add a check of existing bullets that the update rewords, or that state a limitation, since those were written against older code. The step was chosen with evals on six past maintenance releases. A model drafted each release's section with a candidate skill, and a second model checked every entry against the code. It flagged 6% of the entries from the old skill, and about 1% with the subagent step. Asking the drafter to check its own entries made no difference. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Shubham Padia(19 Oct 26)

  marketing: Track which marketing buttons get clicked. Google Analytics doesn't record clicks on links within our site. So it can't tell which "Get started" button on /slack-alternative/ people use, since they all go to /. Elements with the analytics-click class now send a marketing_click event with their data-button-id. The ID needs to be registered as a custom dimension in Google Analytics before it shows up in reports. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Shubham Padia(04 Sept 26)

  marketing: Link to the Slack alternative page. Add links from the footer, the home page, and /why-zulip/, so that the new page is reachable from the rest of the site and gets crawled. The Product menu entry is left for a follow-up once the page is deployed, because the marketing nav uses absolute zulip.com URLs, and the documentation crawler checks those against the live site. Co-Authored-By: Claude Fable 5.1 <[email protected]>

• Shubham Padia(04 Sept 26)

  marketing: Add /slack-alternative/ landing page. This page is for people who are looking for an alternative to Slack and don't know Zulip yet. The title and description lead with "Slack alternative", with Zulip only as a suffix, since the target reader isn't searching for Zulip yet. The customer logos are the same images the home page uses. They live in svg_icons.css, which is about 120KB. The other marketing pages don't need that file, so this page gets its own webpack bundle instead of adding the file to the shared marketing-page bundle. This page caps feature images at their container width to prevent overflow on narrow screens. Other marketing pages can be addressed in a follow-up issue. Co-Authored-By: Claude Fable 5.1 <[email protected]>

• Shubham Padia(10 Sept 26)

  marketing: Share the alternating section background rule. This is a prep commit for the next commit. Co-Authored-By: Claude Fable 5.1 <[email protected]>

• Shubham Padia(22 Oct 26)

  portico: Share the home page quote text color. Move the quote text color into portico_variables.css, so that other marketing pages can use it too. The home page now loads that file. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Shubham Padia(22 Oct 26)

  portico: Crop empty space from the Pilot client logo. The Pilot logo SVG had about 23px of empty space on every side. This makes the logo look small when it's scaled to fit a box. /hello looks the same, because it centers the logo at its natural size. Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Alex Vandiver(16 Oct 26)

  help: Fall back to unoptimized images if sharp cannot load. The prebuilt sharp binaries refuse to load on CPUs without x86-64-v2 support. This includes older hardware, as well as virtual machines using a generic CPU model such as kvm64 on newer hardware. Astro reports this as "MissingSharp: Could not find Sharp", hiding sharp's actual "Unsupported CPU" error, and the help center build failure aborts the upgrade. Since bundled releases include a pre-built version of the help center, this failure mode only occurs when upgrading with `upgrade-zulip-from-git`. If sharp fails to load, build the help center with Astro's passthrough image service, and print sharp's "Unsupported CPU" error so the cause is discoverable. For these virtualized or older hosts, help center images are served as the original unoptimized PNGs rather than as optimized WebP, at slightly higher filesize (currently a sum of 1.38MB, vs 533KB). Co-Authored-By: Claude Opus 5.5 <[email protected]>

• Evy Kassirer(12 Oct 26)

  events: Use pydantic types for message and update_message events. These are the last events built as dicts. Both carry the per-recipient notification inputs that process_message_event and process_message_update_event consume and never forward. The message event always sets them, so they are required there; update_message sets them only for content edits, so they are optional there. The message event is not a subclass of the model clients receive: its message field is the message id and message_dict the wide dict, which Tornado finalizes per client. The update_message event shares UpdateMessageOptionalFields with the model clients receive, split out of UpdateMessageEvent for that purpose, and declares the required fields itself: it leaves out flags, which Tornado adds per recipient, and makes message_ids optional, since do_update_message only knows it after applying the edit to every affected message. The event is otherwise filled in by attribute assignment where the dict used to be mutated. propagate_mode gets a PropagateMode alias in zerver.lib.types so the view, the edit request and the event agree on its type. The tests that mock send_event_on_commit read the event as an object now instead of a dict. Co-Authored-By: Claude Fable 5.1 <[email protected]>

• sandeep(07 Sept 26)

  settings: Structure the notification sound preview as a button. The control was a '<span>' with a click handler, so it could not be reached from a keyboard. Render it with the 'icon_button' component instead, which also lets the flex row center it without the 'line-height' hack. Fixes part of #36224.

• sandeep(07 Sept 26)

  icons: Replace FontAwesome icons with Zulip icons in settings. Replace decorative FontAwesome icons in the settings panels with their Zulip equivalents: - 'fa-ellipsis-v' to 'zulip-icon-grip-vertical' - 'fa-info-circle' to 'zulip-icon-info' - 'fa-question-circle' to 'zulip-icon-help' - 'fa-play-circle' to 'zulip-icon-play-circle' The drag handles used two 'fa-ellipsis-v' icons side by side. A single 'zulip-icon-grip-vertical' draws the same two columns of dots, and is already the drag handle in the poll and todo modals. The Zulip glyphs are drawn at a different scale, so the icons are resized and seated against the text beside them. The info icons swap their 'position: relative' nudge for a 'vertical-align' that scales with the label or heading, leaving one mechanism instead of two. All four info icons now carry 'aria-hidden'; they only open a tooltip beside a label that already names the setting. Fixes part of #36224.

• sandeep(07 Sept 26)

  icons: Redesign play-circle.svg to match the other circular icons. The icon was drawn at 24x24 with strokes, so it looked bolder than the 16x16 filled circular icons beside it, like 'help' and 'info'. Redraw it at 16x16 as a filled icon. This changes it everywhere: the user card and personal menu popovers today, and the notification sound preview once that moves to it. Fixes part of #36224.

• Ishan Kumar(13 Oct 26)

  recent_view: Remove unused filter_muted template parameter. The "Include muted" filter button was replaced by the topic filter dropdown in 1e7b4ae160, and recent_view_filters.hbs no longer reads filter_muted, so stop passing it.

• Sahil Batra(21 Oct 26)

  bots: Fix owner change text in reactivation modal. The statement to unsubscribe bot from accessible streams when the owner is being changed after reactivation is no longer true after e57c43b705.

• Anders Kaseorg(21 Oct 26)

  requirements: Upgrade Python requirements. Signed-off-by: Anders Kaseorg <[email protected]>

• Anders Kaseorg(21 Oct 26)

  ruff: Fix RUF071 `os.path.commonprefix()` compares strings character-by-character. Signed-off-by: Anders Kaseorg <[email protected]>

• Anders Kaseorg(21 Oct 26)

  install-uv: Upgrade uv from 0.12.19 to 0.13.4. Signed-off-by: Anders Kaseorg <[email protected]>

• Pinank Shah(04 Sept 26)

  typeahead: Use grid layout for typeahead content. Replace the flex layout with named grid areas for the optional leading icon or avatar and the typeahead text content. Use a single content column for suggestions without a leading icon so text-only entries do not reserve an empty column or extra gap. Fixes #37030.

• Karl Stolley(12 Oct 26)

  subscriptions: Keep focus ring within button area.

• Karl Stolley(12 Oct 26)

  subscriptions: Target icon for desired size.

• Shubham Padia(30 Jun 26)

  markdown: Match topic-link rendering in the web app local echo. Mirror the backend change in the web app's Markdown so local echo and the server's stored render agree: handleStreamTopic and handleStreamTopicMessage now leave a non-empty topic link as plain text when the channel only allows the empty topic. The check is exposed to the shared Markdown code via a new is_empty_topic_only_channel helper on MarkdownHelpers, wired in the web app to stream_data.is_empty_topic_only_channel. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

• Shubham Padia(30 Jun 26)

  markdown: Don't linkify named topics in empty-topic-only channels. A `#**channel>topic**` (or `…@id`) link to a non-empty topic in an empty-topic-only channel points at a topic that can never receive messages, so we now leave such syntax as plain text rather than linkifying it. This is safe because validate_topics_policy refuses to set empty_topic_only while the channel has messages in named topics, so these channels can never contain a valid non-empty topic. To do this, the stream-topic handlers check the channel's effective topics_policy. The mention backend already caches a ChannelInfo for each linked channel, so it now also records the channel's topics_policy there. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

• Shubham Padia(30 Jun 26)

  composebox_typeahead: Show empty-topic completion only on ">". An empty-topic-only channel can never contain a non-empty topic, so a link to a named topic in one is dead: clicking it narrows to a phantom topic in the left sidebar while the compose box falls back to the empty ("general chat") topic. Such channels therefore never offer named-topic completion. Selecting one inserts the complete channel link with no topic typeahead reopened by default; pressing ">" is the explicit request for a topic and inserts the partial `#**channel>` syntax, whose completion offers just the channel's single empty topic. Named-topic links can no longer be created for these channels, while the empty-topic link stays reachable. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>