While technically a fix, this is a breaking change if
you were relying on an external signal that aborts within the query.
It used to not set the state by just being an AbortError DomException
and now it will become an error. This behavior is more correct as we
don't want to ignore aborted signals that are external. Each fetch
creates an AbortController and passes the signal to query which is
aborted (without a reason) if any other method of the store fetches
again. This is done to avoid using an outdated request.
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Adoption](https://docs.renovatebot.com/merge-confidence/) | [Passing](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|---|---|
| [@pinia/colada](https://pinia-colada.esm.dev) ([source](https://github.com/posva/pinia-colada)) | [`^0.17.8` -> `^0.18.0`](https://renovatebot.com/diffs/npm/@pinia%2fcolada/0.17.9/0.18.0) |  |  |  |  |
---
### Release Notes
<details>
<summary>posva/pinia-colada (@​pinia/colada)</summary>
### [`v0.18.0`](https://github.com/posva/pinia-colada/blob/HEAD/CHANGELOG.md#0180-2025-12-02)
[Compare Source](https://github.com/posva/pinia-colada/compare/v0.17.9...v0.18.0)
##### ⚠ BREAKING CHANGES
- While technically a fix, this is a breaking change if
you were relying on an external signal that aborts within the `query`.
It used to not set the state by just being an AbortError DomException
and now it will become an error. This behavior is more correct as we
don't want to ignore aborted signals that are external. Each fetch
creates an AbortController and passes the signal to `query` which is
aborted (without a reason) if any other method of the store fetches
again. This is done to avoid using an *outdated* request.
##### Bug Fixes
- **query:** preserve any external AbortError ([0cdf7b9](https://github.com/posva/pinia-colada/commit/0cdf7b9a48ba346f25f2c4940d73834e77a4f25f))
</details>
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4zOS4zIiwidXBkYXRlZEluVmVyIjoiNDIuMzkuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
^0.17.8->^0.18.0Release Notes
posva/pinia-colada (@pinia/colada)
v0.18.0Compare Source
⚠ BREAKING CHANGES
you were relying on an external signal that aborts within the
query.It used to not set the state by just being an AbortError DomException
and now it will become an error. This behavior is more correct as we
don't want to ignore aborted signals that are external. Each fetch
creates an AbortController and passes the signal to
querywhich isaborted (without a reason) if any other method of the store fetches
again. This is done to avoid using an outdated request.
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.