Changelog — logg-sh/logg

logg

2026.09.06

Generate and publish release communication from connected product sources with review, targeting, and editions.

Teams can turn repo and tracker evidence into customer-ready notes without leaving the workspace.

Features

  • Generate and publish release communication from connected product sources with review, targeting, and editions.

    Teams can turn repo and tracker evidence into customer-ready notes without leaving the workspace.

  • Send changelog campaigns and scheduled deliveries, including subscriber preferences and sender-domain setup.

    Customers can announce releases on a controlled schedule instead of only posting a public page.

  • Import existing changelogs, recover from failed imports, and guide readers through upgrades.
  • Invite collaborators, manage project access, and review changelog revisions before they go live.
  • Track public engagement and project analytics for published changelogs.

Improvements

  • Harden GitHub, GitLab, and Bitbucket source access and keep release evidence within the connected project.

    Publishing stays grounded in the repos you actually connected, which is safer for first customers.

  • Require tracking opt-in in embeds and keep React client code from leaking server-only boundaries.
  • Preserve unmanaged changelog content when a complete history sync runs.
  • Align packaged CLI version metadata with the runtime version.

2026.09.04

Install logg as a GitHub App so it can work on your repositories without a personal token.

Teams can connect GitHub as a product instead of borrowing a developer login.

Features

  • Install logg as a GitHub App so it can work on your repositories without a personal token.

    Teams can connect GitHub as a product instead of borrowing a developer login.

  • Import an existing CHANGELOG.md and keep a changelog file in the repository as the living record.

    You can start from a file you already ship and keep it in sync with what logg publishes.

  • Jira and GitLab issues are included in the evidence used to write each release.

    Release notes can reflect tracker work, not only git history.

  • Draft two announcement posts next to every changelog entry.
  • Embed a changelog widget with a single script tag, including a notification bell.
  • Every public changelog and version link gets its own Open Graph card.
  • Each entry records how often it was read.

Improvements

  • Changelog pages render live instead of from a pre-baked snapshot.
  • A refused credential is treated as a source problem, not as an empty changelog.
  • Ship a GitHub Action that runs in the runner's native shell, plus package licenses and READMEs.
  • Stability work made the service steadier.

2026.09.09

Publish an entry from a single publication panel that brings drafting, review and publishing together.

Publishing no longer means hopping between separate screens.

Features

  • Publish an entry from a single publication panel that brings drafting, review and publishing together.

    Publishing no longer means hopping between separate screens.

  • Show when a release window closes, with only the root manifest opening a release.
  • Import entries and subscribers from new dedicated import screens.

Improvements

  • Reorganize each project into six areas, each with a single job, covering the overview, entries, email, imports, insights and settings.

    Makes it obvious where to go for any task in a project.

  • Reorder project settings so they read top to bottom.
  • Give public pages and email pages, including subscription confirmation, preferences and project invites, a consistent look.
  • Rewrite the documentation page to use the product's own terminology.

Fixes

  • Simplify entry visibility back to Internal and Customers, removing the Users, Developers and Business controls and the project-level audience toggle while keeping existing stored metadata, custom editions and privacy handling intact.

    Restores the intended, simpler choice about who sees an entry without losing anything already saved.

  • Security hardening landed behind the scenes.

2026.09.02

Turn the project embed guide into a chooser for picking how to embed.

Teams can pick an embed path without wading through a long static guide.

Features

  • Turn the project embed guide into a chooser for picking how to embed.

    Teams can pick an embed path without wading through a long static guide.

  • Raise a horizon animation under the marketing landing page.

    The public homepage now opens with a clearer, more distinctive visual.

Improvements

  • Settle workspace surfaces with hairline borders, lift, and a single frame around navigation.

    The product feels quieter and more consistent as you move between org and project screens.

  • Show an honest empty state on the login door instead of a misleading one.

2026.08.26

Launch Logg as a workspace for turning repository activity into a public changelog.

Teams can sign in, create projects, and ship a customer-facing record instead of a dump of commits.

Features

  • Launch Logg as a workspace for turning repository activity into a public changelog.

    Teams can sign in, create projects, and ship a customer-facing record instead of a dump of commits.

  • Sign in with an email link or GitHub, GitLab, or Bitbucket, then create organizations and invite teammates.
  • Connect a project to GitHub, GitLab, or Bitbucket so deliveries flow into changelog entries without the pipeline going dark.

    Detection, drafting, and publishing stay on one path from the repo to the live record.

  • Draft entries with a rules-based writer, a workbench, and monthly writing quotas instead of unconstrained generation.
  • Publish a public changelog with two themes, edition rules, custom domains, and RSS, Markdown, JSON, and llms.txt feeds.

    Readers and agents can follow the same record in the browser, in feeds, or on your own domain.

  • Embed the changelog, subscribe readers, and send announcement and digest mail through notification channels.
  • Expose a read API, a React package, a CLI, and an OAuth 2.1 MCP agent surface with consent.
  • Bill through a merchant of record that handles tax, with checkout, portal, and overage paths.

Get new entries by email

Double opt-in; one-click out. Details in the privacy policy.

Powered by logg.sh