@github/copilot - npm Package Compare versions

Comparing version

1.0.43

1.0.44-0

+201

pvrecorder/node_mo...recorder-node/lib/windows/arm64/LICENSE

		Apache License
		Version 2.0, January 2004
		http://www.apache.org/licenses/

		TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

		1. Definitions.

		"License" shall mean the terms and conditions for use, reproduction,
		and distribution as defined by Sections 1 through 9 of this document.

		"Licensor" shall mean the copyright owner or entity authorized by
		the copyright owner that is granting the License.

		"Legal Entity" shall mean the union of the acting entity and all
		other entities that control, are controlled by, or are under common
		control with that entity. For the purposes of this definition,
		"control" means (i) the power, direct or indirect, to cause the
		direction or management of such entity, whether by contract or
		otherwise, or (ii) ownership of fifty percent (50%) or more of the
		outstanding shares, or (iii) beneficial ownership of such entity.

		"You" (or "Your") shall mean an individual or Legal Entity
		exercising permissions granted by this License.

		"Source" form shall mean the preferred form for making modifications,
		including but not limited to software source code, documentation
		source, and configuration files.

		"Object" form shall mean any form resulting from mechanical
		transformation or translation of a Source form, including but
		not limited to compiled object code, generated documentation,
		and conversions to other media types.

		"Work" shall mean the work of authorship, whether in Source or
		Object form, made available under the License, as indicated by a
		copyright notice that is included in or attached to the work
		(an example is provided in the Appendix below).

		"Derivative Works" shall mean any work, whether in Source or Object
		form, that is based on (or derived from) the Work and for which the
		editorial revisions, annotations, elaborations, or other modifications
		represent, as a whole, an original work of authorship. For the purposes
		of this License, Derivative Works shall not include works that remain
		separable from, or merely link (or bind by name) to the interfaces of,
		the Work and Derivative Works thereof.

		"Contribution" shall mean any work of authorship, including
		the original version of the Work and any modifications or additions
		to that Work or Derivative Works thereof, that is intentionally
		submitted to Licensor for inclusion in the Work by the copyright owner
		or by an individual or Legal Entity authorized to submit on behalf of
		the copyright owner. For the purposes of this definition, "submitted"
		means any form of electronic, verbal, or written communication sent
		to the Licensor or its representatives, including but not limited to
		communication on electronic mailing lists, source code control systems,
		and issue tracking systems that are managed by, or on behalf of, the
		Licensor for the purpose of discussing and improving the Work, but
		excluding communication that is conspicuously marked or otherwise
		designated in writing by the copyright owner as "Not a Contribution."

		"Contributor" shall mean Licensor and any individual or Legal Entity
		on behalf of whom a Contribution has been received by Licensor and
		subsequently incorporated within the Work.

		2. Grant of Copyright License. Subject to the terms and conditions of
		this License, each Contributor hereby grants to You a perpetual,
		worldwide, non-exclusive, no-charge, royalty-free, irrevocable
		copyright license to reproduce, prepare Derivative Works of,
		publicly display, publicly perform, sublicense, and distribute the
		Work and such Derivative Works in Source or Object form.

		3. Grant of Patent License. Subject to the terms and conditions of
		this License, each Contributor hereby grants to You a perpetual,
		worldwide, non-exclusive, no-charge, royalty-free, irrevocable
		(except as stated in this section) patent license to make, have made,
		use, offer to sell, sell, import, and otherwise transfer the Work,
		where such license applies only to those patent claims licensable
		by such Contributor that are necessarily infringed by their
		Contribution(s) alone or by combination of their Contribution(s)
		with the Work to which such Contribution(s) was submitted. If You
		institute patent litigation against any entity (including a
		cross-claim or counterclaim in a lawsuit) alleging that the Work
		or a Contribution incorporated within the Work constitutes direct
		or contributory patent infringement, then any patent licenses
		granted to You under this License for that Work shall terminate
		as of the date such litigation is filed.

		4. Redistribution. You may reproduce and distribute copies of the
		Work or Derivative Works thereof in any medium, with or without
		modifications, and in Source or Object form, provided that You
		meet the following conditions:

		(a) You must give any other recipients of the Work or
		Derivative Works a copy of this License; and

		(b) You must cause any modified files to carry prominent notices
		stating that You changed the files; and

		(c) You must retain, in the Source form of any Derivative Works
		that You distribute, all copyright, patent, trademark, and
		attribution notices from the Source form of the Work,
		excluding those notices that do not pertain to any part of
		the Derivative Works; and

		(d) If the Work includes a "NOTICE" text file as part of its
		distribution, then any Derivative Works that You distribute must
		include a readable copy of the attribution notices contained
		within such NOTICE file, excluding those notices that do not
		pertain to any part of the Derivative Works, in at least one
		of the following places: within a NOTICE text file distributed
		as part of the Derivative Works; within the Source form or
		documentation, if provided along with the Derivative Works; or,
		within a display generated by the Derivative Works, if and
		wherever such third-party notices normally appear. The contents
		of the NOTICE file are for informational purposes only and
		do not modify the License. You may add Your own attribution
		notices within Derivative Works that You distribute, alongside
		or as an addendum to the NOTICE text from the Work, provided
		that such additional attribution notices cannot be construed
		as modifying the License.

		You may add Your own copyright statement to Your modifications and
		may provide additional or different license terms and conditions
		for use, reproduction, or distribution of Your modifications, or
		for any such Derivative Works as a whole, provided Your use,
		reproduction, and distribution of the Work otherwise complies with
		the conditions stated in this License.

		5. Submission of Contributions. Unless You explicitly state otherwise,
		any Contribution intentionally submitted for inclusion in the Work
		by You to the Licensor shall be under the terms and conditions of
		this License, without any additional terms or conditions.
		Notwithstanding the above, nothing herein shall supersede or modify
		the terms of any separate license agreement you may have executed
		with Licensor regarding such Contributions.

		6. Trademarks. This License does not grant permission to use the trade
		names, trademarks, service marks, or product names of the Licensor,
		except as required for reasonable and customary use in describing the
		origin of the Work and reproducing the content of the NOTICE file.

		7. Disclaimer of Warranty. Unless required by applicable law or
		agreed to in writing, Licensor provides the Work (and each
		Contributor provides its Contributions) on an "AS IS" BASIS,
		WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
		implied, including, without limitation, any warranties or conditions
		of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
		PARTICULAR PURPOSE. You are solely responsible for determining the
		appropriateness of using or redistributing the Work and assume any
		risks associated with Your exercise of permissions under this License.

		8. Limitation of Liability. In no event and under no legal theory,
		whether in tort (including negligence), contract, or otherwise,
		unless required by applicable law (such as deliberate and grossly
		negligent acts) or agreed to in writing, shall any Contributor be
		liable to You for damages, including any direct, indirect, special,
		incidental, or consequential damages of any character arising as a
		result of this License or out of the use or inability to use the
		Work (including but not limited to damages for loss of goodwill,
		work stoppage, computer failure or malfunction, or any and all
		other commercial damages or losses), even if such Contributor
		has been advised of the possibility of such damages.

		9. Accepting Warranty or Additional Liability. While redistributing
		the Work or Derivative Works thereof, You may choose to offer,
		and charge a fee for, acceptance of support, warranty, indemnity,
		or other liability obligations and/or rights consistent with this
		License. However, in accepting such obligations, You may act only
		on Your own behalf and on Your sole responsibility, not on behalf
		of any other Contributor, and only if You agree to indemnify,
		defend, and hold each Contributor harmless for any liability
		incurred by, or claims asserted against, such Contributor by reason
		of your accepting any such warranty or additional liability.

		END OF TERMS AND CONDITIONS

		APPENDIX: How to apply the Apache License to your work.

		To apply the Apache License to your work, attach the following
		boilerplate notice, with the fields enclosed by brackets "[]"
		replaced with your own identifying information. (Don't include
		the brackets!) The text should be enclosed in the appropriate
		comment syntax for the file format. We also recommend that a
		file or class name and description of purpose be included on the
		same "printed page" as the copyright notice for easier
		identification within third-party archives.

		Copyright [yyyy] [name of copyright owner]

		Licensed under the Apache License, Version 2.0 (the "License");
		you may not use this file except in compliance with the License.
		You may obtain a copy of the License at

		http://www.apache.org/licenses/LICENSE-2.0

		Unless required by applicable law or agreed to in writing, software
		distributed under the License is distributed on an "AS IS" BASIS,
		WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
		See the License for the specific language governing permissions and
		limitations under the License.

+109

pvrecorder/node_mo...corder-node/lib/windows/arm64/NOTICE.md

		# Vendored modification of `@picovoice/pvrecorder-node` (Windows ARM64 prebuild)

		This directory contains a single locally-built Windows ARM64 prebuild of the
		`pv_recorder.node` native module that ships with `@picovoice/pvrecorder-node`.
		It is used to override the upstream prebuild for SEA builds — see
		`script/cli-package-json.js` for the wire-up.

		## Upstream package

		- Name: `@picovoice/pvrecorder-node`
		- Version pinned against: `1.2.8`
		- Source: <https://github.com/Picovoice/pvrecorder>
		- License: Apache License, Version 2.0

		> Copyright 2021-2024 Picovoice Inc.
		>
		> Licensed under the Apache License, Version 2.0 (the "License"); you may not
		> use this file except in compliance with the License. You may obtain a copy of
		> the License at <http://www.apache.org/licenses/LICENSE-2.0>.

		The full Apache 2.0 license text is at the URL above. The upstream npm package
		does not ship a `LICENSE` file; the canonical text lives in the source
		repository linked above.

		## What was modified

		In compliance with Section 4(b) of the Apache 2.0 license, this notice states
		the change made to the upstream source before this binary was built:

		In `project/node/CMakeLists.txt`, after the existing block that adds
		`delayhook.c` to the `windows-amd64` and `windows-arm64` builds, the following
		block was added so that `node.exe` is delay-loaded on Windows ARM64:

		```cmake
		# Delay-load node.exe so that Node API calls resolve to the host process,
		# even when it isn't named node.exe (e.g., SEA builds, Electron, embedders).
		if (${PV_RECORDER_PLATFORM} STREQUAL "windows-arm64")
		target_link_options(pv_recorder_napi PRIVATE "LINKER:--delayload=node.exe")
		endif()
		```

		No other files in the upstream source were modified.

		## Why

		The upstream Windows ARM64 prebuild of `pv_recorder.node` _statically_ imports
		`node.exe`. When the binary is loaded inside a Single Executable Application
		(SEA) where the host process is `copilot.exe`, the Windows loader resolves the
		static `node.exe` import by searching `PATH` and maps a _second_ `node.exe`
		image into the process. The pvrecorder NAPI calls then go through the second
		Node's exports while operating on `napi_env` values issued by the SEA's
		embedded Node, producing memory corruption and a hard crash on the first NAPI
		call after init.

		The upstream binding already includes `project/node/delayhook.c`, which
		implements `__pfnDliNotifyHook2` to redirect delay-load resolutions of
		`node.exe` to `GetModuleHandle(NULL)` — i.e. to whatever EXE is hosting the
		process (which inside our SEA is `copilot.exe`, and `copilot.exe`'s export
		table is a superset of `node.exe`'s because the SEA was minted from
		`node.exe`). However, the linker is never told to delay-load `node.exe`, so
		the import remains static and the hook is dead code. The one-line change above
		enables the existing fix.

		The upstream amd64 prebuild does not have this bug — it imports its C runtime
		from `msvcrt.dll` and does not import from `node.exe` at all — so the change
		is intentionally scoped to `windows-arm64` only.

		## How to reproduce this build

		The change above was applied on top of upstream commit
		[`a69cfd644896ec69bc1b06e0fd6a6394be77a6bc`](https://github.com/Picovoice/pvrecorder/commit/a69cfd644896ec69bc1b06e0fd6a6394be77a6bc)
		(the latest `main` at the time the binary was built).

		1. Clone <https://github.com/Picovoice/pvrecorder> and check out the commit
		above (or a later commit, if you have verified the relevant CMake file has
		not diverged).
		2. Apply the CMake diff shown in [What was modified](#what-was-modified).
		3. On a Windows ARM64 machine, install MSYS2 and the CLANGARM64 toolchain
		(`mingw-w64-clang-aarch64-toolchain`, `-cmake`, `-make`, `-binutils`).
		4. From the MSYS2 CLANGARM64 shell:

		```bash
		cd <pvrecorder>/project/node
		mkdir build && cd build
		cmake .. -G "MinGW Makefiles" \
		-DPV_RECORDER_PLATFORM=windows-arm64 \
		-DPV_WINDOWS_NODE_ARCH=win-arm64 \
		-DOUTPUT_DIR=windows/arm64
		cmake --build .
		```

		5. The output is `<pvrecorder>/lib/node/windows/arm64/pv_recorder.node`.

		To verify the fix is present in the resulting binary, parse its PE imports and
		confirm `node.exe` appears under the delay import directory and not under
		the regular import directory.

		## Lifecycle

		This vendored binary exists only to bridge the gap until the equivalent
		upstream change is accepted and released by Picovoice. Once a published
		`@picovoice/pvrecorder-node` release ships with the delay-load fix, this
		override should be deleted and the wire-up in `script/cli-package-json.js`
		removed.

		The CI script `npm run check:pvrecorder-vendored` fails the build whenever the
		installed `@picovoice/pvrecorder-node` version diverges from the pinned
		version above, prompting human re-evaluation of whether the override is still
		needed.

+8

-8

package.json

		{
		"name": "@github/copilot",
		"description": "GitHub Copilot CLI brings the power of Copilot coding agent directly to your terminal.",
		"version": "1.0.43",
		"version": "1.0.44-0",
		"license": "SEE LICENSE IN LICENSE.md",
		@@ -72,12 +72,12 @@ "type": "module",
		"buildMetadata": {
		"gitCommit": "f4baa20"
		"gitCommit": "0f16607"
		},
		"optionalDependencies": {
		"@github/copilot-linux-x64": "1.0.43",
		"@github/copilot-linux-arm64": "1.0.43",
		"@github/copilot-darwin-x64": "1.0.43",
		"@github/copilot-darwin-arm64": "1.0.43",
		"@github/copilot-win32-x64": "1.0.43",
		"@github/copilot-win32-arm64": "1.0.43"
		"@github/copilot-linux-x64": "1.0.44-0",
		"@github/copilot-linux-arm64": "1.0.44-0",
		"@github/copilot-darwin-x64": "1.0.44-0",
		"@github/copilot-darwin-arm64": "1.0.44-0",
		"@github/copilot-win32-x64": "1.0.44-0",
		"@github/copilot-win32-arm64": "1.0.44-0"
		}
		}

-48

definitions/configure-copilot.agent.yaml

		name: configure-copilot
		displayName: Configure Copilot
		description: >
		Manages Copilot CLI MCP server configuration. Use when the user wants to add,
		remove, or modify MCP servers.
		model: claude-haiku-4.5
		contexts:
		- cli
		tools:
		- bash
		- read_bash
		- stop_bash
		- powershell
		- read_powershell
		- stop_powershell
		- view
		- edit
		- create
		- glob
		- grep
		- mcp_validate
		- mcp_reload
		promptParts:
		includeAISafety: true
		includeToolInstructions: true
		includeParallelToolCalling: true
		includeCustomAgentInstructions: false
		includeEnvironmentContext: true
		prompt: \|
		You are a configuration agent for the Copilot CLI. You help users add, remove, and modify MCP server configurations.

		## MCP Server Config Files

		- User config: {{configDir}}/mcp-config.json
		- Project config: {{cwd}}/.mcp.json

		## Server Config Schema

		User config wraps servers in `{ "mcpServers": { ... } }`. Server names must match `/{{serverNamePattern}}/`.
		Project/workspace configs use `{ "servers": { ... } }` and support `${input:id}` variable references.

		{{mcpSchema}}

		Environment values support `$VAR` and `${VAR:-default}` expansion.

		## After Editing

		After editing a config file, call mcp_validate to check for errors, then call mcp_reload to apply changes.

app.js

Sorry, the diff of this file is too big to display

changelog.json

Sorry, the diff of this file is too big to display

koffi/build/koffi/win32_arm64/koffi.node