factor: use authorization header for auth

[pedrocrvz]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @pedrocrvz, 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 refactors the authentication method across the Gelato client implementations to align with common API security practices. By transitioning from a custom API key header to the standard 'Authorization: Bearer' scheme, the change enhances interoperability and consistency in how API credentials are handled. This update ensures that client requests are authenticated using a widely recognized and secure pattern.

Highlights

• Authentication Header Update: The authentication mechanism for both the Gelato Bundler and EVM Relayer clients has been updated to use the standard 'Authorization: Bearer' header instead of the custom 'X-API-Key' header. This standardizes how API keys are passed for authentication.
• Version Bump: The project version has been incremented from '0.0.9' to '0.0.11'.
• Changelog Entry Added: A new changeset file has been added, documenting this refactoring change for the @gelatocloud/gasless package as a patch release.

Changelog

• @gelatocloud/gasless
  • refactor: use authorization header for auth

Activity

• No review comments or activity have 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

The pull request refactors the API key handling to use a standard Authorization: Bearer header instead of a custom X-API-Key header in both the bundler and relayer clients. This is a good practice for API authentication. A new changeset file has been added, and the package version has been updated. The changes are clean and improve security by adopting a more standard authentication mechanism.