Skip to main content
BEEQ maintains a detailed changelog that tracks every feature, bug fix, refactor, and dependency update across releases. The changelog is automatically generated from commit messages — which is why following the Conventional Commits format is so important.

​
How it works

When a release is cut, the release tooling reads all commits since the previous tag, groups them by type, and appends a new section to CHANGELOG.md. The section headings map directly to Conventional Commit types:
Changelog sectionCommit type
Features ⚡️feat
Bug Fixes 🐞fix
Refactor 🛠️refactor
Performance 🏎perf
Documentation 📚docs
Chore ⚙️chore
Revert 🔄revert
Commits of type style, test, ci, build, and wip are typically not surfaced in the changelog.
Because the changelog is generated automatically, do not edit CHANGELOG.md by hand. Your changes will be overwritten on the next release.

​
Recent releases

Here is an excerpt from the most recent entries to illustrate the format:

​
1.12.3 (2026-02-10)

Documentation 📚
  • Storybook: enable back HTML story code preview
Chore ⚙️
  • Enhance esm-loader.js to dynamically load ESM modules based on version from CDN URL
  • deps: update @stencil/core to v4.42.0
  • deps: update Storybook to v10.2.7
Revert 🔄
  • tsconfig change to new jsxImportSource alternative and remove the h import

​
1.12.0 (2026-01-28)

Features ⚡️
  • Button: add support for icon-only button variant with aspect-ratio 1:1 (square)
  • Steps, Step Item: add orientation property and support for vertical layout
Bug Fixes 🐞
  • Datepicker: prevent Cally library loading race condition with singleton promise pattern
  • Select: prevent tag removal on backspace in multiselect when the input is not empty
Refactor 🛠️
  • Datepicker: improve performance and scalability with utilities, and update the Cally library

​
Viewing the full changelog

The complete changelog is available in the repository: You can also view changes for a specific release range using GitHub’s compare view, linked at the top of each entry, for example: 
https://github.com/Endava/BEEQ/compare/v1.12.1...v1.12.2

​
Breaking changes in the changelog

Breaking changes are called out explicitly in the commit body using the BREAKING CHANGE: footer. When reading the changelog, look for entries with ! in the type, such as refactor(checkbox)!: — these signal a breaking change with migration instructions in the PR body.

​
Versioning

BEEQ follows Semantic Versioning:
  • Patch (1.12.2 → 1.12.3): bug fixes and minor maintenance.
  • Minor (1.11.x → 1.12.0): new backward-compatible features.
  • Major (1.x → 2.0.0): breaking changes.

Build docs developers (and LLMs) love

Get started for freeTalk to us