Starting Tuesday, March 11th, GitHub will onboard Google Cloud Platform and Anthropic PBC as providers of the public preview models Claude 3.5 Sonnet and Claude 3.7 Sonnet.
This change will result in increased Claude Sonnet rate limits and greater service quality in GitHub Copilot when using these models.
Today’s changelog announces API support for issues advanced search, timeline events for issue types, and an update on issue types settings.
You can now use GraphQL and the REST API to perform advanced queries for issues using the AND and OR keywords and nested searches.
For the REST API, you can set the advanced_search parameter to true. Check out the REST API documentation for more details.
http://api.github.com/search/issues?q={query}&advanced_search=true
For GraphQL, you can use the ISSUE_ADVANCED type. Check out the GraphQL documentation for more details.
query {
search(query: "is:issue AND assignee:@me AND (label:support OR comments:>5)", type: ISSUE_ADVANCED, first: 10) {
nodes {
... on Node {
id
}
}
issueCount
}
}
Note that on September 4, 2025, all issue queries will use advanced search by default. This means that after this date:
advanced_search parameter for the REST API. ISSUE GraphQL type will support advanced search. You can now see events in the issue timeline when issue types are added, updated, and removed from an issue.
We are retiring the “Private repositories only” setting for issue types. Over the next week, you will no longer be allowed select this setting to specify an issue type for use only in private repositories, and all existing issue types with this setting selected will be removed on March 26, 2025.
In order to continue using these issue types, you will need to unselect the “Private repositories only” setting in the issue types organization settings page before this date. They can then be edited, disabled, or deleted as needed.
Join the discussion within the GitHub Community.
See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the documentation.
Today, we released an upgrade to the GPT-4o Copilot preview model for code completion.
The GPT-4o Copilot model released last month has been upgraded through reinforcement learning to deliver even more useful code completions.
This upgraded model is available today in public preview under the same gpt-4o-copilot name, with general availability expected in mid-April 2025.
To get started in Visual Studio Code or JetBrains, follow the instructions for your preferred IDE.
If you’re a Copilot Business or Enterprise user, your administrator first needs to enable this model for your organization by opting in to Editor preview features in the Copilot policy settings on github.com.
Personal instructions are now generally available for Copilot Chat on github.com! This means you can provide Copilot with important details about your preferences, such as your preferred language, response style, or even code standards.
To get started, open up Copilot Chat, click ..., and select Personal instructions. That’s it! Copilot will now incorporate your preferences for all chats in github.com.
💡 Looking for ideas? Here are some examples to kick things off:
Copilot features can go through different early access stages, which are typically enabled and configured through settings. The possible stages are as follows:
Last month, we introduced agent mode for Copilot Edits in VS Code Insiders. In agent mode, Copilot can automatically search your workspace for relevant context, edit files, check them for errors, and run terminal commands (with your permission) to complete a task end-to-end.
Agent mode is available today in VS Code Insiders, and we just started rolling it out gradually in VS Code Stable. Once you have agent mode enabled, you’ll see a mode dropdown in the Copilot Edits view — simply select Agent.
We made several improvements to the UX of tool usages this month:
Ctrl + Enter shortcut.Agent mode autonomously searches your codebase for relevant context. Expand the message to see the results of which searches were done.
We’ve also made various improvements to the prompt and behavior of agent mode:
github.copilot.chat.agent.runTasks if the model runs tasks when it shouldn’t.Learn more about Copilot Edits agent mode or read the agent mode announcement blog post.
If you are a Copilot Business or Enterprise user, an administrator of your organization must opt in to “Editor Preview Features” for agent mode to be available.
You can now use Copilot to edit notebook files with the same intuitive experience as editing code files. Create new notebooks from scratch, modify content across multiple cells, insert and delete cells, and change cell types. This preview feature provides a seamless workflow when working with data science or documentation notebooks.
We recommend using VS Code Insiders and the pre-release version of GitHub Copilot Chat to get the best notebook editing experience with Copilot.
We have polished the integration of Copilot Edits with code and notebook editors:
Files that are attached and not yet sent are now rendered as regular chat attachments. Only files that have been modified with AI are added to the changed files list.
You can use the VS Code setting chat.renderRelatedFiles to enable getting suggestions for related files. Related file suggestions are rendered below the chat attachments.
We removed the limit on the number of files you can attach to your Copilot Edits prompt and the client-side rate limit.
Note that service-side usage rate limits still apply.
Custom instructions enable you to tailor GitHub Copilot to provide chat responses and code suggestions to the way you and your team work. Describe your specific requirements in a .github/copilot-instructions.md file in your workspace and enable them with the VS Code setting github.copilot.chat.codeGeneration.useInstructionFiles.
Custom instructions are generally available with .github/copilot-instructions.md. Make sure that the github.copilot.chat.codeGeneration.useInstructionFiles setting is enabled to have Copilot use these instructions when generating responses.
Learn more about custom instructions in Copilot.
If you host your source code in a GitHub repository, you can leverage several features, including advanced code searching, the @github chat participant, and more!
However, for private GitHub repositories, VS Code needs to have permission to interact with your repositories on GitHub. For a while, this was presented with our usual VS Code authentication flow, where a modal dialog showed up when you invoked certain functionality (for example, asking @workspace or @github a question, or using the #codebase tool).
To make this experience smoother, we’ve introduced this confirmation in chat:
Not only is it not as jarring as a modal dialog, but it also has new functionality:
@github.github.copilot.advanced.authPermissions. Any feature that needs this additional permission will fail.It’s important to note that this confirmation does not confirm or deny Copilot (the service) access to your repositories. This is only how VS Code’s Copilot experience authenticates. To configure what Copilot can access, please read the docs on content exclusion.
When you add #codebase to your Copilot Chat query, Copilot helps you find relevant code in your workspace for your chat prompt. #codebase can now run tools like text search and file search to pull in additional context from your workspace.
Set the github.copilot.chat.codesearch.enabled VS Code setting to enable this behavior. The full list of tools is:
To help with fixing code or other issues in your workspace, you can now attach problems from the Problems panel to your chat as context for your prompt.
Either drag an item from the Problems panel onto the Chat view, type #problems in your prompt, or select the paperclip 📎 button. You can attach specific problems, all problems in a file, or all files in your codebase.
Previously, you could attach folders as context by using drag and drop from the Explorer view. Now, you can also attach a folder by selecting the paperclip 📎 icon or by typing #folder: followed by the folder name in your chat prompt.
We’ve added a collapsed mode for NES. When you enable this mode, only the NES suggestion indicator is shown in the left editor margin. The code suggestion itself is revealed only when you navigate to it by pressing Tab. Consecutive suggestions are shown immediately until a suggestion is not accepted.
The collapsed mode is disabled by default and can be enabled by configuring editor.inlineSuggest.edits.showCollapsed:true, or you can toggle it in the NES gutter indicator menu.
You can now change the model providing code completions by using the Change Completions Model command in the Command Palette or the Configure Code Completions item in the Copilot menu in the title bar.
If you’re a Copilot Business or Enterprise user, your Administrator needs to enable certain models for your organization by opting in to Editor Preview Features in the Copilot policy settings on github.com.
This release, we added more models to choose from when using Copilot. The following models are now available in the model picker in Visual Studio Code and Copilot Chat on github.com:
Claude 3.7 Sonnet: Claude 3.7 Sonnet is now in preview for all customers on paid Copilot plans. This new Sonnet model supports both thinking and non-thinking modes in Copilot. In initial testing, we’ve seen particularly strong improvements in agentic scenarios. Learn more about the Claude 3.7 Sonnet model availability in the GitHub blog post.
We’re quickly rolling out end-to-end Copilot Vision support in this version of Copilot Chat. This lets you attach images and interact with images in chat prompts. For example, if you encounter an error while debugging, attach a screenshot of VS Code, and ask Copilot to help you resolve the issue. You could also use it to attach a UI mockup and let Copilot provide some HTML and CSS to implement the mockup.
You can attach images in multiple ways:
A warning is shown if the selected model currently does not have the capability to handle the file type. GPT 4o is the only model currently supporting images. You can provide JPEG/JPG, PNG, GIF, and WEBP image types. Claude 3.5 Sonnet and Gemini 2.0 Flash will soon support images as well.
We are experimenting with a new centralized Copilot status overview that provides a quick overview of your Copilot status and key editor settings. You can enable the Copilot status overview with the VS Code setting chat.experimental.statusIndicator.enabled. It includes the following changes:
This Copilot status overview is accessible via the Copilot icon in the Status Bar.
We are experimenting with enhanced context for inline completions and /fix commands for TypeScript files. The experiment is currently scoped to Insider releases and can be enabled with the chat.languageContext.typescript.enabled setting.
You can provide custom instructions for generating pull request title and description with the setting github.copilot.chat.pullRequestDescriptionGeneration.instructions. You can point the setting to a file in your workspace, or you can provide instructions inline in your settings. Get more details about customizing Copilot in VS Code.
The following sample shows how to provide a custom instruction inline in settings.
{
"github.copilot.chat.pullRequestDescriptionGeneration.instructions": [
{
"text": "Prefix every PR title with an emoji."
}
]
}
You need to have the GitHub Pull Requests extension installed to generate a title and description.
We made Copilot Edits more accessible.
F7 to enable it.We have a new window.title variable, activeEditorState, to indicate editor information such as modified state, the number of problems, and when a file has pending Copilot Edits to screen reader users. When in Screen Reader Optimized mode, this is appended by default and can be disabled with accessibility.windowTitleOptimized:false.
You can now attach images and work with them directly in Copilot Chat in VS Code or Visual Studio. Share screenshots of errors and Copilot will interpret the image and resolve the issue. Or share mockups of new designs, and Vision will help you bring them to life.
You can now attach images using several methods:
Currently, the supported image types are JPEG/JPG, PNG, GIF, and WEBP.
You can use the vision capability with the GPT-4o model. Make sure you have the Copilot ‘Editor Preview Features’ policy enabled to get access.
This feature was previously available to VS Code Insiders and Visual Studio Preview users, and is now available to users of the stable editor versions in public preview.
To learn more, read the documentation about using Vision in Copilot Chat.
Please share your feedback in our community discussions.
Keep control over the security posture of your organization with delegated alert dismissal. With this feature, you can require a review process before alerts are dismissed in code scanning and secret scanning. This helps you manage security risk better, as well as meet audit and compliance requirements.
While this feature adds oversight and control, organizations should carefully balance security needs with development velocity. Things to consider include:
This feature can be configured and managed at scale using security configurations or at the repository level.
Each dismissal request requires a mandatory comment explaining the rationale, with email notifications sent to both approvers and requesters throughout the process. If rejected, the alert remains open.
People with the organization owner or security manager role can review and approve dismissal requests by default. The state of previously dismissed alerts does not change when enabling this feature.
The dismissal and approval process is visible on the alert timeline, included on the audit log, and accessible through both the REST API and webhooks.
You can enable this feature today for code scanning and secret scanning in GitHub Enterprise Cloud. It will also be available in version 3.17 of GitHub Enterprise Server.
At GitHub, we believe that investing in the security of your codebases should be straightforward, cost-effective, and accessible for everyone. Today, we’re announcing changes to pricing plans and availability of GitHub Advanced Security (GHAS), aligning with our ongoing mission to help organizations of all sizes secure their code with the flexibility they seek.
Starting April 1, 2025, GitHub Advanced Security will be available as two standalone security products: GitHub Secret Protection and GitHub Code Security. In addition, these products will become available to GitHub Team plan customers for the first time.
New customers can purchase GitHub Secret Protection, which includes features that help detect and prevent secret leaks (e.g. secret scanning, AI-detected passwords, and push protection for secrets). Secret Protection will be available for $19 per month per active committer, with features including:
In addition, we’re launching a new scanning feature to help organizations understand their secret leak footprint across their GitHub perimeter. This feature will be free for GitHub Team and Enterprise organizations.
New customers will also be able to purchase Code Security, which detects and fixes vulnerabilities in your code before it reaches production. Code Security will be available for $30 per month per active committer with features including:
Starting April 1, 2025, customers on the GitHub Team plan can purchase Secret Protection and Code Security. These products will be available through a consumption-based, pay-as-you-go model (i.e., metered billing) to ensure security remains affordable, scalable, and accessible for all customers on GitHub.
Existing customers with plans managed with a GitHub or Microsoft sales account team can transition to the new GitHub Advanced Security plans at start time of renewal for renewal dates after April 1, 2025. Please contact your account team for further details. For existing self-serve customers, instructions on how to transition to the new GitHub Advanced Security plans will be announced over the coming months through GitHub’s roadmap and changelog.
GitHub Team customers can choose to purchase Secret Protection or Code Security from their organization settings pages starting April 1, 2025.
GitHub is committed to empowering the developer community by helping organizations recognize and address the risks of secret leaks. That’s why we’re launching a new free tool next month which will provide clear insights into their exposure, along with actionable steps to strengthen their security and protect their code.
Scan your organization for aggregate insights on public leaks, private exposures, and token types.
The secret risk assessment will be available on April 1, 2025 as part of the launch of Secret Protection for GitHub Team and Enterprise plans.
Available in the ‘Security’ tab, organization and security admins will be able to run a scan in order to understand how their organization is affected by secret leaks and exposures. Once a scan is initiated, GitHub will look for secret leaks and exposures across your organization, returning a collection of insights including:
No specific secrets will be stored or shared. The scan will be a point-in-time assessment across all public and private repositories. For organizations ready to adopt a continuous monitoring tool, we recommend enabling secret scanning for detection and incident management of specific secrets.
We’re launching this feature to help organizations understand their secret leak footprint across their GitHub perimeter.
GitHub is committed to making a meaningful impact on the developer community by helping organizations recognize their risk from secret leaks. Our goal is to provide clear insights into their exposure and a clear path to stronger security.
This feature will be available for free to organizations with a GitHub Team or Enterprise plan. Organization admins and security managers will be able to run the report and review any results.
To learn more about the launch of GitHub Secret Protection, please refer to this changelog. Have questions? Let us know what you think by starting a discussion in GitHub Community — we’re listening.
The improved merge experience on the pull request page is now generally available! This update is designed to help you better understand the state of your pull request and get it merged faster.
This experience supports all the usual ways of merging: direct, bypass and merge, auto-merge, and merge queue, and works with rulesets to ensure pull requests meet all the requirements to merge.
The new experience is designed to feel familiar, but also improves on the previous experience. Here are some highlights:
Learn more about merging a pull request.
To suggest a feature, report a problem, or discuss this improved experience, visit the GitHub Community.
npm’s massive ecosystem of open source packages is one of its greatest strengths. But as a security-conscious developer, it can be tough to keep up with vulnerability reporting and updates once your project has more than a handful of dependencies, each of which has its own set of dependent packages. Dependabot notifies you of vulnerabilities and their fixes as they come in. Unfortunately, it’s hard to distinguish actionable alerts about direct dependencies you’ve added to your manifests from those transitive dependencies that were pulled in along the way… until now, that is.
GitHub’s dependency graph now tracks direct and transitive dependencies for npm packages. This helps you triage, prioritize, and remediate your Dependabot alerts. This capability shows up in user-facing features across the site:
relationship:direct filter in the search bar.relationships section that uses the SPDX relationshipType: DEPENDS_ON field to express the tree of package dependencies. Tools like guac.sh can help explore and visualize this tree.relationship field with direct, transitive, or unknown values in the DependencyGraphDependency object. See the API documentation for details.We started with npm because it’s the most popular package ecosystem in the known universe, but it’s just the beginning. Over the next few months, package types for other programming languages will also get the transitivity treatment. Up next: Maven packages for Java.
To try this out, you’ll need to make sure the dependency graph is enabled. To see the Dependabot labels, you’ll also need to enable Dependabot alerts. If the “Direct” labels aren’t showing up for you immediately, push a commit that updates one of your manifest files, which will trigger an update of the dependency graph.
Join the discussion within GitHub Community.
Scaling your GitHub usage just got easier! We are expanding our pay-as-you-go usage-based billing and licensing reporting interface to include GitHub Enterprise (GHE) and GitHub Advanced Security (GHAS) Server-only usage.
We announced pay-as-you-go billing for GHE and GHAS on August 1, 2024 to give customers flexible self-provisioning and pricing. Since then, enterprise accounts on github.com created on or after that date could generate a GitHub Enterprise Server key for the appropriate license count when license adjustments were needed. This required all users, including Server-only users, to be represented in the enterprise account’s user list on GitHub Enterprise Cloud.
Now, you can track and monitor your Server-only license usage for both Enterprise and Advanced Security as a separate line item on the Billing & Licensing > Licensing page.
Note that it will still be required to add all Server-only users to your GitHub Enterprise Cloud enterprise user list to account for their license usage and generate a license key with the appropriate license count. This update does not change this compliance requirement.
For existing customers who already have GHE or GHAS, your plan and existing billing method will remain as-is.
If you are interested in pay-as-you-go usage-based billing and have a GitHub account team, please connect with them to discuss whether switching to this model is an option for you.
Check out our documentation to learn more about usage-based billing for licenses.
The GitHub Copilot plugin for JetBrains IDEs now includes the ability to view code references, designed to enhance your coding experience and improve productivity.
Viewing code references: When GitHub Copilot suggests code that matches public code, you will be notified of this match. Click “View matches” at the end of the response to access the reference information.
Informed decisions with code suggestions: code referencing allows you to make more informed decisions about whether to use the suggested code.
We encourage you to try out the latest version of the GitHub Copilot plugin and share your feedback. Your input is invaluable in helping us refine and improve the product.
Connect with us and other developers in the GitHub Community to share your experiences, ask questions, and provide feedback.
This week, we’ve added an indicator for your daily or hourly quotas, allocated a section of the dashboard to issues assigned to you, and introduced several UX improvements and bug fixes to ensure a smooth development process with Copilot Workspace.
As you’re nearing your quota limit, Copilot Workspace will now display a counter so you can keep track of how many tokens you have left, and prioritize your usage accordingly.
Your recently assigned issues are now listed in the homepage dashboard, providing another jumping point to start developing from!
The sessions index page now maintains scroll position when navigating across sessions.
When viewing a new file’s diff, the diff is now highlighted in green.
We’ve added an arrow to the current branch name, indicating that it is clickable.
You can now select file names in the Plan stage, allowing you to copy them as needed.
We fixed the “live preview” button on the run command.
We fixed the overlay of the file tree view on small viewports.
Light/dark mode is now fixed to match your settings theme.
Terminal commands are now correctly disposed of when exiting the command dialogue without saving.
There’s improved file name generation to remove excess backtick characters.
We fixed a bug where the plan was not being shown in mobile view.
The “Revise” button on file headers is now represented by a sparkling pencil icon instead of crosshairs.
There’s a new square circle button for stop buttons.
Please give your feedback in our GitHub Discussion. We’d love to hear your thoughts!
January and February brought a number of improvements to GitHub Mobile, making it more powerful and flexible. We’re rolling out exciting new features designed to make coding and collaboration easier on the go. From third-party integrations that extend GitHub Copilot’s capabilities to in-chat coding assistance, sub-issues, and refined notification preferences, these updates are designed to boost productivity and keep you connected wherever you are.
| Copilot Extensions | Sub-issues |
|---|---|
 |
 |
Learn more about GitHub Mobile and share your feedback to help us improve.
Join the discussion within GitHub Community.
CodeQL version 2.20.5 has been released and includes a host of coverage improvements, including extended support for C# 13 and new detection capabilities for Java and GitHub Actions workflow files.
CodeQL is the static analysis engine that powers GitHub code scanning, which finds and remediates security issues in your code.
CodeQL 2.20.5 adds full support for new language features introduced in C# 13 / .NET 9, as well improved coverage for .NET 9. This will improve the detection of alerts and reduce the chance of false negative results.
CodeQL Java analysis is improved with additional support for Cross Site Request Forgery (CSRF). The new analysis capability detects vulnerabilities that occur when using HTTP request types that are not protected against cross site requests by default.
Go analysis has been updated to support Go 1.24, which includes new language features and improvements. This will improve the detection of alerts and reduce the chance of false negative results.
For a full list of changes, please refer to the complete changelog for version 2.20.5. Every new version of CodeQL is automatically deployed to users of GitHub code scanning on GitHub.com. The new functionality in CodeQL 2.20.5 will also be included in GitHub Enterprise Server (GHES) version 3.17. If you use an older version of GHES, you can manually upgrade your CodeQL version.
We recently launched analysis capabilities for GitHub Actions workflow files in public preview.
With the release of CodeQL 2.20.5, we are expanding the analysis capabilities to detect additional types of security risks associated with Actions workflow files and we have adjusted some of the existing queries.
The analysis coverage is improved with the addition of five new queries that identify additional types of security risks associated with Actions workflow files. The new queries are:
actions/envpath-injection/medium detects situations where user-controlled sources (like the text of a GitHub issue) are used to populate the PATH environment variable. This could allow an attacker to alter the execution of system commands.actions/envvar-injection/medium detects situations where environment variables which are not properly sanitized can lead to the injection of additional unwanted variables, using new lines or {delimiters}.actions/code-injection/medium– detects situation where user-controlled input can end up in contexts like run: or script:, leading to malicious code being executed and secrets being leaked.actions/artifact-poisoning/medium detects situations where artifacts are not correctly extracted, stored and verified, which could result in a poisoned artifact being executed, leading to repository compromise.actions/untrusted-checkout/medium detects situations where workflows triggered by events like pull_request_target or issue_comment can execute arbitrary code from untrusted sources, if followed by an explicit checkout.Because of its lower precision and the large number of alerts it generates, the query actions/unpinned-tag has been moved to the security-extended query suite from the default query suite, and all existing alerts for this query will be automatically closed if the security-extended suite is not being used.
Three queries have been removed from the default and security-extended query suites because they do not produce relevant security alerts. Alerts generated by these queries will be closed automatically.
actions/if-expression-always-true/criticalactions/if-expression-always-true/highactions/unnecessary-use-of-advanced-configThese changes are now available with the release of CodeQL 2.20.5. For a full list of changes, please refer to the complete changelog for version 2.20.5. Every new version of CodeQL is automatically deployed to users of GitHub code scanning on GitHub.com. The new functionality in CodeQL 2.20.5 will also be included in GitHub Enterprise Server (GHES) version 3.17. If you use an older version of GHES, you can manually upgrade your CodeQL version.
OpenAI’s latest model, GPT-4.5, is now available in GitHub Copilot Chat to Copilot Enterprise users. GPT-4.5 is a large language model designed with advanced capabilities in intuition, writing style, and broad knowledge. It performs effectively with creative prompts and provides reliable responses to obscure knowledge queries. GPT-4.5 will launch in Visual Studio Code and on github.com for Copilot Enterprise users with a limit of 10 requests every 12 hours per user. In the coming weeks, we’ll be scaling rate limits and extending support to Visual Studio and JetBrains.
As model releases have continued to accelerate, we’ve been thinking about how we can sustainably offer advanced AI models like GPT-4.5 to more GitHub users. This includes individual developers who want the most advanced capabilities from day one. Stay tuned for updates.
Copilot Enterprise administrators will need to enable access to GPT-4.5 via a new policy in Copilot settings. As an administrator, you can confirm availability by checking your individual Copilot settings and confirming the policy for GPT-4.5 is set to “enabled”. Once enabled, users will see GPT-4.5 in the Copilot Chat model selector in VS Code and on github.com.
Codespaces will be undergoing maintenance in Europe and Southeast Asia from 17:00 UTC on Friday, February 28 to 02:00 UTC on Saturday, March 1. Maintenance will begin in North Europe at 17:00 UTC on Friday, February 28. Once it is complete, maintenance will start in Southeast Asia, followed by UK South. Each region will take approximately two to three hours to complete.
During this time period, users may experience connectivity issues with new and existing Codespaces.
If you have uncommitted changes you may need during the maintenance window, you should verify they are committed and pushed before maintenance starts. Codespaces with any uncommitted changes will be accessible as usual once maintenance is complete.
We are making changes to npm replication APIs to optimize performance and availability. As part of this update, certain endpoints will be deprecated as of Thursday, May 29, 2025.
To facilitate a seamless transition, the new endpoints will be available starting Tuesday, March 18, 2025, operating in parallel with the existing endpoints. The existing endpoints will be fully deprecated on Thursday, May 29, 2025.
During the transition period, you may access the new endpoints by including the npm-replication-opt-in header with the value true in your requests. This option will be available from Tuesday, March 18, 2025 until the deprecation date, after which only the new endpoints will be available. Effective Thursday, May 29, 2025, the header will be ignored, and all requests will be directed to the new endpoints by default.
This notice is provided to ensure adequate time for necessary updates to replication implementations. We strongly encourage developers to migrate to the new endpoints as early as possible.
To assist with migration, we have detailed documentation in our replication API migration community discussion, outlining alternative approaches for deprecated endpoints when available. This is the go-to place for questions and discussions.
If you have further questions or need additional assistance, please reach out to our support team.