@ihyeon/flow-qa 0.1.1 → 0.1.2

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.
package/README.ko.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # Flow QA
2
2
 
3
+ [![npm 버전](https://img.shields.io/npm/v/%40ihyeon%2Fflow-qa?label=npm)](https://www.npmjs.com/package/@ihyeon/flow-qa) · [npm 패키지: @ihyeon/flow-qa](https://www.npmjs.com/package/@ihyeon/flow-qa)
4
+
3
5
  [English](https://github.com/hyeonse-swing/flow-qa/blob/main/README.md) · **한국어**
4
6
 
5
7
  사용자 플로우를 검토 가능한 테스트 케이스로 바꾸고, 실제 브라우저 실행 결과를 증거가 연결된 QA 리포트로 남기는 로컬 도구입니다. 플로우의 기대 결과가 모호하면 추측해 통과시키지 않고 질문과 차단 상태로 남깁니다.
@@ -14,7 +16,7 @@ CLI와 `127.0.0.1` 전용 웹 UI를 제공합니다. UI는 영어로 시작하
14
16
  Node.js 24 이상이 필요합니다. 브라우저는 첫 실행 전에 설치합니다.
15
17
 
16
18
  ```sh
17
- npm install -g @ihyeon/flow-qa@0.1.1
19
+ npm install -g @ihyeon/flow-qa@0.1.2
18
20
  flow-qa browser install
19
21
  flow-qa ui --demo
20
22
  ```
package/README.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # Flow QA
2
2
 
3
+ [![npm version](https://img.shields.io/npm/v/%40ihyeon%2Fflow-qa?label=npm)](https://www.npmjs.com/package/@ihyeon/flow-qa) · [npm package: @ihyeon/flow-qa](https://www.npmjs.com/package/@ihyeon/flow-qa)
4
+
3
5
  **English** · [한국어](https://github.com/hyeonse-swing/flow-qa/blob/main/README.ko.md)
4
6
 
5
7
  Flow QA turns a user flow into reviewable test cases, runs them in a real browser, and ties the results to evidence in a QA report. When an expected outcome is unclear, it keeps the question visible and blocks that case instead of guessing.
@@ -14,7 +16,7 @@ Flow QA is available as a CLI and a web UI bound to `127.0.0.1`. Provide a targe
14
16
  Requires Node.js 24 or later. Install Chromium before the first run:
15
17
 
16
18
  ```sh
17
- npm install -g @ihyeon/flow-qa@0.1.1
19
+ npm install -g @ihyeon/flow-qa@0.1.2
18
20
  flow-qa browser install
19
21
  flow-qa ui --demo
20
22
  ```
package/docs/releases.md CHANGED
@@ -2,6 +2,30 @@
2
2
 
3
3
  The alpha entries below are historical release records. They document earlier package versions and checks.
4
4
 
5
+ ## Automated npm releases
6
+
7
+ A push to `main` publishes only when `package.json` changes to a new plain `X.Y.Z` version. Pull requests and pushes without a version change run verification without publishing. The package and lockfile versions must agree; the version must increase, and registry errors stop the release. Rerunning a successful publication skips the existing immutable npm version.
8
+
9
+ The `publish` job in [ci.yml](../.github/workflows/ci.yml) waits for the full verification job, then publishes through npm trusted publishing (OIDC). It uses the `latest` tag and checks the published package with a fresh consumer installation and three real Chromium demo cases. No npm token is stored in GitHub secrets.
10
+
11
+ For the next release, update the release notes and current installation examples, then bump the version before committing and pushing:
12
+
13
+ ```sh
14
+ npm version patch --no-git-tag-version
15
+ npm run check
16
+ ```
17
+
18
+ Push the version change to `main` and check the **Verify release** workflow. A successful verification job alone does not confirm publication: the publish job and its registry smoke check must also pass. Retry a transient failure by rerunning the same workflow; do not reuse a published version for different package contents.
19
+
20
+ The npm trusted publisher is configured for GitHub repository `hyeonse-swing/flow-qa`, workflow `ci.yml`, with direct publishing allowed. See [npm's trusted publishing documentation](https://docs.npmjs.com/trusted-publishers/) for account setup.
21
+
22
+ ## 0.1.2
23
+
24
+ Adds version-gated npm publishing from GitHub Actions and npm links in both README languages. Runtime behavior is unchanged from 0.1.1.
25
+
26
+ - Package: [`@ihyeon/flow-qa@0.1.2`](https://www.npmjs.com/package/@ihyeon/flow-qa/v/0.1.2)
27
+ - Verification and publication: [GitHub Actions](https://github.com/hyeonse-swing/flow-qa/actions/workflows/ci.yml)
28
+
5
29
  ## 0.1.1
6
30
 
7
31
  This release uses plain semver and the npm `latest` dist-tag. It includes the runtime fixes documented in the historical entry below, with no additional runtime changes. The existing runtime passed 47 tests and the browser checks recorded there. Version 0.1.1 metadata, package contents, and a fresh consumer installation were also verified: the installed `flow-qa` command worked and all three Chromium demo cases passed without model calls.
@@ -10,7 +34,7 @@ This release uses plain semver and the npm `latest` dist-tag. It includes the ru
10
34
  - Source and package: [GitHub release](https://github.com/hyeonse-swing/flow-qa/releases/tag/v0.1.1)
11
35
  - Public checks: [GitHub Actions](https://github.com/hyeonse-swing/flow-qa/actions/workflows/ci.yml)
12
36
 
13
- Use this version when checking the published package:
37
+ Use the matching source revision when checking this historical package:
14
38
 
15
39
  ```sh
16
40
  FLOWQA_PACKAGE_SPEC=@ihyeon/flow-qa@0.1.1 npm run smoke:package
package/docs/ui.md CHANGED
@@ -7,7 +7,7 @@ Use the target app's URL and a user flow to review cases, run them, and inspect
7
7
  Node.js 24 or later is required. Install Flow QA and start the local demo:
8
8
 
9
9
  ```sh
10
- npm install -g @ihyeon/flow-qa@0.1.1
10
+ npm install -g @ihyeon/flow-qa@0.1.2
11
11
  flow-qa browser install
12
12
  flow-qa ui --demo
13
13
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ihyeon/flow-qa",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "license": "MIT",
5
5
  "author": "Hyeonse Im",
6
6
  "repository": {