Skip to content

chore: upgrade development status to Production/Stable for 8 modules#123

Merged
gonzalesedwin1123 merged 1 commit into19.0from
chore/upgrade-module-status-to-stable
Mar 19, 2026
Merged

chore: upgrade development status to Production/Stable for 8 modules#123
gonzalesedwin1123 merged 1 commit into19.0from
chore/upgrade-module-status-to-stable

Conversation

@gonzalesedwin1123
Copy link
Member

Summary

  • Upgrade development_status from Beta to Production/Stable for: spp_land_record, spp_registry_group_hierarchy, spp_farmer_registry, spp_farmer_registry_cr, spp_farmer_registry_demo,
    spp_farmer_registry_vocabularies, spp_starter_farmer_registry, spp_oauth
  • Update corresponding README badges (maturity badge from Beta/yellow to Production/Stable/green)

Test plan

  • Pre-commit checks pass
  • Verify maturity badges render correctly on module pages

Modules: spp_land_record, spp_registry_group_hierarchy, spp_farmer_registry,
spp_farmer_registry_cr, spp_farmer_registry_demo, spp_farmer_registry_vocabularies,
spp_starter_farmer_registry, spp_oauth
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 focuses on promoting several modules to a production-ready state. It involves updating the development status in the module metadata and modifying the corresponding maturity badges in the README files to reflect this change. This enhancement signifies that these modules are now considered stable and reliable for production use.

Highlights

  • Development Status Upgrade: Upgraded the development_status metadata in the __manifest__.py files of eight modules from 'Beta' to 'Production/Stable'.
  • README Badge Update: Updated the maturity badge in the README.rst files of three modules to reflect the 'Production/Stable' status, changing the badge color from yellow to green.
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
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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.

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
Copy link

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.96%. Comparing base (470aac7) to head (39639ae).
⚠️ Report is 4 commits behind head on 19.0.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             19.0     #123   +/-   ##
=======================================
  Coverage   69.96%   69.96%           
=======================================
  Files         832      832           
  Lines       48813    48813           
=======================================
  Hits        34154    34154           
  Misses      14659    14659           
Flag Coverage Δ
spp_base_common 90.26% <ø> (ø)
spp_farmer_registry 88.39% <ø> (ø)
spp_farmer_registry_cr 61.15% <ø> (ø)
spp_farmer_registry_demo 54.01% <ø> (ø)
spp_farmer_registry_vocabularies 39.40% <ø> (ø)
spp_irrigation 95.45% <ø> (ø)
spp_land_record 98.55% <ø> (ø)
spp_oauth 97.43% <ø> (ø)
spp_programs 45.51% <ø> (ø)
spp_registry_group_hierarchy 91.17% <ø> (ø)
spp_security 66.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
spp_farmer_registry/__manifest__.py 0.00% <ø> (ø)
spp_farmer_registry_cr/__manifest__.py 0.00% <ø> (ø)
spp_farmer_registry_demo/__manifest__.py 0.00% <ø> (ø)
spp_farmer_registry_vocabularies/__manifest__.py 0.00% <ø> (ø)
spp_land_record/__manifest__.py 0.00% <ø> (ø)
spp_oauth/__manifest__.py 0.00% <ø> (ø)
spp_registry_group_hierarchy/__manifest__.py 0.00% <ø> (ø)
🚀 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.

@gonzalesedwin1123 gonzalesedwin1123 marked this pull request as ready for review March 19, 2026 10:35
@gonzalesedwin1123 gonzalesedwin1123 merged commit e98d801 into 19.0 Mar 19, 2026
26 checks passed
@gonzalesedwin1123 gonzalesedwin1123 deleted the chore/upgrade-module-status-to-stable branch March 19, 2026 10:35
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.

2 participants