From fb62504cf77937a7f0d7467974cb3352460f6ac8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 24 Feb 2026 19:40:01 +0000 Subject: [PATCH] ci: version packages --- .changeset/jolly-spiders-fail.md | 36 ------------------------- packages/core/CHANGELOG.md | 34 +++++++++++++++++++++++ packages/core/package.json | 2 +- packages/devtools/CHANGELOG.md | 39 +++++++++++++++++++++++++++ packages/devtools/package.json | 2 +- packages/react-devtools/CHANGELOG.md | 40 ++++++++++++++++++++++++++++ packages/react-devtools/package.json | 2 +- packages/react/CHANGELOG.md | 39 +++++++++++++++++++++++++++ packages/react/package.json | 2 +- 9 files changed, 156 insertions(+), 40 deletions(-) delete mode 100644 .changeset/jolly-spiders-fail.md diff --git a/.changeset/jolly-spiders-fail.md b/.changeset/jolly-spiders-fail.md deleted file mode 100644 index 24ee79e..0000000 --- a/.changeset/jolly-spiders-fail.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -"@connectivity-js/react-devtools": minor -"@connectivity-js/devtools": minor -"@connectivity-js/react": minor -"@connectivity-js/core": minor ---- - -**Bug fix: `onSuccess`/`onError`/`onSettled` now fire after offline queue flush** - -Previously, when an action was queued while offline and later flushed, the result -was discarded and no callbacks fired. Now: - -- `onSuccess(result)` and `onSettled()` are called after a successful flush -- `onError(error)` and `onSettled()` are called when a flush exhausts all retry attempts -- Intermediate retry attempts do not trigger any callbacks - -**BREAKING:** `onSettled` is no longer called when a job is enqueued. It fires only -after the job reaches a terminal state (immediate execution success/error, or final -flush outcome). Code relying on `onSettled` firing at enqueue time should switch to -`onEnqueued` instead. - ---- - -**Bug fix: `QueuedJob.lastError` now stores the original `Error` object** - -`lastError` was previously storing a stringified message via `toErrorMessage()`, -silently discarding the stack trace and any custom properties on the Error object. -`lastError` is now typed `unknown` and holds the original thrown value. - ---- - -**Bug fix: grace period fires with the latest offline reason** - -When a second offline network event arrived during an active grace period timer, -the timer closure retained the first event's `reason`. The committed status change -now always reflects the most-recent event's reason. diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md index b3f5809..fc6e0a0 100644 --- a/packages/core/CHANGELOG.md +++ b/packages/core/CHANGELOG.md @@ -1,5 +1,39 @@ # @connectivity-js/core +## 0.2.0 + +### Minor Changes + +- **Bug fix: `onSuccess`/`onError`/`onSettled` now fire after offline queue flush** ([#12](https://github.com/minseong0324/connectivity-js/pull/12)) + + Previously, when an action was queued while offline and later flushed, the result + was discarded and no callbacks fired. Now: + + - `onSuccess(result)` and `onSettled()` are called after a successful flush + - `onError(error)` and `onSettled()` are called when a flush exhausts all retry attempts + - Intermediate retry attempts do not trigger any callbacks + + **BREAKING:** `onSettled` is no longer called when a job is enqueued. It fires only + after the job reaches a terminal state (immediate execution success/error, or final + flush outcome). Code relying on `onSettled` firing at enqueue time should switch to + `onEnqueued` instead. + + *** + + **Bug fix: `QueuedJob.lastError` now stores the original `Error` object** + + `lastError` was previously storing a stringified message via `toErrorMessage()`, + silently discarding the stack trace and any custom properties on the Error object. + `lastError` is now typed `unknown` and holds the original thrown value. + + *** + + **Bug fix: grace period fires with the latest offline reason** + + When a second offline network event arrived during an active grace period timer, + the timer closure retained the first event's `reason`. The committed status change + now always reflects the most-recent event's reason. + ## 0.1.0 ### Minor Changes diff --git a/packages/core/package.json b/packages/core/package.json index 9054ba8..087755c 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@connectivity-js/core", - "version": "0.1.0", + "version": "0.2.0", "description": "Type-safe, lightweight, framework-agnostic connectivity detection and offline action queue", "author": "@minseong0324 ", "license": "MIT", diff --git a/packages/devtools/CHANGELOG.md b/packages/devtools/CHANGELOG.md index 9e3b8c7..4a86704 100644 --- a/packages/devtools/CHANGELOG.md +++ b/packages/devtools/CHANGELOG.md @@ -1,5 +1,44 @@ # @connectivity-js/devtools +## 0.2.0 + +### Minor Changes + +- **Bug fix: `onSuccess`/`onError`/`onSettled` now fire after offline queue flush** ([#12](https://github.com/minseong0324/connectivity-js/pull/12)) + + Previously, when an action was queued while offline and later flushed, the result + was discarded and no callbacks fired. Now: + + - `onSuccess(result)` and `onSettled()` are called after a successful flush + - `onError(error)` and `onSettled()` are called when a flush exhausts all retry attempts + - Intermediate retry attempts do not trigger any callbacks + + **BREAKING:** `onSettled` is no longer called when a job is enqueued. It fires only + after the job reaches a terminal state (immediate execution success/error, or final + flush outcome). Code relying on `onSettled` firing at enqueue time should switch to + `onEnqueued` instead. + + *** + + **Bug fix: `QueuedJob.lastError` now stores the original `Error` object** + + `lastError` was previously storing a stringified message via `toErrorMessage()`, + silently discarding the stack trace and any custom properties on the Error object. + `lastError` is now typed `unknown` and holds the original thrown value. + + *** + + **Bug fix: grace period fires with the latest offline reason** + + When a second offline network event arrived during an active grace period timer, + the timer closure retained the first event's `reason`. The committed status change + now always reflects the most-recent event's reason. + +### Patch Changes + +- Updated dependencies [[`907d59e`](https://github.com/minseong0324/connectivity-js/commit/907d59ef5c7417a9b5265c3e51ca8cad16414394)]: + - @connectivity-js/core@0.2.0 + ## 0.1.0 ### Minor Changes diff --git a/packages/devtools/package.json b/packages/devtools/package.json index 023b29e..3281096 100644 --- a/packages/devtools/package.json +++ b/packages/devtools/package.json @@ -1,6 +1,6 @@ { "name": "@connectivity-js/devtools", - "version": "0.1.0", + "version": "0.2.0", "description": "Framework-agnostic devtools panel for Connectivity", "author": "@minseong0324 ", "license": "MIT", diff --git a/packages/react-devtools/CHANGELOG.md b/packages/react-devtools/CHANGELOG.md index 2aa96ce..3f0873c 100644 --- a/packages/react-devtools/CHANGELOG.md +++ b/packages/react-devtools/CHANGELOG.md @@ -1,5 +1,45 @@ # @connectivity-js/react-devtools +## 0.2.0 + +### Minor Changes + +- **Bug fix: `onSuccess`/`onError`/`onSettled` now fire after offline queue flush** ([#12](https://github.com/minseong0324/connectivity-js/pull/12)) + + Previously, when an action was queued while offline and later flushed, the result + was discarded and no callbacks fired. Now: + + - `onSuccess(result)` and `onSettled()` are called after a successful flush + - `onError(error)` and `onSettled()` are called when a flush exhausts all retry attempts + - Intermediate retry attempts do not trigger any callbacks + + **BREAKING:** `onSettled` is no longer called when a job is enqueued. It fires only + after the job reaches a terminal state (immediate execution success/error, or final + flush outcome). Code relying on `onSettled` firing at enqueue time should switch to + `onEnqueued` instead. + + *** + + **Bug fix: `QueuedJob.lastError` now stores the original `Error` object** + + `lastError` was previously storing a stringified message via `toErrorMessage()`, + silently discarding the stack trace and any custom properties on the Error object. + `lastError` is now typed `unknown` and holds the original thrown value. + + *** + + **Bug fix: grace period fires with the latest offline reason** + + When a second offline network event arrived during an active grace period timer, + the timer closure retained the first event's `reason`. The committed status change + now always reflects the most-recent event's reason. + +### Patch Changes + +- Updated dependencies [[`907d59e`](https://github.com/minseong0324/connectivity-js/commit/907d59ef5c7417a9b5265c3e51ca8cad16414394)]: + - @connectivity-js/devtools@0.2.0 + - @connectivity-js/core@0.2.0 + ## 0.1.0 ### Minor Changes diff --git a/packages/react-devtools/package.json b/packages/react-devtools/package.json index 5b630ce..4fd5087 100644 --- a/packages/react-devtools/package.json +++ b/packages/react-devtools/package.json @@ -1,6 +1,6 @@ { "name": "@connectivity-js/react-devtools", - "version": "0.1.0", + "version": "0.2.0", "description": "React devtools for Connectivity", "author": "@minseong0324 ", "license": "MIT", diff --git a/packages/react/CHANGELOG.md b/packages/react/CHANGELOG.md index 88db5c9..c9051f7 100644 --- a/packages/react/CHANGELOG.md +++ b/packages/react/CHANGELOG.md @@ -1,5 +1,44 @@ # @connectivity-js/react +## 0.2.0 + +### Minor Changes + +- **Bug fix: `onSuccess`/`onError`/`onSettled` now fire after offline queue flush** ([#12](https://github.com/minseong0324/connectivity-js/pull/12)) + + Previously, when an action was queued while offline and later flushed, the result + was discarded and no callbacks fired. Now: + + - `onSuccess(result)` and `onSettled()` are called after a successful flush + - `onError(error)` and `onSettled()` are called when a flush exhausts all retry attempts + - Intermediate retry attempts do not trigger any callbacks + + **BREAKING:** `onSettled` is no longer called when a job is enqueued. It fires only + after the job reaches a terminal state (immediate execution success/error, or final + flush outcome). Code relying on `onSettled` firing at enqueue time should switch to + `onEnqueued` instead. + + *** + + **Bug fix: `QueuedJob.lastError` now stores the original `Error` object** + + `lastError` was previously storing a stringified message via `toErrorMessage()`, + silently discarding the stack trace and any custom properties on the Error object. + `lastError` is now typed `unknown` and holds the original thrown value. + + *** + + **Bug fix: grace period fires with the latest offline reason** + + When a second offline network event arrived during an active grace period timer, + the timer closure retained the first event's `reason`. The committed status change + now always reflects the most-recent event's reason. + +### Patch Changes + +- Updated dependencies [[`907d59e`](https://github.com/minseong0324/connectivity-js/commit/907d59ef5c7417a9b5265c3e51ca8cad16414394)]: + - @connectivity-js/core@0.2.0 + ## 0.1.0 ### Minor Changes diff --git a/packages/react/package.json b/packages/react/package.json index 124d97f..b300130 100644 --- a/packages/react/package.json +++ b/packages/react/package.json @@ -1,6 +1,6 @@ { "name": "@connectivity-js/react", - "version": "0.1.0", + "version": "0.2.0", "description": "React adapter for Connectivity", "author": "@minseong0324 ", "license": "MIT",