Bump version v2.7.9

[RishadAlam]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @RishadAlam, 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 primarily focuses on a routine version increment to v2.7.9 for the Bit Integrations plugin. It also enhances the plugin's architecture by incorporating a new namespace for 'IntegrationsPro' actions and triggers, suggesting an expansion of professional integration features. Additionally, development dependencies have been updated to ensure compatibility and leverage the latest tools.

Highlights

• Version Bump: The plugin version has been updated from 2.7.8 to 2.7.9 across multiple configuration and plugin files, including backend/Config.php, bitwpfi.php, and readme.txt.
• New IntegrationsPro Support: Added support for BitApps\IntegrationsPro actions and triggers within the backend/Flow/Flow.php file, expanding the plugin's integration capabilities.
• Dependency Update: The composer.lock file was updated to reflect a new version of friendsofphp/php-cs-fixer (v3.94.2) and a change in the plugin-api-version.
• Localization File Update: The languages/bit-integrations.pot file had its POT creation date updated and line number references adjusted for BuddyBoss related messages.

Changelog

• backend/Config.php
  • Updated the VERSION constant to 2.7.9.
• backend/Flow/Flow.php
  • Added a new elseif condition to isActionExists to check for BitApps\IntegrationsPro\Actions.
  • Added a new elseif condition to isTriggerExists to check for BitApps\IntegrationsPro\Triggers.
• bitwpfi.php
  • Updated the plugin's Version header to 2.7.9.
  • Updated the BTCBI_VERSION define to 2.7.9.
• composer.lock
  • Updated friendsofphp/php-cs-fixer from v3.94.0 to v3.94.2.
  • Updated the plugin-api-version from 2.9.0 to 2.6.0.
• languages/bit-integrations.pot
  • Updated the POT-Creation-Date.
  • Adjusted line number references for several BuddyBoss related messages.
• readme.txt
  • Updated the Stable tag to 2.7.9.

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.

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

The pull request primarily focuses on bumping the plugin version to v2.7.9 and adding support for a new Pro namespace (BitApps\IntegrationsPro) in the action and trigger existence checks. The changes are consistent across configuration files, plugin headers, and the readme. However, there is a suspicious downgrade of the plugin-api-version in composer.lock that should be verified to ensure it doesn't break dependency resolution in specific environments.

[gemini-code-assist]

The plugin-api-version has been downgraded from 2.9.0 to 2.6.0. This typically happens when composer update is run using an older version of Composer. Please ensure this was intentional and that it doesn't affect any dependencies that might rely on newer Composer features.

[gemini-code-assist]

The new IntegrationsPro namespace is checked after the legacy BTCBI_PRO namespace. If IntegrationsPro is intended to be the modern standard for the Pro version, it might be better to check it before the deprecated namespace to avoid loading legacy controllers if both are present.