ci: bump macOS from 13 to 26 on CI

[riscait]

🙌 What's Done

• bump macOS from 13 to 26 on CI
• add cSpell settings
• fetch-metadata@v2.5.0

✍️ What's Not Done

📝 Additional Notes

🖼️ Image Differences

Before	After
image	image

Pre-launch Checklist

• I have reviewed my own code (e.g., updated tests and documentation)

---

Note

CI/workflows

• Upgrade iOS deploy workflows to macos-26 runners
• Update dependabot/fetch-metadata to v2.5.0 and normalize github-token quoting

Editor/spellcheck

• Add refreshable to .cspell.yaml dictionary
• Add VSCode cSpell.ignorePaths for **/.pub-cache

^{Written by Cursor Bugbot for commit f8d2475. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @riscait, 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 enhancing the development environment by updating the CI macOS version and refining the project's spell-checking configuration. The CI update aims to ensure builds run on a more recent macOS environment, while the cSpell additions streamline code quality checks by adding a new word to the dictionary and ignoring cache directories.

Highlights

• CI Environment Update: The pull request aims to update the macOS version used in the Continuous Integration (CI) pipeline from version 13 to 26.
• cSpell Configuration: New cSpell settings have been introduced to improve spell checking within the project, including adding a new word to the dictionary and ignoring cache directories.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/dependabot-auto-merge.yaml
  • .github/workflows/deploy-ios-production-app.yaml
  • .github/workflows/deploy-ios-staging-app.yaml

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's title and description, 'ci: bump macOS from 13 to 26 on CI', are misleading as the changes only update cSpell configuration. There are no CI-related changes. This makes the repository history confusing. Please update the title and description to accurately reflect the changes (e.g., 'chore: Update cSpell configuration'). I have also left a suggestion to consolidate the cSpell configuration for better maintainability.