Skip to content

[GHSA-vvfw-4m39-fjqf] Add patched version 29.1.0 - #10443

Open
mikeflame wants to merge 1 commit into
github:mikeflame/advisory-improvement-10443from
mikeflame:mikeflame-GHSA-vvfw-4m39-fjqf
Open

mikeflame wants to merge 1 commit into
github:mikeflame/advisory-improvement-10443from
mikeflame:mikeflame-GHSA-vvfw-4m39-fjqf

Conversation

@mikeflame

Copy link
Copy Markdown

Updates

  • Affected versions: <= 29.0 → < 29.1.0
  • Patched versions: none → 29.1.0
  • References: the v29.1.0 release

Comments
The record ends the range at last_affected: 29.0 with no patched version. The fix it already references, f9492f5 ("fix: Add request validation to prevent untrusted access in configuration update", 2026-04-13), shipped in AVideo 29.1.0, which was published to Packagist on 2026-09-23. That was after this record was reviewed on 2026-04-14.

GitHub's compare API reports the 29.0 tag as behind f9492f5 (the fix is not in 29.0) and the v29.1.0 tag as ahead of it (the fix is in 29.1.0):

Packagist has no version between 29.0 (2026-04-07) and 29.1.0 (2026-09-23). This PR replaces last_affected: 29.0 with fixed: 29.1.0 and records last_known_affected_version_range: "<= 29.0", so the set of affected published versions does not change.

@github-actions
github-actions Bot changed the base branch from main to mikeflame/advisory-improvement-10443 October 19, 2026 09:57
@arifsetiawan9617-hue

Copy link
Copy Markdown

Getting started with GitHub Copilot CLI

Quickly learn how to use GitHub Copilot CLI.

Introduction

GitHub Copilot CLI is a powerful terminal-native AI coding assistant that brings agentic capabilities directly to your command line. The Copilot CLI offers deep flexibility, GitHub workflow integration, and the ability to work autonomously on complex tasks while maintaining full user control.

This guide will help you start using the CLI.

Installation

Use one of these commands:

  • Cross-platform (npm)

    Prerequisite: Node.js 22 or later.

    npm install -g @github/copilot
  • Windows (WinGet)

    winget install GitHub.Copilot
  • macOS/Linux (Homebrew)

    brew install --cask copilot-cli

Starting the CLI for the first time

  1. In the terminal, navigate to the project directory where you want to use Copilot CLI.

  2. Start an interactive CLI session:

    copilot
  3. In the CLI interface, enter /login and follow the on-screen prompts to authenticate with your GitHub account.

    You'll only have to do this the first time you use the CLI.

  4. When prompted, confirm that you trust that the files in the current directory are suitable for use with an AI tool.

    [!NOTE]
    Copilot won't make changes to your files without your explicit approval.

  5. Try asking Copilot a question, for example:

    Give me an overview of this project.
    

    If you like, you can speak your prompt instead of typing it. See Use voice input with Copilot CLI.

Core shortcuts to master

Shortcut Action
Esc Cancel the current operation
Ctrl+C Cancel if thinking, clear input, or exit
Ctrl+L Clear the screen
@ Mention files to include in context
/ Show slash commands
? Show tabbed help
↑ and ↓ Navigate the command history

For a full list of shortcuts and available commands, enter:

/help

Using GitHub Copilot CLI non-interactively

You can also enter a command and get a response from Copilot directly in your terminal, without starting an interactive session.

To do this, pass a prompt to the CLI with the -p flag. For example:

copilot -p "In Git, how can I apply a commit from another branch"

The -p flag allows you to use GitHub Copilot CLI programmatically within scripts, for example to automate tasks using AI.

You can add the -s flag to tell the CLI to output only Copilot's response, omitting the additional usage information.

copilot -sp "YOUR PROMPT HERE"

For details of other flags you can use programmatically, and for more information, enter:

copilot help

or:

copilot help TOPIC

where TOPIC is one of the topics listed in the help output.

Next steps

Find out more about Copilot CLI:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants