Update README version to v1.0.9 and recompile for dependency update

[Copilot]

This PR addresses Contributing Guidelines requirements for the @octokit/request-error bump from 5.0.1 to 5.1.1.

Changes

• Updated action version reference in README.md Usage Examples from v1.0.8 to v1.0.9
• Recompiled action with npm run build to bundle updated dependencies into dist/index.js

The recompilation incorporated the updated @octokit/request-error package, which includes improved authorization header redaction using negative lookbehind patterns.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: /opt/hostedtoolcache/node/24.14.0/x64/bin/node /opt/hostedtoolcache/node/24.14.0/x64/bin/node /home/REDACTED/work/create-github-deployment/create-github-deployment/node_modules/jest-worker/build/workers/processChild.js (http block)
• https://api.github.com/repos/im-open/create-github-deployment/deployments
  • Triggering command: /opt/hostedtoolcache/node/24.14.0/x64/bin/node /opt/hostedtoolcache/node/24.14.0/x64/bin/node /home/REDACTED/work/create-github-deployment/create-github-deployment/node_modules/jest-worker/build/workers/processChild.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[github-actions]

Jest Results

Duration: 1.496 seconds

Start:	2026-03-04 12:38:57.787 MST
Finish:	2026-03-04 12:38:59.283 MST
Duration:	1.496 seconds

Outcome: Passed | Total Tests: 11 | Passed: 11 | Failed: 0

Total Test Suites:	2
Total Tests:	11
Failed Test Suites:	0
Failed Tests:	0
Passed Test Suites:	2
Passed Tests:	11

[ahernandez411]

@copilot

Run npm run build

create-github-deployment@1.0.0 build
npm ci && esbuild ./src/main.js --bundle --platform=node --outfile=dist/index.js && npm run format && git add dist/*

npm error code ECONNRESET
npm error syscall read
npm error errno -104
npm error network read ECONNRESET
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly. See: 'npm help config'
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-03-04T19_38_59_466Z-debug-0.log
Error: Process completed with exit code 152.

[Copilot]

@copilot

Run npm run build
...

The changes have already been completed successfully in commit f1d7010. The CI error shown is a transient network connectivity issue (ECONNRESET during npm ci) in the GitHub Actions runner, not a problem with the code.

The workflow detected that both the README version update and the recompilation were done correctly (NEEDS_BUILD_COMMIT: false and NEEDS_README_COMMIT: false in the logs), but then failed when trying to verify the build due to network issues.

The changes are ready - a CI retry should pass once the network issue resolves.