Have an agent bump a package and open a PR

A contributor used GitHub Copilot to refresh @github/copilot in an SDK repo and get a pull request opened with the dependency and lockfile changes.

Done with GitHub Copilot· Intermediate· Jul 2026

What they did
Steve Sanderson asked GitHub Copilot to move @github/copilot up to 1.0.69-2 in the SDK repo. The agent returned a pull request that updated the package files and lockfile, but it also carried changes into the Node samples and test harness manifests, plus lockfile entries that picked up musl libc qualifiers. The automated PR was visible on the PR page, while the agent’s own activity was mentioned in a comment.
How it went
Sanderson treated the extra edits as acceptable and merged the pull request to keep the repo in step. All 65 checks succeeded. The added lockfile noise was probably caused by a different toolchain version.
Tips
If your agent runs under a toolchain that does not match your automation, expect unrelated lockfile differences. Review any manifest changes outside the target dependency before you merge.

Try it yourself with GitHub Copilot

In [owner/repo], raise [package name] from [current version] to [target version]. Limit the edit to the package manifest and the lockfile, then open a pull request. If the agent makes any additional lockfile or manifest changes, call them out separately in the PR description and pause for my approval before keeping them. Run [test command] and summarize the outcome, then end the task once the PR is open and do not merge, delete, or submit anything further without my confirmation.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.