Create 2.0.0 stable release

2.x branch usage remains quite high and the only bug is 3367638 so I think it would be quite appropriate to make a new stable.

I tagged alpha3 a week ago. I think we can wait until a few more people test it with Drupal 11. Once Drupal 11 is released, then yes, it would make sense to tag 2.0.0.

Would also be nice if someone RTBCd that 🐛 Delete Login history records after user delete Fixed .

@jcnventura - yes, thanks for creating that release. I'm not sure I understand why we should wait for Drupal 11 until making the 2.0.0 stable?

I just reviewed 3367638 and it looks good to me. Since I've got the last commit on it I'd love if you could review the changes I made?

Thanks!

Drupal 11 is now scheduled for July 29th.

Can you clarify why we should wait for that to tag 2.0.0?

I think we could tag it now, but am curious for your thoughts.

Should be good now. No one raised any bug and it's been a month since alpha3

There seems to be a very minor phpcs bug in the CI. Maybe we can fix that before tagging it

Great catch. I fixed the phpcs and a yml lint issue identified by eslint. They are now green on this MR.

I propose we create the release on the 23rd so the commits I made today can hopefully get a little testing in the dev branch.

OK, there are no more bugs in the 2.x queue. It's been a while since the last commits without any new issues being opened. Seems like time to cut the 2.0.0 release.

Now created and marked as recommended on the project page https://www.drupal.org/project/login_history/releases/2.0.0 →

Thanks to everyone who worked on this release!

Automatically closed - issue fixed for 2 weeks with no activity.