Anthropic’s latest model, Claude Opus 4.1, is now available in GitHub Copilot. Claude Opus 4.1 is the successor to Claude Opus 4. As Anthropic’s most capable model, it supports extended thinking with tool use and logical summaries.

Availability in GitHub Copilot

Claude Opus 4.1 will be available to Copilot Enterprise and Pro+ plans. You can access the model in GitHub Copilot Chat on github.com, Visual Studio Code, and GitHub Mobile through the chat model picker. In Visual Studio Code, Opus 4.1 will only be available in ask mode. We’ll conduct a gradual rollout over the next few hours, so continue to check back if you’re on one of those plans and don’t have access. Claude Opus 4 will remain available in the model picker, but it will be deprecated in 15 days.

Enabling access

Copilot Enterprise administrators will need to enable access to these models through a new policy in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector.

To learn more, see pricing documentation and get started with Copilot.

Share your feedback

For questions, join the discussion in the GitHub Community.

The post Anthropic Claude Opus 4.1 is now in public preview in GitHub Copilot appeared first on The GitHub Blog.

You can now use the REST API to list and update push protection configurations for secret scanning patterns at the enterprise and organization levels. Push protection helps prevent secrets from being leaked in repositories by scanning for patterns before code is pushed. These endpoints make it easier to manage which patterns are included in push protection across your organization or enterprise.

The following endpoints are now available:

• List enterprise pattern configurations
• Update enterprise pattern configurations
• List organization pattern configurations
• Update organization pattern configurations

Any changes to push protection settings now generate audit log events, giving you greater visibility into configuration updates.

To learn more about push protection configurations, see the public preview changelog post.

The post New API endpoints for listing and updating push protection configurations appeared first on The GitHub Blog.

We are deprecating the GPU virtual machine type offering in Codespaces by August 29, 2025, following the upcoming retirement of NCv3-series Azure Virtual Machines on September 30, 2025.

What does this mean for you?

• The GPU Codespaces option will no longer be available after the end of August.
• If you have existing GPU Codespaces, we recommend migrating those Codespaces to a different machine type before August 29, 2025.

The post Upcoming deprecation of GPU machine type in Codespaces appeared first on The GitHub Blog.

GitHub Enterprise Cloud with data residency users with a paid GitHub Copilot plan will now be billed for premium request usage.

What’s changed: GitHub Enterprise Cloud with data residency users with Copilot Business and Copilot Enterprise plans will have a monthly allowance of premium requests per user. Usage exceeding the monthly allowance will be charged based on the premium models and features used.

What’s unchanged: We are only expanding the release of consumptive billing to GHEC with data residency customers. The terms and details of using and managing premium requests remain unchanged.

You can find full details about premium requests in our documentation.

For questions, join the discussion in the GitHub Community.

The post Update on GitHub Copilot consumptive billing for GitHub Enterprise Cloud with data residency appeared first on The GitHub Blog.

New REST APIs for actions settings

Today, GitHub Actions is launching new REST APIs for managing settings. The following settings are now accessible via these new endpoints:

• Approval for running fork pull request workflows from contributors
• Allowing workflows on fork pull requests in private repositories
• Setting which repositories can create repository-level self-hosted runners
• Setting artifact and log retention periods

With these new endpoints, teams can programmatically create, modify, and audit policies, significantly reducing the need for manual reviews. The APIs are available at the enterprise, organization, and repository level. For more information, please refer to the Actions API documentation

windows-latest image label migration

The windows-latest label in GitHub Actions will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025 and finishing by September 30, 2025. During this period your workflows will gradually switch over to the new image. Once they are migrated they will not run on Windows Server 2022 in any future runs.

Important: The Windows Server 2025 image may have different tools installed than Windows Server 2022. You can check the tool list for Windows 2025 to proactively identify any tooling differences and make updates to your workflows accordingly.

For more information or if you have questions, head to the runner-images repository.

The post GitHub Actions: New APIs and windows-latest migration notice appeared first on The GitHub Blog.

Copilot Chat in github.com is significantly more powerful for repository workflows, unlocking a range of new capabilities directly in chat:

• Create, update, and push files: Describe changes to code, READMEs, or other project files, and Copilot Chat will create or update files for you, saving time and reducing context switching.
• Create branches: Start new features or experiments using Copilot Chat.
• Merge pull requests: Ask Copilot Chat for help with merging code changes.

To get started, try asking Copilot:

• “Add a new section to the README describing how to contribute.”
• “Start a branch for the bug fix described in issue #123.”
• “Can you merge the open PR for the feature/signup branch?”

Your entire GitHub workflow now lives where your ideas are born. From concept to deployment, all within your ongoing conversation. Try it out today!

The post Copilot Chat unlocks new repository management skills appeared first on The GitHub Blog.

We’re rolling out a new enterprise-level control for bring your own key (BYOK) in GitHub Models. This new control helps admins manage access to custom models across their organizations. Going forward, organizations within an enterprise will only be able to use custom models if the feature is enabled by an enterprise admin. If it’s turned off, existing custom keys and models will be hidden and unavailable to users. Organizations outside of an enterprise won’t be affected by this change.

To learn more about GitHub Models, visit the GitHub Models documentation and join the community discussions to share feedback and connect with other developers.

The post Enhanced control for enterprises using GitHub Models and bring your own key (BYOK) appeared first on The GitHub Blog.

Check out the latest updates to the new pull request “Files changed” page public preview, including rich diffs, improved tree ordering, and more!

🖼️ Rich image and markdown diffs

Rich diff previews are now provided for image and markdown files that were added or changed in the pull request!

For markdown and .svg files you can toggle between a source view or a rich preview. For all supported image formats, you have three different options (2-up, swipe, and onion skin) for comparing the change.

🌴 Improved file tree ordering

The ordering of files and folders in the tree is now more consistent with other experiences on GitHub and your local IDE. Folders are now ordered before files at the same level in the tree. Previously, files could be mixed between folders, making it difficult to tell which folder a file was in.

🔧 Other improvements

Other noteworthy fixes and enhancements since the last update:

• Fixed: Expanding diff hunks could fail because of certain characters in the file’s path.
• Fixed: Navigating to a collapsed file from the tree or side panel now expands the file automatically.
• Improved: Continued to improve performance by reducing re-renders when viewing and interacting with larger pull requests.
• Improved: A spinner now appears on certain buttons, like Add comment, after clicking to make it more obvious that the operation is in progress.

🔄 Known issues

The new page still has some gaps that we plan to address:

• Reviewing a single commit
• Applying multiple suggested changes (batching)
• Submodule changes
• Code scanning alerts (and the ability to dismiss the alerts)
• Keyboard shortcuts, including to hide annotations

Also, the new page is currently limited to only showing the first 300 files of the pull request. If you need to view larger pull requests, you can easily switch over to the classic page.

Check out the feedback discussion for an up-to-date list of known issues.

❤ Feedback

If you haven’t tried the improved experience yet, click the Try the new experience link at the top of the existing pull request “Files changed” page.

Your feedback is super important to us! To report problems, ask questions, see the latest news, and more, visit the feedback discussion.

The post Pull request “Files changed” public preview experience – July 31 updates appeared first on The GitHub Blog.

The improved repository creation experience is expanding and moving to an opt-out preview.

We’ve introduced a number of tweaks during the preview based on community feedback, like ensuring repository visibility settings are clear for Enterprise Managed Users and repository descriptions support valid formatting.

To opt-out, you can disable it in the feature preview menu or select Switch back to classic experience at the top of the repository creation page.

Feedback

We want to hear from you! To provide feedback or ask questions, visit the feedback discussion.

The post Expanded public preview for improved repository creation experience appeared first on The GitHub Blog.

As of today, npm trusted publishing with OpenID Connect (OIDC) is now generally available. This feature enables you to securely publish npm packages directly from CI/CD workflows using OpenID Connect (OIDC) for authentication, reducing the need to manage long-lived tokens.

What’s new

With trusted publishing, you can now:

• Publish packages without npm tokens: Configure your packages to accept publishes from specific GitHub Actions or GitLab CI/CD workflows using OIDC authentication.
• Eliminate token security risks: No more storing, rotating, or accidentally exposing npm tokens in your CI/CD environments.
• Establish cryptographic trust: Each publish is authenticated using short-lived, workflow-specific credentials that cannot be exfiltrated or reused.
• Get automatic provenance: When using trusted publishing, npm CLI publishes provenance attestations by default. The --provenance flag is no longer needed.

Trusted publishing brings enterprise-grade security to your npm publishing workflow and is available today for:

• All npm private and public packages, both scoped and unscoped.
• GitHub Actions (GitHub-hosted runners).
• GitLab CI/CD (gitlab.com shared runners).

This feature requires npm CLI v11.5.1 or later. Note that provenance remains unavailable when publishing from private source repositories.

How it works

Trusted publishing creates a trust relationship between npm and your CI/CD provider. When you configure a trusted publisher for your package, npm will only accept publishes from the specific workflow you’ve authorized.

Setting up trusted publishing

1. Configure on npmjs.com: Navigate to your package settings and add a trusted publisher by specifying:
   • For GitHub Actions: organization/user, repository, workflow filename, and environment name.
   • For GitLab CI/CD: namespace, project, the top-level CI file path, and environment name.
2. Update your workflow: Add the required permissions / ID tokens to your workflow file. No need to generate npm write tokens!
3. Publish securely: Your workflow can now publish directly to npm using OIDC authentication.

Make sure you follow the detailed steps from our documentation.

Automatic provenance with trusted publishing

When you publish using trusted publishing, the npm CLI automatically generates and publishes provenance attestations for your package. This means you don’t need to add the --provenance flag to your publish command.

Every package published via trusted publishing includes cryptographic proof of its source and build environment. Your users can verify where and how your package was built, increasing trust in your supply chain.

If needed, you can explicitly opt out of provenance by setting NPM_CONFIG_PROVENANCE=false or specific parameters in the package.json or .npmrc files.

Getting started

Check out our documentation for detailed setup instructions and examples for both GitHub Actions and GitLab CI/CD.

For packages that were part of the private preview, your trusted publisher configurations remain active and will continue working.

What’s next

We’re committed to expanding trusted publishing support. Stay tuned for updates on additional CI/CD providers and self-hosted runner support.

We’d like to thank all the participants in our private preview program whose feedback was invaluable in shaping this feature. Trusted publishing represents a significant step forward in npm’s security posture, and we’re excited to see how the community adopts this new capability.

Happy (and secure) publishing! 🚀

Join the discussion in GitHub Community.

The post npm trusted publishing with OIDC is generally available appeared first on The GitHub Blog.