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.

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

Release 0.9.0 #603

Merged
merged 2 commits into from Apr 25, 2024
Merged

Release 0.9.0 #603

merged 2 commits into from Apr 25, 2024

Conversation

kasparsd
Copy link
Collaborator

@kasparsd kasparsd commented Apr 23, 2024

Create a release with the following changes 0.8.2...release/next

This is a large release with lots of changes and improvements to how the two-factor data is processed.

Notable Changes

Full Changelog

Generated via git log 0.8.2...release/next --oneline --reverse --first-parent:

fd9a058 Merge pull request #551 from pkevan/patch-2
c490519 Allow filtering the PHP classname used for a provider (#546)
ed75664 Bump tested up to version (#552)
836ef62 Store the two-factor details in the user session at login time (#528)
f027b04 Bump guzzlehttp/psr7 from 2.4.3 to 2.5.0 (#555)
bb96a02 Simplify UI Text / more consistent text and UI. (#521)
c725c9b Use the integer REST API type instead of number, to resolve overly strict user_id capability checks (#560)
ff00842 Enqueue jQuery and wp.apiRequest for use within callbacks. (#561)
9032f2d Revalidate two factor settings prior to allowing any two-factor changes to an account. (#529)
654ebb7 2FA revalidation: Avoid prompting for revalidation when the user disables all 2fa methods (#567)
30e3d1f Bump version identifier
d971a9d Enqueue jQuery and wp.apiRequest for use within callbacks. (#561)
441690f Use the integer REST API type instead of number, to resolve overly strict user_id capability checks (#560)
af7ad52 Bump tested up to version (#552)
286aa22 Tests: Simplify the cookie management.
98830a9 Sync two-factor session meta to newly created sessions (#574)
f21ed3c Require a nonce be present for revalidate POST requests. (#575)
f2227ab Bump tough-cookie from 4.1.2 to 4.1.3 (#579)
237cc2c Destroy existing sessions when activating 2FA. (#578)
2d4b9ec (tag: 0.8.2) Destroy existing sessions when activating 2FA.
5fe5af3 Bump version identifier
2b0d9bc Add method to disable an individual provider (#587)
7e0d337 Merge pull request #595 from JJJ/issue-594
4bb3180 Merge pull request #597 from bph/patch-1
48840ca Merge pull request #589 from WordPress/dependabot/npm_and_yarn/postcss-8.4.31
9d4ce3b Merge pull request #582 from WordPress/dependabot/npm_and_yarn/word-wrap-1.2.4

@kasparsd
Copy link
Collaborator Author

@dd32 @iandunn Is it reasonable to assume that the current master branch has been running on WP.org for a while and is sufficiently tested to be tagged version 0.9.0 of this plugin? The changelog here is pretty significant and I'm not sure we can delay the release any further, especially if we want to merge in the U2F removal soon.

cc: @jeffpaul

@kasparsd kasparsd requested a review from dd32 April 23, 2024 09:58
@kasparsd
Copy link
Collaborator Author

I was reviewing the changelog and pushed b86efd5 to master unintentionally. Sorry about that.

@dd32
Copy link
Member

dd32 commented Apr 23, 2024

WordPress.org appears to be running 2b0d9bc
Changes not on w.org: 2b0d9bc...b86efd5

I feel releasing 0.9 is safe.

@kasparsd kasparsd merged commit dc27957 into master Apr 25, 2024
2 checks passed
@kasparsd kasparsd deleted the release/next branch April 25, 2024 10:05
@kasparsd
Copy link
Collaborator Author

The release is now out!

I've tested this on my local site and everything works as expected -- login, user profile settings, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants