examples/vue-ts-example-2025
1
0
Fork 0
Code Issues 1 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

chore(deps): update dependency @pinia/colada to ^0.18.0 #176

Merged
renovatebot merged 1 commits from renovate/v0.x into main 2025-12-17 03:27:48 +08:00
Conversation 0 Commits 1 Files Changed 2 +6 -6
renovatebot commented 2025-12-17 00:53:45 +08:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pinia/colada (source) ^0.17.8 -> ^0.18.0 age adoption passing confidence

Release Notes

posva/pinia-colada (@​pinia/colada)

v0.18.0

Compare Source

⚠ 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)

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@pinia%2fcolada/0.18.0?slim=true) | ![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@pinia%2fcolada/0.18.0?slim=true) | ![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@pinia%2fcolada/0.17.9/0.18.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@pinia%2fcolada/0.17.9/0.18.0?slim=true) | --- ### Release Notes <details> <summary>posva/pinia-colada (@&#8203;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-->
renovatebot added 1 commit 2025-12-17 00:53:45 +08:00
chore(deps): update dependency @pinia/colada to ^0.18.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI/CD Pipeline / playwright (push) Successful in 1m49s
Details
CI/CD Pipeline / build-and-deploy (push) Successful in 1m54s
Details
80d989f6d0
renovatebot merged commit 80d989f6d0 into main 2025-12-17 03:27:48 +08:00
renovatebot deleted branch renovate/v0.x 2025-12-17 03:27:48 +08:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_1-h.cc renovatebot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: examples/vue-ts-example-2025#176
Delete Branch "renovate/v0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?