Skip to content

build(deps): bump tower-sessions-memory-store from 0.14.0 to 0.15.0#35155

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/tower-sessions-memory-store-0.15.0
Open

build(deps): bump tower-sessions-memory-store from 0.14.0 to 0.15.0#35155
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/tower-sessions-memory-store-0.15.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 22, 2026

Bumps tower-sessions-memory-store from 0.14.0 to 0.15.0.

Release notes

Sourced from tower-sessions-memory-store's releases.

v0.15.0

What's Changed

  • Update rand to v0.9. #238
  • Fix memory ordering race. #254

New Contributors

Full Changelog: maxcountryman/tower-sessions@v0.14.0...v0.15.0

Changelog

Sourced from tower-sessions-memory-store's changelog.

0.15.0

  • Update rand to v0.9. #238
  • Fix memory ordering race. #254
Commits
  • 92ad026 mark v0.15.0
  • 3cd7a25 Insert/remove session data before release-update to is_modified
  • 7800836 Add tower-sessions-cookie-store to the README
  • 5ea8112 Update mockall requirement from 0.13.0 to 0.14.0
  • 9acb2d1 fix: clippy lints
  • 9ad9533 fix(tower-sessions-core): disable parking_lot serde feature
  • 81105af Update rand
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [tower-sessions-memory-store](https://github.com/maxcountryman/tower-sessions) from 0.14.0 to 0.15.0.
- [Release notes](https://github.com/maxcountryman/tower-sessions/releases)
- [Changelog](https://github.com/maxcountryman/tower-sessions/blob/main/CHANGELOG.md)
- [Commits](maxcountryman/tower-sessions@v0.14.0...v0.15.0)

---
updated-dependencies:
- dependency-name: tower-sessions-memory-store
  dependency-version: 0.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the A-dependencies Area: dependency upgrades label Feb 22, 2026
@dependabot dependabot bot requested a review from a team as a code owner February 22, 2026 22:46
@dependabot dependabot bot requested a review from ohbadiah February 22, 2026 22:46
@github-actions
Copy link

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

  • Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
  • Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
  • Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-dependencies Area: dependency upgrades

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants