Round of dependency updates to address vulnerable versions

[joehan]

Description

Doing a round of dependency updates to deal with vulnerabilities that were popping up on package scanning.

form-data 2.5.3 - 2.5.4
glob 10.4.x -> 10.5.0
jws 3.2.2 -> 4.0.1
js-yaml 3.14.1 -> 3.14.2
body-parser 2.2.0 -> 2.2.1
tmp 0.0.33 -> 0.2.5

Scenarios Tested

Tests pass, code builds, and I ran through some basic commands to sanity check things.

[gemini-code-assist]

Summary of Changes

Hello @joehan, 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 maintenance task: updating several npm dependencies to mitigate potential security vulnerabilities and leverage the latest stable releases. Concurrently, it introduces explicit type annotations to interactive UI components, which improves the robustness and maintainability of the codebase by ensuring type consistency in user input handling.

Highlights

• Dependency Updates: Several key dependencies have been updated to address identified vulnerabilities and ensure the project uses more stable and secure versions. This includes updates for @inquirer/prompts, glob, js-yaml, and jsonwebtoken.
• Improved Type Safety: Explicit type arguments have been added to various interactive prompt functions (prompt.checkbox, search, select) across multiple files, enhancing type safety and code clarity, particularly when dealing with user input and selections.

🧠 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.

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 updates several dependencies to address security vulnerabilities, a crucial maintenance task. The code changes are minor and correctly adapt to the new, more type-safe API of the updated @inquirer/prompts library by adding explicit generic type annotations to its prompt functions. These changes are consistent across the codebase and improve type safety. The pull request is well-executed and ready for merging.