@fengsp , this is a patch that I mentioned to you offline. And it has been shipped to PyPI. It would be great if you can merge it in, as-is.
The tangible change to the downstream developers is that this patch version temporarily pins to Flask<2.3. This is of course not a long term solution. Later we will merge in the other existing PR which will work on Flask 2.2+, and then we will ship it as Flask-session 0.5.0.
The other file that I introduced in this PR is a Github action that will make the subsequent release much easier. I did that all the time on projects that I own. It is harmless if you choose to not use it, but I would suggest to keep that file in.
@fengsp , this is a patch that I mentioned to you offline. And it has been shipped to PyPI. It would be great if you can merge it in, as-is.
The tangible change to the downstream developers is that this patch version temporarily pins to Flask<2.3. This is of course not a long term solution. Later we will merge in the other existing PR which will work on Flask 2.2+, and then we will ship it as Flask-session 0.5.0.
The other file that I introduced in this PR is a Github action that will make the subsequent release much easier. I did that all the time on projects that I own. It is harmless if you choose to not use it, but I would suggest to keep that file in.