chore: Test OIDC NPM Publishing Without Token

[jonathannorris]

Testing Angular SDK patch release after removing NPM_TOKEN from GitHub secrets to validate that OIDC authentication alone works for npm publishing.

[gemini-code-assist]

Summary of Changes

Hello @jonathannorris, 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 is a targeted test designed to verify the functionality of OIDC-based NPM publishing for the Angular SDK. The core objective is to confirm that packages can be successfully published without the explicit use of a stored NPM_TOKEN, thereby enhancing the security posture of the publishing process. The actual modification is a minor, non-functional change to a README.md file, which acts as a trigger for the associated CI/CD pipeline to execute the OIDC publishing flow.

Highlights

• OIDC NPM Publishing Test: This pull request serves as a test to validate that OpenID Connect (OIDC) authentication alone is sufficient for publishing the Angular SDK to NPM, specifically after the removal of the NPM_TOKEN from GitHub secrets. The minimal code change is intended solely to trigger the publishing workflow.

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 introduces a minor cosmetic change in packages/angular/projects/angular-sdk/README.md by removing a blank line. As the pull request description indicates, this change is intended to test the OIDC NPM publishing workflow. The change itself is innocuous and I see no issues with it.