ci: version packages

Author: github-actions[bot]

.changeset/jolly-spiders-fail.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

packages/core/CHANGELOG.md

@@ -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 <KIM Minseong>",
   "license": "MIT",

packages/core/package.json

@@ -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

packages/devtools/CHANGELOG.md

@@ -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 <KIM Minseong>",
   "license": "MIT",

packages/devtools/package.json

@@ -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

packages/react-devtools/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@connectivity-js/react-devtools",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "React devtools for Connectivity",
   "author": "@minseong0324 <KIM Minseong>",
   "license": "MIT",

packages/react-devtools/package.json

@@ -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

packages/react/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@connectivity-js/react",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "React adapter for Connectivity",
   "author": "@minseong0324 <KIM Minseong>",
   "license": "MIT",