DevOps Weekly Update

As previously communicated for the GitHub Actions Get workflow usage and Get workflow run usage endpoints, we’re closing down the remaining product-specific billing APIs for Actions, Packages, and shared storage.

The following product-specific billing endpoints for enterprises, organizations, and users are no longer supported:

• /settings/billing/actions
• /settings/billing/packages
• /settings/billing/shared-storage

All GitHub users now have access to a consolidated usage endpoint that provides usage details about all GitHub metered products. To learn more, refer to Migrating from the endpoints used for the previous billing platform.

The post Product-specific billing APIs are closing down appeared first on The GitHub Blog.

Copilot coding agent is our asynchronous, autonomous background agent. Delegate a task to Copilot, and it opens a draft pull request, makes changes in the background, then requests a review from you.

The GitHub CLI 2.80.0 release introduces the agent-task command set for managing coding agent tasks in gh:

• Start a new task: gh agent-task create "refactor the codebase"
• List all your tasks: gh agent-task list
• View task details: gh agent-task view 1234
• View the task log in real-time: gh agent-task view 1234 --log --follow

The agent-task command set also ships with the following aliases for convenience:

• gh agent-tasks
• gh agent
• gh agents

For more information about command line flags and arguments, run gh agent-task --help.

The post Kick off and track Copilot coding agent sessions from the GitHub CLI appeared first on The GitHub Blog.

Following the release of using Copilot to create issues, we’re making issue creation even smarter. You can now ask Copilot to include relevant code snippets and files directly into your issues on github.com/copilot.

You can now:

• Create an issue and ask Copilot to attach related code snippets or files.
• Add snippets after Copilot’s initial draft.
• Review and edit Copilot’s suggestions before creating the issue.

Try it out

1. Navigate to github.com/copilot.
2. Try prompts like: “Create me an issue for YOUR-PROMPT-HERE in YOUR-ORGANIZATION/YOUR-REPOSITORY and add relevant code snippets.”

Helpful tips

• Snippets aren’t added by default, so be sure to prompt Copilot to include them.
• Copilot may make mistakes, so always double-check the snippets and files it suggests.
• Be specific with your prompts to get the most useful results.

With this update, issues can carry richer context from the start, helping you maintain continuity from reporting to implementation.

The post Copilot can create issues with code snippets in public preview appeared first on The GitHub Blog.

We have a major update to announce to the new pull request “Files changed” page: you can now comment anywhere in a changed file! 🎉 This feature and the new “Files changed” page are both in public preview.

💬 Comment anywhere in a changed file

Using the new “Files changed” page, you can now comment on any line of a changed file!

This is useful when you need to:

• Flag a change that should have been made.
• Suggest changes to lines beyond the lines surrounding the change.
• As an author, provide additional context to reviewers about an unchanged part of a file.

Previously, you could only comment on the three lines surrounding a change.

How it works

To add a comment to an unchanged line of any file changed in a pull request:

1. Navigate to the new “Files changed” page.
2. Select a changed file and expand all or part of the diff to reveal unchanged lines.
3. Click the + on a line and add your comment or include a suggested change, just like you normally would.

These comments will appear on the new “Files changed” and the “Conversation” pages.

Note: This feature is rolling out gradually on a per-repository basis.

Considerations

1. If using the classic “Files changed” page to view a pull request with comments on unchanged lines, a warning message will appear explaining that there are additional comments only available on the new page.
2. These comments can only be added to files already changed (i.e., not unchanged files).
3. API support is currently limited, but comments on unchanged lines will be returned by existing APIs and in webhook events.
4. This feature changes the positioning logic for comments in general. If you notice any issues with comment positioning, let us know.

🚀 Single file mode improvements

Single file mode, announced in the last update to help you view larger pull requests, has been improved:

• New: Marking a file as viewed automatically moves you to the next file.
• Fixed: Navigating between files using the Next file or Previous file buttons now honors any file filters you have applied.
• New: Keyboard shortcuts are now available for navigating to the next (J) or previous (K) file.
• Improved: To reduce confusion, a message now appears at the bottom of the page when the page is in single file mode.
• Improved: Large and deleted files, which are not rendered by default, no longer influence the decision to apply single file mode.
• Fixed: Various bugs related to unnecessary fetch requests, filtering, and more have been addressed.

📣 Feedback

Your feedback is super important to us! Visit us in the GitHub community:

• Feedback on the new “Files changed” page
• Feedback on the feature enabling you to comment on any line

Disclaimer: The UI for features in public preview is subject to change.

The post Pull request “Files changed” public preview now supports commenting on unchanged lines appeared first on The GitHub Blog.

We’re announcing the scheduled deprecation of the GitHub Copilot in the CLI extension for GitHub CLI (i.e., gh-copilot) which will stop working on October 25, 2025. This extension’s capabilities are being replaced by the new GitHub Copilot CLI, a fully agentic AI assistant that provides the full power of Copilot’s coding agent locally in your terminal.

What’s changing

• The gh-copilot extension will be deprecated and stop functioning on October 25, 2025.
• Enterprise customers with the “Copilot in the CLI” policy currently enabled will notice we’re automatically disabling this policy. We’re doing this so administrators can review whether to allow access to the new Copilot CLI, which is now in public preview.
• The new Copilot CLI provides a much more powerful, agentic experience compared to the limited suggestion capabilities of gh-copilot.

Migration and alternatives

• Copilot Pro and Enterprise users: We recommend migrating to the new GitHub Copilot CLI, which offers enhanced agentic capabilities.
• Free plan users: Since the new Copilot CLI isn’t available on the free plan, we recommend using Ask mode in Visual Studio Code to get explanations and command suggestions. Alternatively, you could explore the gh-models extension to interact with AI models via the GitHub CLI.

For more information about the new GitHub Copilot CLI, visit the GitHub Copilot CLI repository.

The post Upcoming deprecation of gh-copilot CLI extension appeared first on The GitHub Blog.

GitHub Copilot CLI is now in public preview

We’re bringing the power of GitHub Copilot coding agent directly to your terminal. With GitHub Copilot CLI, you can work locally and synchronously with an AI agent that understands your code and GitHub context.

What’s new:

• Terminal-native development: Work with Copilot coding agent directly in your command line — no context switching required.
• GitHub integration out of the box: Access your repositories, issues, and pull requests using natural language, all authenticated with your existing GitHub account.
• Agentic capabilities: Build, edit, debug, and refactor code with an AI collaborator that can plan and execute complex tasks.
• MCP-powered extensibility: Take advantage of the fact that the coding agent ships with GitHub’s MCP server by default and supports custom MCP servers to extend capabilities.
• Full control: Preview every action before execution — nothing happens without your explicit approval.

Getting started is simple:

1. Install via npm: npm install -g @github/copilot
2. Authenticate with your GitHub account.
3. Start building with your existing Copilot Pro, Pro+, Business, or Enterprise plan.

Whether you’re exploring a new codebase, implementing features from issues, or debugging locally, Copilot CLI brings intelligent assistance right where developers work.

Ready to get started?

• Install Copilot CLI today.

Looking for more information?

• Read the documentation
• Learn more about Copilot coding agent
• Check out our product page

The post GitHub Copilot CLI is now in public preview appeared first on The GitHub Blog.

Copilot coding agent, our asynchronous, autonomous developer agent, is now generally available for all paid Copilot subscribers.

Delegate a task to Copilot, and Copilot will open a draft pull request and work in the background in its own development environment. It does this through the power of GitHub Actions. Once Copilot is done, it will request a review from you, and you can ask Copilot to make changes by leaving comments on the pull request.

Copilot coding agent has already been used to create more than 1,000,000 pull requests since it launched in public preview in May.

Copilot coding agent can complete a wide range of software development tasks including:

• Implementing new features
• Fixing bugs
• Addressing technical debt
• Improving test coverage
• Updating documentation

There are many ways to hand tasks to Copilot, including assigning it an issue, using the agents panel accessible on every page on GitHub, or using the Delegate to coding agent button in Visual Studio Code.

To learn more about Copilot coding agent, head to our documentation.

If you’re a Copilot Business or Copilot Enterprise subscriber, an administrator will have to enable Copilot coding agent from the “Policies” page before you can use it.

The post Copilot coding agent is now generally available appeared first on The GitHub Blog.

Ever wish Copilot understood your project as well as your teammates do? Now it can.

With GitHub Copilot Spaces, you can bring together the context it needs — files, pull requests, issues, and repos — so that Copilot’s responses are always grounded in your project. With spaces, Copilot doesn’t just generate output. Copilot understands your systems, your standards, and your open tasks.

👩‍💻 Turn Copilot into a project expert


Spaces ground Copilot in curated files, docs, pull requests, and issues so that it can generate code, explain system design, and suggest solutions that follow your team’s standards. You can add custom instructions to make responses even more specific to your workflow.

⚖️ Scale expertise across teams


Spaces make knowledge collaborative. You can share a space across your org so that teammates can access the same project context and get unblocked faster. Instead of repeating the same explanations, your space becomes a living knowledge hub for files uploaded to a GitHub repository.

⏲️ Always up to date


Your code is already safely stored on GitHub, and adding it to a space is seamless. You just attach it directly from your repository, no copy and paste required. Once attached, files and repositories stay in sync as they evolve, making Copilot an evergreen expert in your project.

🖥️ Spaces in your IDE

This release to general availability adds the option to access spaces directly in your IDE through the remote GitHub MCP server,

📂 Examples of how
teams are already using Copilot Spaces

• Generating code that follows security patterns, API standards, and team preferences.
• Sharing knowledge like SQL/KQL queries, telemetry schemas, or best-practice auth docs.
• Onboarding new developers by giving them instant access to curated project knowledge.
• Planning projects and create issues by centralizing PRDs and decisions in one space.

💬 Get started

• Try Copilot Spaces today at github.com/copilot/spaces. Spaces are currently available in github.com for all Copilot users.
• Provide feedback in the Copilot Spaces community discussion or using the inline Give feedback button in the UI.
• Learn more about spaces in our documentation on Copilot Spaces.
• Copilot Spaces follow the same billing model as Copilot Chat.

The post Copilot Spaces is now generally available appeared first on The GitHub Blog.

Last month, we began testing improvements to the content and layout of the home dashboard and enabled it for a small subset of users. That test is over and we have returned the dashboard to its original state, focused on the feed.

What’s changed

• Users that were automatically added to the feature preview are now removed.
• All users will see the feed on their home dashboard.

The post Recent changes to the home dashboard disabled appeared first on The GitHub Blog.

With GitHub Copilot coding agent on GitHub Mobile, you can delegate tasks to Copilot and let it handle them in the background while you’re on the go.

We’ve got two major additions to the Copilot coding agent experience on GitHub Mobile:

Kick off new tasks while you’re on the go

You can now ask Copilot to start a new coding task directly from Home or the Repository view. Simply tap the + button, choose your repository, and enter your prompt. Copilot will create a draft pull request, work in the background, and tag you for review once it’s ready. If you have push notifications enabled on mobile, you’ll also receive a notification when your draft is ready.

Track the status of all your Copilot coding agents’ work

You can now easily access the Agents page from Home on the mobile app. Just tap the Agents section under the My Work section to see a list of your Copilot coding agent tasks. This provides a centralized view of all your agent tasks at a glance, making it simple to stay on top of your work from anywhere.

Join the discussion within GitHub Community.

The post Start and track Copilot coding agent tasks in GitHub Mobile appeared first on The GitHub Blog.

4.46.0 (September 25, 2025)

ENHANCEMENTS:

• dependencies: frontdoor/webapplicationfirewallpolicies - update to API version 2025-03-01 (#29742)
• azurerm_cdn_frontdoor_firewall_policy - support for the captcha_cookie_expiration_in_minutes property and the CAPTCHA value in the custom_rule.action property (#29742)
• azurerm_cdn_frontdoor_security_policy - add update ability (#30299)
• azurerm_cognitive_account - add support for C2, C3, C4, D3, and S1 to sku_name (#30655)
• azurerm_flex_function_app - add support for the http_concurrency property (#29678)
• azurerm_kubernetes_cluster - add support for the api_server_access_profile.virtual_network_integration_enabled and api_server_access_profile.subnet_id properties (#30559)
• azurerm_machine_learning_workspace - add support for the service_side_encryption_enabled property (#30478)
• azurerm_mysql_flexible_server - add support for the managed_hsm_key_id property (#30502)
• azurerm_netapp_volume - add support for updating protocols (#30643)
• azurerm_netapp_volume_group_oracle - add support for updating protocols (#30643)
• azurerm_netapp_volume_group_sap_hana - add support for updating protocols (#30643)
• azurerm_postgresql_flexible_server - add support for the 17 value in the version property (#30683)
• azurerm_storage_queue - add support for the storage_account_id property (#28752)

BUG FIXES:

• azurerm_cdn_frontdoor_firewall_policy - fix the read function so it now correctly marks the resource as gone (#30704)

4.45.1 (September 22, 2025)

NOTES:

This release contains a Terraform Plugin SDK v2 version bump that prevents identity change validation from raising an error when prior identity is empty (all attributes are null).

BUG FIXES:

• dependencies: hashicorp/terraform-plugin-sdk/v2 - update to v2.38.1 (#30667)
• azurerm_network_interface - ensure identity is set during non-refresh apply operations (#30667)

1.14.0-beta2 (September 25, 2025)

NEW FEATURES:

• List Resources: List resources can be defined in *.tfquery.hcl files and allow querying and filterting existing infrastructure.

• A new Terraform command terraform query: Executes list operations against existing infrastructure and displays the results. The command can optionally generate configuration for importing results into Terraform.

• A new GenerateResourceConfiguration RPC allows providers to create more precise configuration values during import. (#37515)

• New top-level Actions block: Actions are provider defined and meant to codify use cases outside the normal CRUD model in your Terraform configuration. Providers can define Actions like aws_lambda_invoke or aws_cloudfront_create_invalidation that do something imparative outside of Terraforms normal CRUD model. You can configure such a side-effect with an action block and have actions triggered through the lifecycle of a resource or through passing the -invoke CLI flag. (#37553)

ENHANCEMENTS:

• terraform test: expected diagnostics will be included in test output when running in verbose mode" (#37362)

• terraform test: ignore prevent_destroy attribute during when cleaning up tests" (#37364)

• terraform stacks command support for -help flag (#37645)

BUG FIXES:

• Retrieve all workspace variables while doing a terraform import, include variables inherited from variable sets but not overwritten by the workspace. (#37241)

• Fix OSS backend proxy support by adding a proxy layer for OSS backend operations. Resolves #36897. (#36897)

• console and test: return explicit diagnostics when referencing resources that were not included in the most recent operation. (#37663)

UPGRADE NOTES:

• The parallelism of Terraform operations within container runtimes may be reduced depending on the CPU bandwidth limit setting. (#37436)

• Building Terraform 1.14 requires macOS Monterey or later (due to being built on Go 1.25 which imposes these requirements) (#37436)

Previous Releases

For information on prior major and minor releases, refer to their changelogs:

• v1.13
• v1.12
• v1.11
• v1.10
• v1.9
• v1.8
• v1.7
• v1.6
• v1.5
• v1.4
• v1.3
• v1.2
• v1.1
• v1.0
• v0.15
• v0.14
• v0.13
• v0.12
• v0.11 and earlier

[VAULT-39673] This is an automated pull request to build all artifact…

…s for a release (#31563)

Co-authored-by: Tony Wittinger <anwittin@users.noreply.github.com>

DEPRECATIONS:

• compute: deprecated the option to deploy a container during VM creation using the container startup agent in google_compute_instance. Use alternative services to run containers on your VMs. Learn more at https://cloud.google.com/compute/docs/containers/migrate-containers. (#24375)

FEATURES:

• New Data Source: google_artifact_registry_maven_artifact (#24358)
• New Data Source: google_compute_interconnect_location (#24377)
• New Resource: google_network_services_wasm_plugin (#24406)
• New Resource: google_resource_manager_capability (#24404)

IMPROVEMENTS:

• cloudrunv2: added mount_options in gcsfuse volumes for google_cloud_run_v2_service, google_cloud_run_v2_job, and google_cloud_run_v2_workerpool resources. (#24413)
• compute: added cipher_suite field to google_compute_vpn_tunnel resource. (#24378)
• container: added auto_ipam_config to google_container_cluster resource. (#24396)
• storage: added support for timeouts to google_storage_bucket_iam_binding, google_storage_bucket_iam_member, google_storage_bucket_iam_policy resources (#24376)

BUG FIXES:

• bigtable: fixed node_scaling_factor forcing new instance on google_bigtable_instance when adding new cluster (#24410)
• cloudscheduler: fixed a type assertion panic in google_cloud_scheduler_job when processing HTTP headers with nil or unexpected data types (#24360)
• compute: fixed the Network field cannot be modified issue in google_compute_region_backend_service. Now updating the network field will force the resource to be recreated. (#24398)
• netapp: fixed incorrect default value handling in google_netapp_volume for export_policy.rules attributes has_root_access and squash_mode. When not specified, these fields will now take on the API default value with no diff. (#24395)
• netapp: updated google_netapp_storage_pool to source the default value for the qos_type field from the API. If not specified in the configuration, qos_type will now default to the value provided by the NetApp Volumes API. (#24394)
• sql: fixed the permadiffs on disk_size when disk_autoresize is enabled in google_sql_database_instance (#24399)
• workbench: added retry for unable to queue the operation 409 errors in google_workbench_instance resource. (#24392)

NOTES:

• bigtable: It is recommended for google_bigtable_table_iam_* resources to upgrade to v6.50.0 and switch from instance to instance_name in your configuration before upgrading to v7.X (#24400)

DEPRECATIONS:

• bigtable: deprecated instance in favor of instance_name in google_bigtable_table_iam_* resources (#24400)

IMPROVEMENTS:

• bigtable: added instance_name field to google_bigtable_table_iam_* resources (#24400)

6.14.1 (September 22, 2025)

NOTES:

• provider: This release contains both internal provider fixes and a Terraform Plugin SDK V2 update related to a regression which may impact resources that support resource identity (#44375)

BUG FIXES:

• provider: Fix Missing Resource Identity After Update errors for non-refreshed and failed updates (#44375)
• provider: Fix Unexpected Identity Change errors when fully-null identity values in state are updated to valid values (#44375)