Channel
@medusajs_news
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
24subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002509283466 |
|---|---|
| Type | Channel |
| Username | @medusajs_news |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/medusajs_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 07:39 | 24 | +1 |
| 29 Aug 2026, 01:04 | 23 | +1 |
| 11 Aug 2026, 13:32 | 22 | no change |
| 7 Aug 2026, 22:04 | 22 | first reading |
20 posts held, back to 4 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 June 2026 to 31 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Gorgo just shipped the Integration Module for Medusa Configuring a plugin in Medusa usually means editing medusa-config, keeping secrets in environment variables, and shipping a redeploy for every key change. The new Integration Module removes that chore: a plugin declares its settings once, and admins manage them right in the Admin – no medusa-config edits, no redeploys. 🔗 Links: • Read the announcement • Read…
🔥1
New Integrations Jul'26 The Medusa Integrations Directory adds 14 community plugins across payments, marketplaces, search, ERP, and fulfillment. Key additions include Faire and Etsy sync for catalog and order management, Paytrail for Finnish payments, NMI for multi-method processing, and Klaviyo for event tracking and marketing automation. Additional tools cover authentication (SuperTokens, Better Auth), search (Alg…
Reorder: Open-Source Subscriptions Plugin for Medusa Built as a native Medusa plugin, it uses modules, workflows, scheduled jobs, Admin API routes, and Admin UI extensions, keeping subscriptions alongside orders, carts, payments, and customers without external sync. It includes lifecycle controls, dunning with retries, analytics (MRR, churn, LTV), plans and offers, and scheduler-driven renewals with full history. Se…
Medusa Cloud CLI v0.1.11 Released with Local Builds and Context Naming The update introduces a local build command that replicates the cloud environment using Docker and runs from the project root. CLI-based environment variable management is expanded, enabling direct configuration without the dashboard. It also adds support for named project and environment contexts, improving clarity when switching or scripting wo…
Medusa v2.18 Released with Community Contributions Community activity increased after introducing AI-assisted issue triage and PR review, with monthly contributors rising from ~15 to ~32. Issue resolution improved by about 50%, from ~48 to ~74 closed per month, while open issues dropped to 16. The release focuses on new features, developer experience improvements, and bug fixes driven by these contributions. 🔗 Read…
New Medusa release v2.18.0 New features, bug fixes, and dependency updates improve performance and security. • Breaking: Default load strategy set to BALANCED; delete method return type updated • Improved configurable data tables in Admin dashboard with advanced view options • Orders can be transferred to guest customers from Admin dashboard • Inventory workflows now emit events for subscriptions and side effects • …
Two additions every MCP author should implement Medusa’s MCP server exposes documentation to coding agents and logs where they fail to find answers or encounter inconsistencies. It introduces a feedback tool for agents to report concrete issues, including mismatches between APIs and docs, which are sent to Posthog and routed into Linear. It also adds a context field on tool calls to capture the agent’s intent, helpi…
Learn how to set up testing for Medusa plugins - using Gorgo's own plugins as an example. In the article we break down the different types of tests: unit, integration, and contract. The contract ones hit providers' live APIs every day, and the whole suite runs against the latest Medusa release. That's how we catch breaking changes before they ever reach your stores. 🔗 Read the article #medusajs #gorgojs #blog
New Layout Composer in Medusa Admin Announced The feature is available in Medusa version 2.17.2 and enables drag-and-drop customization across dashboard elements. Users can reorder or hide sections, sidebar items, and top bar elements, including core components. Layouts can be saved as personal preferences or shared as global defaults for all project users. It also supports replacing built-in sections with custom wi…
New Medusa release v2.17.2 The admin dashboard layout is now fully customizable through a reworked Layout Composer. • Added drag-and-drop Layout Composer with persistent admin layout settings • Added async payment methods support across Payment module and workflows • Added quantity-based tiered pricing in Price Lists • Added contextual browser tab titles using route seo resolver • Improved admin layout extensibilit…
Newsletter June 2026 - Versions 2.15.5 through 2.17.1 are out - Global Product Options - Multi-Factor Authentication - Medusa ESLint Plugin: Add guardrails to AI agents - New prompts for the Medusa MCP - Nine new community integrations - Community highlights 🔗 Read more #medusajs #blog #news
New Integrations June 2026 The update adds nine community-built integrations to extend Medusa stores with notifications, payments, POS APIs, and automation tools. New options include Discord alerts, Postal email infrastructure, POS endpoints with dynamic pricing, and Juspay Hyperswitch for multi-provider payments. A visual Flow Builder enables workflow automation without custom code, while additional plugins support…
Showing the 12 most recent of 20 posts we hold for @medusajs_news. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Medusa.js News” (@medusajs_news), 24 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/medusajs_news.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.