Migration to version 18.0

[OCA-git-bot]

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0

Modules to migrate

• auth_admin_passkey
• auth_admin_passkey_totp_mail_enforce
• auth_api_key - By @thienvh332 - [18.0][MIG] auth_api_key: Migration to 18.0 #701
• auth_api_key_group - By @thienvh332 - [18.0][MIG] auth_api_key_group: Migration to 18.0 #703
• auth_api_key_server_env - By @thienvh332 - [18.0][MIG] auth_api_key_server_env: Migration to 18.0 #702
• auth_oidc - By @ap-wtioit - [18.0][MIG] auth_oidc: Migration to 18.0 #705
• auth_saml
• auth_signup_verify_email - By @JrAdhoc - [18.0][MIG] auth_signup_verify_email: Migration to 18.0 #727
• auth_user_case_insensitive
• base_user_empty_password - By @chaule97 - [18.0][MIG] base_user_empty_password #699
• impersonate_login
• user_log_view

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

[ap-wtioit]

working on (ready for review) auth_oidc #705

[moncefarajdal]

Working on user_log_view and auth_admin_passkey

[moncefarajdal]

user_log_view : #711

[moncefarajdal]

auth_user_case_insensitive : #712

[moncefarajdal]

I have a question: Should I add my name in the contributors in the README file before the pull request is merged?

[pedrobaeza]

If the migration means some significant time (not only changing the version number), then yes, it's acceptable that you become a contributor there.

[moncefarajdal]

@pedrobaeza In this module auth_user_case_insensitive there was a significant change in the super()._login method so I adapted it to the new version and also updated the test cases. Does this count as a significant contribution?

[pedrobaeza]

Go ahead then. Take into account that this is a bit subjective, and what "we" (understood as the community) don't want is that people abuses the system to place it as a top contributor. But right now, your contributions seem valuable and checked carefully.

[JrAdhoc]

auth_signup_verify_email: #727