chore: version bump to 2.6.0

[GrammaTonic]

Bump VERSION to 2.6.0 and update CHANGELOG for release.

[gemini-code-assist]

Summary of Changes

Hello, 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 prepares for the release of version 2.6.0 by updating the project's version identifier and documenting all new features and improvements in the changelog. The changes primarily focus on enhancing Prometheus monitoring capabilities across multiple phases and refining security advisory workflows, ensuring the project is ready for its next major iteration.

Highlights

• Version Bump: The project version has been updated from 2.5.0 to 2.6.0, signifying a new release.
• Changelog Update: The CHANGELOG has been updated to reflect the features and improvements included in version 2.6.0, specifically detailing Prometheus Monitoring phases (2-6) and security enhancements.
• Prometheus Monitoring: Version 2.6.0 introduces significant advancements in Prometheus monitoring, covering metric gap fixes, DORA metrics, job lifecycle tracking, new Grafana dashboards, user documentation, and a comprehensive test suite.
• Security Improvements: The security-advisories.yml workflow logic and coverage have been improved as part of this release.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• VERSION
  • Updated the version number to 2.6.0.
• docs/releases/CHANGELOG.md
  • Added release notes for v2.6.0, including details on Prometheus Monitoring Phases 2-6.
  • Included improvements to security-advisories.yml workflow logic and coverage.

Activity

• No human activity has been recorded on this pull request yet.

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

This pull request bumps the project version to 2.6.0 and updates the changelog with the new release notes. The changes are appropriate for a release. I've identified a minor inconsistency in the new changelog entry regarding Grafana dashboard names and have provided a suggestion to align it with other documentation for improved clarity.

[gemini-code-assist]

There's a minor inconsistency in the names of the Grafana dashboards mentioned. The changelog lists 'Job Performance' and 'Cache Efficiency', but other documentation (like docs/features/PROMETHEUS_SETUP.md) and the dashboard files themselves (job-analysis.json, performance-trends.json) use 'Job Analysis' and 'Performance Trends'. To ensure consistency and avoid user confusion, it would be best to use the actual dashboard titles in the changelog.

Suggested change

	- **Phase 4**: Split mega-dashboard into 4 standalone Grafana dashboards — Runner Overview, Job Performance, Cache Efficiency, DORA Metrics (#1137).
	- **Phase 4**: Split mega-dashboard into 4 standalone Grafana dashboards — Runner Overview, DORA Metrics, Performance Trends, Job Analysis (#1137).