release: 17.0.1.3.1 GA

[jeremi]

This PR merges the release branch into 17.0 following GA tag v17.0.1.3.1.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

2 out of 3 committers have signed the CLA.
✅ (jeremi)[https://github.com/jeremi]
✅ (gonzalesedwin1123)[https://github.com/gonzalesedwin1123]
❌ @OpenSPP
openspp seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[codecov]

Codecov Report

❌ Patch coverage is 82.96943% with 39 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.15%. Comparing base (95434f7) to head (2ba5d6b).
⚠️ Report is 1 commits behind head on 17.0.

Files with missing lines	Patch %	Lines
spp_branding_kit/controllers/main.py	54.83%	14 Missing ⚠️
spp_branding_kit/utils.py	30.76%	9 Missing ⚠️
spp_branding_kit/__init__.py	87.23%	4 Missing and 2 partials ⚠️
spp_branding_kit/models/ir_http.py	50.00%	5 Missing ⚠️
spp_branding_kit/tests/test_init_hooks.py	94.33%	2 Missing and 1 partial ⚠️
spp_branding_kit/tests/test_controllers.py	66.66%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             17.0     #847      +/-   ##
==========================================
+ Coverage   78.05%   78.15%   +0.10%     
==========================================
  Files         771      784      +13     
  Lines       20155    20395     +240     
  Branches     2436     2460      +24     
==========================================
+ Hits        15732    15940     +208     
- Misses       3854     3886      +32     
  Partials      569      569              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gemini-code-assist]

Summary of Changes

Hello @jeremi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request represents a significant release for the OpenSPP platform, tagged as 17.0.1.3.1 GA. The primary focus is on updating module versions across the board, integrating a new branding kit for enhanced customization, and refining CI/build processes. Additionally, module documentation has been extensively revised to reflect updated summaries and maturity statuses, indicating a progression towards more stable releases for many components. This release aims to consolidate recent developments and prepare the platform for broader adoption.

Highlights

• New Module Integration: The spp_branding_kit module (version 17.0.1.3.1) has been integrated, providing comprehensive branding customization and telemetry management for the OpenSPP platform.
• Module Version Updates: Numerous existing OpenSPP modules have had their versions updated to 17.0.1.3.1 across their manifest files and the metapackage configuration.
• Documentation and Maturity Status Enhancements: Many module README.rst, DESCRIPTION.md, and index.html files have been updated with revised summaries and maturity badges, transitioning several modules from 'Alpha' or 'Beta' to 'Production/Stable'.
• CI/Build System Tweaks: The .pre-commit-config.yaml has been adjusted to remove the --convert-fragments-to-markdown option from the oca-gen-addon-readme hook, and .gitignore now includes the .release/ directory.
• Translation File Cleanup: Several .pot translation files for modules like base_geoengine, g2p_bank_rest_api, g2p_encryption_keymanager, g2p_entitlement_cash, g2p_enumerator, g2p_registry_documents, g2p_registry_encryption, and g2p_registry_rest_api have been removed.
• Metapackage Dependency Updates: The setup/_metapackage/pyproject.toml file has been updated to reflect the new metapackage version and includes new module dependencies such as spp_attendance, spp_branding_kit, spp_change_request_base, spp_dashboard_base, and others, while removing spp_demo.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request appears to be a release preparation, merging the release branch for version 17.0.1.3.1. The changes include version bumps in __manifest__.py files, updates to READMEs and module summaries to be more descriptive, and the addition of several new modules like spp_attendance and spp_branding_kit. A number of translation (.pot) files have also been removed. Overall, the changes align with a release process. However, I've identified several inconsistencies in the updated README files where module titles or descriptions do not match the module's actual purpose, which could cause confusion. I've left specific comments with suggestions to correct these documentation issues.

[gemini-code-assist]

The title of this README, 'OpenSPP Change Request: Create Group', is inconsistent with the module's purpose, which is to create a 'Farm'. The overview and the module name spp_change_request_create_farm both refer to creating a farm. Please update the title for clarity.

Suggested change

	OpenSPP Change Request: Create Group
	====================================
	OpenSPP Change Request: Create Farm
	===================================

[gemini-code-assist]

The overview states that this module handles 'adding new Farm', which is inconsistent with the module's name spp_change_request_edit_farm and its purpose of editing existing farms. Please update the description to reflect that it's for editing, not adding, farms.

Suggested change

	The `spp_change_request_edit_farm <spp_change_request_edit_farm>`__
	module extends the OpenSPP Change Request system to specifically handle
	requests for adding new farmers to existing groups within the registry.
	It leverages the framework provided by the
	`spp_change_request <spp_change_request>`__ module and integrates with
	other registry modules to streamline the process of adding farmers while
	maintaining data integrity and consistency.
	requests for adding new Farm within the registry. It leverages the
	framework provided by the `spp_change_request <spp_change_request>`__
	module and integrates with other registry modules to streamline the
	process of adding farmers while maintaining data integrity and
	consistency.
	The `spp_change_request_edit_farm <spp_change_request_edit_farm>`__
	module extends the OpenSPP Change Request system to specifically handle
	requests for editing existing Farm records within the registry. It leverages the
	framework provided by the `spp_change_request <spp_change_request>`__
	module and integrates with other registry modules to streamline the
	process of editing farms while maintaining data integrity and
	consistency.

[gemini-code-assist]

The title 'OpenSPP Change Request: Create Group' is incorrect for this module. The module name is spp_change_request_edit_farmer and the overview correctly states its purpose is to edit an existing Farmer. Please update the title to 'OpenSPP Change Request: Edit Farmer' for consistency.

Suggested change

	OpenSPP Change Request: Create Group
	====================================
	OpenSPP Change Request: Edit Farmer
	===================================

[emjay0921]

As I checked, I found out that this changes the app icons. Celine requested before to make the app icons in blue background with white on the logo. Is this intended?

[gonzalesedwin1123]

As I checked, I found out that this changes the app icons. Celine requested before to make the app icons in blue background with white on the logo. Is this intended?

OK @emjay0921 I will replace the icons with what we have in the 17.0 branch.

[sonarqubecloud]

Quality Gate failed

Failed conditions
36.1% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE