@leaflink/dom-testing-utils 5.0.0-alpha.1 → 5.0.0-alpha.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +13 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -13,6 +13,7 @@
13
13
 
14
14
  - [@leaflink/dom-testing-utils](#leaflinkdom-testing-utils)
15
15
  - [Installation](#installation)
16
+ - [Releases](#releases)
16
17
  - [Usage](#usage)
17
18
  - [Setup file](#setup-file)
18
19
  - [Global setup](#global-setup)
@@ -38,6 +39,18 @@
38
39
  pnpm add -D @leaflink/dom-testing-utils
39
40
  ```
40
41
 
42
+ ## Releases
43
+
44
+ Releases are fully automated using [semantic-release](https://github.com/semantic-release/semantic-release). When changes are pushed to a release branch (`main`, `alpha`, `beta`, `canary`, `next`, `next-major`, or `[0-9]+.x`), the CI workflow:
45
+
46
+ 1. Builds the package with `pnpm build`
47
+ 2. Analyzes commits to determine the next version (using [Conventional Commits](https://www.conventionalcommits.org/))
48
+ 3. Publishes to npm and creates a GitHub release with changelog
49
+
50
+ **Commit types that trigger releases:** `feat`, `fix`, `perf`, and `revert`. Other types (e.g. `docs`, `chore`) appear in changelogs but do not bump the version on their own.
51
+
52
+ For detailed commit conventions and manual release instructions, see [CONTRIBUTING.md](.github/CONTRIBUTING.md#semantic-release).
53
+
41
54
  ## Usage
42
55
 
43
56
  In your test files you can import utility functions.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leaflink/dom-testing-utils",
3
- "version": "5.0.0-alpha.1",
3
+ "version": "5.0.0-alpha.3",
4
4
  "description": "Frontend DOM testing utilities",
5
5
  "packageManager": "pnpm@10.12.2",
6
6
  "engines": {