Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrade to Spring Framework 6.1.2 #38666

Closed
philwebb opened this issue Dec 5, 2023 · 2 comments
Closed

Upgrade to Spring Framework 6.1.2 #38666

philwebb opened this issue Dec 5, 2023 · 2 comments
Labels
status: superseded An issue that has been superseded by another type: dependency-upgrade A dependency upgrade

Comments

@philwebb
Copy link
Member

philwebb commented Dec 5, 2023

No description provided.

@philwebb philwebb assigned philwebb and unassigned philwebb Dec 5, 2023
@philwebb philwebb added the type: dependency-upgrade A dependency upgrade label Dec 5, 2023
@philwebb philwebb added this to the 3.2.x milestone Dec 5, 2023
philwebb added a commit that referenced this issue Dec 5, 2023
@philwebb
Start building against Spring Framework 6.1.2 snapshots
4fb68d4 
See gh-38666
wilkinsona added a commit that referenced this issue Dec 6, 2023
@wilkinsona
Adapt to change in Framework's disconnected client detection
6dff3c5 
See gh-38666
wilkinsona added a commit that referenced this issue Dec 12, 2023
@wilkinsona
Adapt to changes in the locking model for closing an app context
612bf95 
See gh-38666
wilkinsona added a commit that referenced this issue Dec 14, 2023
@wilkinsona
Adapt to latest changes in the locking model for context close
8c5b7a8 
See gh-38666
@izeye
Copy link
Contributor

izeye commented Dec 25, 2023

This seems to have been resolved in #38814.

@wilkinsona
Copy link
Member

Thanks, @izeye.

I think the existing issue was missed by our tooling as it was in the 3.2.x milestone rather than 3.2.1.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2024
@wilkinsona wilkinsona removed this from the 3.2.x milestone Jan 2, 2024
@wilkinsona wilkinsona added the status: superseded An issue that has been superseded by another label Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: superseded An issue that has been superseded by another type: dependency-upgrade A dependency upgrade
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@philwebb @wilkinsona @izeye