As previously announced, Enterprise Managed Users (EMUs) must now prove ownership of their email addresses to secure their accounts and prevent any accidental data leaks by third party GitHub Apps and OAuth applications. In January 2025, we also updated the /user/emails REST endpoint to return a placeholder email address with the enterprise’s shortcode appended (e.g. email+shortcode@domain.com) until the EMU user has verified their email address.

While unverified emails may not affect most of your actions on GitHub, some GitHub Apps and OAuth apps may not handle this placeholder email properly. This may prevent you from accessing those apps or result in incomplete data being displayed. These apps may also prompt you to verify your email on GitHub before proceeding.

For example, GitHub Desktop might incorrectly prompt users to update their email in their Git config to their placeholder email. However, updating your Git config email could lead to commit misattribution as opposed to fixing it. While this experience is updated in GitHub Desktop v3.4.17-beta3, we recommend users verify their email address in response to such prompts.

Learn more about how to verify your email address.
App developers should also review our best practices for OAuth and GitHub App implementation to avoid disrupting the user experience in your apps.

The post Verify email address to secure Enterprise Managed User accounts appeared first on The GitHub Blog.

• Import and export makes it easy to share and reuse rulesets, including our collection of ruleset-recipes to help get you started.
• Ruleset history allows administrators of GitHub Enterprise to easily track and rollback changes in the ruleset UI and API.

To learn more, check out the ruleset documentation. You can also join our community discussions.

The post Repositories: Ruleset history, import and export are generally available appeared first on The GitHub Blog.

GitHub Copilot Chat for Xcode is now in public preview! You can enable GitHub Copilot in Xcode with any GitHub account and experience both code completions and in-editor chat assistance today.

What’s new

• Chat view: Ask Copilot for help with coding tasks directly in the chat view.
• Slash commands: Use quick commands, like /explain for code explanations.
• Reference code: Scope chats to specific files for more relevant assistance.
• Multiple conversations: Maintain different threads, each with their own context.
• Chat history management: Keep track of past conversations for future reference.
• Free access: Get 2,000 code completions and 50 chat messages per month for free, simply by signing in with your GitHub account or by creating a new one.

Try it out

• To access GitHub Copilot Chat for Xcode, you’ll need a Copilot license.

• Follow the steps outlined in the Getting Started guide.

Share your feedback

Your feedback drives improvements. Let us know what you think using the in-product feedback option, or share your thoughts with the GitHub Community.
Join us on this journey as we continue to enhance GitHub Copilot for Xcode and deliver a smoother developer workflow!

The post GitHub Copilot Chat for Xcode now in public preview appeared first on The GitHub Blog.

We’re excited to announce that code completions with GitHub Copilot in Eclipse are now in public preview! You can enable GitHub Copilot in Eclipse with any GitHub account and start experiencing AI-powered code completion today.

What’s new

• Code completions: Copilot is now seamlessly integrated into Eclipse, offering real-time, context-aware code suggestions as you type.
• Multi-language support: GitHub Copilot for Eclipse supports a wide range of programming languages, including Java, Python, C++, and more. This enables developers across different tech stacks to leverage Copilot’s AI-powered assistance.
• Content filtering: Copilot incorporates advanced filtering mechanisms to screen out harmful or inappropriate content, helping ensure professional and responsible code recommendations.
• Free Tier: You will have 2,000 code completions and 50 chat messages per month, simply by signing in with your personal GitHub account or by creating a new one.

Try it out

• To access GitHub Copilot for Eclipse, you’ll need a Copilot license.
• Get started today by installing GitHub Copilot on the Eclipse Marketplace.

Share your feedback

Your feedback drives our improvement! Let us know what you think using the in-product feedback option or share your thoughts with the GitHub Community.
Join us on this journey as we continue to enhance GitHub Copilot for Eclipse and deliver a smoother developer workflow!

The post GitHub Copilot code completions now in public preview for Eclipse appeared first on The GitHub Blog.

Developers can now use Dependabot to keep their bun dependencies up to date automatically. For projects that use bun as a package manager, Dependabot Version Updates can now ensure dependencies stay current with the latest releases.

Support for bun security updates will be added in the future.

• Engage with the Dependabot open source community on the topic of bun support
• Learn more about Dependabot version updates
• Learn more about bun

The post Dependabot version updates now support the bun package manager – [GA] appeared first on The GitHub Blog.

GitHub Copilot in Visual Studio 17.13: New features to supercharge your development workflow

Welcome to another exciting GitHub Copilot update for Visual Studio! This release introduces several powerful new features to enhance your workflow, improve transparency, and make coding with Copilot even more intuitive.

GitHub Copilot Free now available in Visual Studio

GitHub Copilot is now more accessible than ever with our new free plan for Visual Studio. With your GitHub account, you’ll get:

• 2,000 code completions per month – Speed up development with AI-powered suggestions.
• 50 chat messages per month – Get instant coding help, explanations, and debugging support.
• Access to the latest AI models (Claude 3.5 Sonnet & GPT-4o) – Write, refactor, and improve your code with cutting-edge AI.

For developers who are just getting started with AI coding tools or those who only need occasional assistance, the free plan provides an easy way to experience the benefits of GitHub Copilot.

Ready to give it a try? Sign up for GitHub Copilot Free and start coding smarter today!

Copilot Edits: Multi-file editing

Refactor and edit multiple files faster with Copilot Edits:

• Preview with clarity – See which files are affected before making changes.
• Review with flow – Accept (TAB) or reject (Alt+Del) changes inline with code diffs.
• Iterate with confidence – Use checkpoints to revisit past iterations.

Copilot Edits helps you make large-scale changes more efficiently, helping to ensure accuracy and control over your codebase. Whether you’re refactoring, applying consistent patterns, or fixing issues across multiple files, GitHub Copilot Edits speeds up the process while keeping you in control.

To try it today, click the Edits thread button (a “+” symbol with a pencil icon) in the top-right corner of the GitHub Copilot Chat window to start a Copilot Edits session.

GitHub Copilot just got smarter: Automatically retrieve relevant context

GitHub Copilot can now pull in the information you need without requiring manual input, making it easier than ever to get accurate, context-aware suggestions. Copilot can search for information from:

• Your current file, open files, and related files – Get relevant suggestions based on what you’re actively working on.
• Your entire codebase – Surface insights from across your project without switching context.
• Debugger data (locals, call stacks, etc.) – Use real-time debugging information to troubleshoot faster.
• Visual Studio itself – Get answers about IDE settings, commands, and workflows.

Instead of manually copying code, searching through files, or retyping information, Copilot can now pull in the right context automatically—helping you write, debug, and refine code faster.

Need more control? Use #file, #method, or #solution in your prompts to specify exactly where Copilot should look.

Code referencing for completions: More transparency, more control

Ever wondered where Copilot’s completions (gray text) come from? Now, with Code Referencing for Completions, you’ll get more visibility when Copilot suggests code that matches public GitHub repositories.

• Toast notification – If you accept a completion that matches public code, you’ll see a toast notification in the bottom-right of your editor.
• Copilot Output Window – View license details and links to the original repository in the Copilot Output Window (Ctrl+Alt+O).
• Adjustable settings – Individual subscribers can block or allow suggestions that match public code in their GitHub settings.

By default, matches to public code are rare (less than 1% of completions), but this tool helps you code with more confidence and transparency.

Bug fixes & improvements

• Added support for zooming in and out within Copilot windows for improved accessibility and readability.
• Users can now easily retry their prompts for better responses.
• Users can now pick which model GitHub Copilot is using for inline chat with the model picker, allowing for quick and easy model selection.

How to update

Make sure you’re using Visual Studio 2022 17.13 or later to access these features.

Download the latest version of Visual Studio 2022

We’d love to hear your feedback! Share your thoughts through the Developer Community or the Send Feedback button in Visual Studio.

Happy coding!

The post GitHub Copilot in Visual Studio 2022 Version 17.13 appeared first on The GitHub Blog.

The improved merge experience on the pull request page announced in December will be enabled by default over the next few days! The feature remains in public preview while we address feedback (keep it coming!) and make final improvements before making it generally available later this quarter.

This improved experience, while still familiar, is designed to help you better understand the state of your pull request and get it merged faster. To learn more, see the public preview announcement.

Recent fixes

There have been numerous bugs fixed and feature gaps filled since the public preview launched last year. Here are some notable fixes:

• Fixed: Enabling auto-merge, deleting branch (after merging), or restoring branch previously failed with an unexpected error message.
• Fixed: In certain scenarios, the commit author email address shown when merging the pull request would not match the email address in the resulting merge (or squash) commit.
• Fixed: GitHub Actions workflow runs could only be approved from the classic merge experience.
• Fixed: Status check durations were missing.

We’ve also made various improvements, including natural ordering for status checks. For a more complete list, see the recently fixed section of this discussion.

How to turn it off

To switch back to the classic experience, click the Switch back to the classic merge experience just below the merge experience on the Conversation page:

If you want to return to the improved experience, click Try the new merge experience below the merge box on the pull request page:

You can also toggle the experience via the feature preview dialog.

How to provide feedback

We want to hear from you! To provide feedback, ask questions, and see a list of known issues, visit the GitHub Community improved merge box discussion.

The post Improved pull request merge experience enabled by default in public preview appeared first on The GitHub Blog.

You can now iterate on your prompt in any user repositories without breaking your flow. With just one click, jump from a prompt in your GitHub-hosted code to the GitHub Models prompt editor:

This feature detects files with “prompt” in the content and uses 10 lines above and below the selected line as context. Once in the prompt editor, you can experiment with models, fine-tune your prompts, and customize parameters.

GitHub Models is a catalog and prompt editor of AI models to help you build AI features and products. You can start using models for free with just your GitHub PAT. This is the first of more features to come that will help with seamless integration between your existing workflow and the GitHub Models prompt editor!

Learn more about GitHub Models or join the discussion in our community forums.

The post GitHub Models prompt editor now integrates with user repository code [GA] appeared first on The GitHub Blog.

Changes to check run status modification

To ensure the trustworthiness and security of Actions Check Run results, developers will soon lose the ability to modify the conclusion and status of an Actions-created check run using the GitHub token from a workflow run. This change will take effect on March 31, 2025. Impacted workflows will start displaying annotations during the week of February 17, 2025.

Updates to the network allow list for self-hosted runners and Azure private networking

In preparation for the public preview of consuming Immutable Actions in February 2025, GitHub has started migrating standard hosted runner customers to immutable actions. There is no action required on your end. This means GitHub Actions will use as an immutable action where available and will default to traditional actions resolution where none exist.

For customers using self-hosted runners, please ensure your self-hosted runner allow lists are updated to accommodate the network traffic. Specifically, you should allow traffic to pkg.actions.githubusercontent.com to ensure immutable actions can be downloaded successfully and jobs don’t fail during setup. If you already allow *.actions.githubusercontent.com (which is listed as a required domain) then no action is necessary. You will also need to enable traffic to ghcr.io for publishing new versions of an immutable action in the future, which will be available with the GA release.

Customers who have not updated their allow lists will automatically be opted out from using immutable actions during the migration. Once GitHub confirms that the runners have been updated, you will automatically be opted back in once the allow lists are updated. If you need to manually opt out or in for using immutable actions, please contact support.

This update also affects runners in all versions of GitHub Enterprise Server that use the GitHub Connect feature to download actions directly from github.com. Customers are advised to update their self-hosted runner network allow lists accordingly. For further guidance on communication between self-hosted runners and GitHub, please refer to our documentation.

Additionally, we’ve updated our guidance for configuring Azure private networking to account for the new domains. The following IP addresses have been added to the NSG template in our documentation.

– 140.82.121.33/32
– 140.82.121.34/32
– 140.82.113.33/32
– 140.82.113.34/32
– 140.82.112.33/32
– 140.82.112.34/32
– 140.82.114.33/32
– 140.82.114.34/32
– 192.30.255.164/31
– 4.237.22.32/32
– 20.217.135.1/32
– 4.225.11.196/32
– 20.26.156.211/32

Ubuntu 20 image brownouts

To raise awareness of the upcoming removal of Ubuntu 20, we will temporarily fail jobs using the ubuntu-20.04 label starting in March 2025. The brownouts will occur on the following dates and times:

• March 4 14:00 UTC – 22:00 UTC
• March 11 13:00 UTC – 21:00 UTC
• March 18 13:00 UTC – 21:00 UTC
• March 25 13:00 UTC – 21:00 UTC

actions/cache v1-v2 and actions/toolkit cache package brownouts

To raise awareness of the upcoming removal, we have scheduled brownouts for the following dates/times, Actions jobs referencing a deprecated verion of the Cache action will fail.

• February 18, 2pm – 10pm UTC

The post Notice of upcoming deprecations and breaking changes for GitHub Actions appeared first on The GitHub Blog.

CodeQL is the static analysis engine behind GitHub code scanning, which finds and remediates security issues in your code. The CodeQL engine has become faster, covers 28 more security queries, supports more ecosystems, and can now scan GitHub Actions (public preview)—among various other bug fixes and small improvements.

All of these improvements were automatically rolled out to code scanning users in the past few months. For users of the CodeQL CLI, here are some highlights of the past few CodeQL releases:

• CodeQL 2.20.4 – 6 February 2025
  • Analysis support for GitHub Actions workflow files is now in public preview, and therefore the use of the actions language (for analysis of GitHub Actions workflows) no longer requires the CODEQL_ENABLE_EXPERIMENTAL_FEATURES environment variable to be set.
  • All experimental queries for C#, Java, and Kotlin have been migrated to the default query suite in the CodeQL community packs that are managed by GitHub Security Lab.
• CodeQL 2.20.3 – 24 January 2025
  • Resolves a security vulnerability where CodeQL databases or logs produced by the CodeQL CLI may contain the environment variables from the time of database creation. This includes any secrets stored in an environment variables. For more information, see the CodeQL CLI security advisory.
• CodeQL 2.20.2 – 22 January 2025
  • All data flow queries have been standardized on a single data flow library, which may result in differences for JavaScript and TypeScript analysis.
  • CodeQL databases now take 2-3x less space on disk, which makes them faster to transfer and read/manipulate. This is thanks to a new compressed database format.
• CodeQL 2.20.1 – 9 January 2025
  • CodeQL is now easier to set up and roll out: automatic build command detection with automatic dependency installation for C/C++ is now supported on Ubuntu 24.04.
  • A new Server Side Template Injection query for Python has been released, thanks to a community contribution.
  • Swift 6.0.2 is now supported.
• CodeQL 2.19.4 – 2 December 2024
  • Analysis coverage improvement: the bottle web framework for Python is now supported.
• CodeQL 2.19.3 – 7 November 2024
  • Analysis for .NET 8 and JDK 17 has been improved.
  • The CodeQL Bundle is now available as an artifact that is compressed using Zstandard. This artifact is smaller and faster to decompress than the original, gzip-compressed bundle. The CodeQL bundle is a tar archive containing tools, scripts, and various CodeQL-specific files.
• CodeQL 2.19.2 – 21 October 2024
  • Analysis of Python apps now has significantly faster extraction and analysis times.
• CodeQL 2.19.1 – 4 October 2024
  • Java 23 is now supported.
  • A new command, codeql resolve packs, shows each step in the pack search process, including what packs were found in each step.

Detailed changelogs for every CodeQL release are available in the CodeQL documentation, and new CodeQL releases occur roughly every two weeks.

For GitHub Enterprise Server customers: All new functionality from CodeQL releases 2.19.0 through 2.20.3 will be included in GHES 3.16 and the latest patch versions of 3.12-3.15. Functionality from 2.20.3 and later 2.20.X versions will be included in 3.17. If you use an older version of GHES, you can manually upgrade your CodeQL version.

The post CodeQL performance and coverage improvements in recent releases appeared first on The GitHub Blog.

FEATURES:

• New Data Source: azurerm_stack_hci_storage_path (#28602)
• New Resource: azurerm_ai_foundry (#27424)
• New Resource: azurerm_ai_foundry_project (#27424)
• New Resource: azurerm_mssql_job_step (#28691)
• New Resource: azurerm_netapp_volume_group_oracle (#28391)
• New Resource: azurerm_virtual_machine_scale_set_standby_pool (#28441)

ENHANCEMENTS:

• dependencies: hashicorp/go-azure-sdk update to v0.20250213.1092825 (#28767)
• dependencies: sentinel partial update to 2023-12-01-preview (#28195)
• Data Source: azurerm_app_configuration - add support for the data_plane_proxy_authentication_mode and data_plane_proxy_private_link_delegation_enabled properties (#28712)
• azurerm_app_configuration - add support for the data_plane_proxy_authentication_mode and data_plane_proxy_private_link_delegation_enabled properties (#28712)
• azurerm_container_app - add support for the client_certificate_mode property (#28523)
• azurerm_cdn_frontdoor_firewall_policy - add support for JSChallenge for custom rules (#28717)
• azurerm_express_route_circuit - add support for the rate_limiting_enabled property (#28659)
• azurerm_mssql_managed_instance_failover_group - add support for secondary_type (#28633)
• azurerm_sentinal_alert_rule_scheduled - increase combined limit of entity_mapping and sentinal_entity_mapping to 10 (#28195)
• azurerm_service_plan - support for premium_plan_auto_scale_enabled (#28524)

BUG FIXES:

• azurerm_cdn_frontdoor_firewall_policy - fixed issue where the js_challenge_cookie_expiration_in_minutes policies default value caused Standard_AzureFrontDoor skus to receive a BadRequest error (#28726)
• azurerm_servicebus_topic - prevent perma diff when provisioning a partitioned topic within a non-partitioned namespace (#26680)
• azurerm_linux_function_app - will no longer plan when site_config.0.cors is the default value (#28703)
• azurerm_linux_function_app_slot - fix issue where site_config.0.elastic_instance_minimum was not being set (#28725)
• azurerm_linux_web_app - will no longer plan when site_config.0.cors is the default value (#28703)
• azurerm_postgresql_flexible_server_virtual_endpoint - allow source_server_id and replica_server_id to reference the same server (#28733)
• azurerm_windows_function_app - will no longer plan when site_config.0.cors is the default value (#28703)
• azurerm_windows_function_app_slot - fix issue where site_config.0.elastic_instance_minimum was not being set (#28725)
• azurerm_windows_web_app - will no longer plan when site_config.0.cors is the default value (#28703)

ENHANCEMENTS:

• dependencies: appconfiguration - update to API version 2024-05-01 (#28700)
• dependencies: update azurerm_cdn_frontdoor_rule to API version 2024-02-01 (#28308)
• dependencies: update azurerm_cdn_frontdoor_ruleset to API version 2024-02-01 (#28308)
• dependencies: update go-azure-sdk to v0.20250131.1134653 (#28674)
• Data Source: azurerm_cdn_frontdoor_firewall_policy - add support for js_challenge_cookie_expiration_in_minutes policy (#28284)
• Data Source: azurerm_nginx_configuration - add support for the protected_file.content_hash property (#28532)
• azurerm_cdn_frontdoor_firewall_policy - add support for js_challenge_cookie_expiration_in_minutes policy (#28284)
• azurerm_cdn_frontdoor_firewall_policy - add support for JSChallenge action type in the managed_rule override block (#28308)
• azurerm_container_app - add support for the volume_mounts.sub_path property (#27533)
• azurerm_nginx_configuration - add support for the protected_file.content_hash property (#28532)
• azurerm_palo_alto_next_generation_firewall_virtual_hub_local_rulestack - add support for the marketplace_offer_id and plan_id properties (#28537)
• azurerm_palo_alto_next_generation_firewall_virtual_hub_panorama - add support for the marketplace_offer_id and plan_id properties (#28537)
• azurerm_palo_alto_next_generation_firewall_virtual_network_local_rulestack - add support for the marketplace_offer_id and plan_id properties (#28537)
• azurerm_palo_alto_next_generation_firewall_virtual_network_panorama - add support for the marketplace_offer_id and plan_id properties (#28537)
• azurerm_route_server - add support for the hub_routing_preference property (#28363)

BUG FIXES:

• azurerm_logic_app_action_http - fix issue where queries would be set to an empty map instead of null when omitted from the configuration (#28447)
• azurerm_machine_learning_compute_cluster - allow resource creation when node_public_ip_enabled is false and subnet_resource_id has not been specified (#28673)
• azurerm_network_watcher_flow_log - prevent panic when removing the traffic_analytics block (#28416)
• azurerm_oracle_autonomous_database - fix incorrect type for the supported_regions_to_clone_to property (#28536)

FEATURES:

• New Resource: aws_cloudwatch_contributor_insight_rule (#41373)

ENHANCEMENTS:

• resource/aws_dynamodb_table_export: Add export_type and incremental_export_specification arguments (#41303)
• resource/aws_quicksight_data_source: Add parameters.s3.role_arn argument to allow override an account-wide role for a specific S3 data source (#41284)
• resource/aws_rds_cluster: Add master_password_wo write-only attribute (#41314)
• resource/aws_rekognition_stream_processor: Deprecates stream_processor_arn in favor of arn. (#41271)
• resource/aws_ssm_parameter: Add value_wo write-only attribute (#40952)
• resource/aws_vpclattice_access_log_subscription: Add service_network_log_type argument (#41304)

BUG FIXES:

• data-source/aws_dynamodb_table: Add missing on_demand_throughput and global_secondary_index.*.on_demand_throughput attributes to resolve read error (#41350)
• resource/aws_cloudformation_stack_set_instance: Prevents overly-long creation times and possible OperationInProgress errors (#41388)
• resource/aws_detective_member: No longer fails with unexpected status when adding Organization member accounts. (#41344)
• resource/aws_ec2_transit_gateway_route_table_association: Fix deleting and recreating resource when dependencies changes don't require the resource be recreated. (#41292)
• resource/aws_internet_gateway: Fix to continue deletion when attachment is not found (#41346)

BUG FIXES:

• data-source/aws_vpclattice_service: Fix regression resulting in AccessDeniedError attempting to list tags (#41295)
• data-source/aws_vpclattice_service_network: Fix regression resulting in AccessDeniedError attempting to list tags (#41295)
• resource/aws_cloudtrail: Fix regression issue where sns_topic_name shows perpectual diff when an ARN of a SNS topic from a different region is specified (#41279)
• resource/aws_s3_bucket_lifecycle_configuration: Fixes "inconsistent result" error when rule[*].prefix is an empty string. (#41296)

1.12.0-alpha20250213 (February 13, 2025)

EXPERIMENTS:

Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.

• The new command terraform rpcapi exposes some Terraform Core functionality through an RPC interface compatible with go-plugin. The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the Terraform Stacks private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview.
• The experimental "deferred actions" feature, enabled by passing the -allow-deferral option to terraform plan, permits count and for_each arguments in module, resource, and data blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment

Previous Releases

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

• 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

1.11.0-rc1 (February 12, 2025)

NEW FEATURES:

• Add write-only attributes to resources. Providers can specify that certain attributes are write-only. They are not persisted in state. You can use ephemeral values in write-only attributes. (#36031)

• terraform test: The -junit-xml option for the terraform test command is now generally available. This option allows the command to create a test report in JUnit XML format. Feedback during the experimental phase helped map terraform test concepts to the JUnit XML format, and new additons may happen in future releases. (#36324)

• S3 native state locking is now generally available. The use_lockfile argument enables users to adopt the S3-native mechanism for state locking. As part of this change, we've deprecated the DynamoDB-related arguments in favor of this new locking mechanism. While you can still use DynamoDB alongside S3-native state locking for migration purposes, we encourage migrating to the new state locking mechanism. (#36338)

ENHANCEMENTS:

• init: Provider installation will utilise credentials configured in a .netrc file for the download and shasum URLs returned by provider registries. (#35843)

• New command modules -json: Displays a full list of all installed modules in a working directory, including whether each module is currently referenced by the working directory's configuration. (#35884)

• terraform test: Test runs now support using mocked or overridden values during unit test runs (e.g., with command = "plan"). Set override_during = plan in the test configuration to use the overridden values during the plan phase. The default value is override_during = apply. (#36227)

• terraform test: Add new state_key attribute for run blocks, allowing test authors control over which internal state file should be used for the current test run. (#36185)

• Include ca-certificates package in our official Docker image to help with certificate handling by downstream (#36471)

BUG FIXES:

• ephemeral values: correct error message when ephemeral values are included in provisioner output (#36427)

• Attempting to override a variable during apply via TF_VAR_ environment variable will now yield warning instead of misleading error. (#36435)

• backends: Fix crash when interrupting during interactive prompt for values (#36448)

Previous Releases

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

• 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

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• update vault auth submodules to api/v1.16.0

• update go.mod

• make proto

Co-authored-by: davidadeleon ddeleon@hashicorp.com

• added check for updating static roles, appending full payload data

• pulling specific properties into payload obj to fix popups

• adding changelog

• add else to keep previous imp for dynamic roles

• removing separate request, utilizing snapshot

• renamed serialized data var, added comment for required username line

• adding test for editing static role

• updated test for edit payload

• Update changelog/29498.txt

Co-authored-by: claire bontempo 68122737+hellobontempo@users.noreply.github.com

Co-authored-by: claire bontempo 68122737+hellobontempo@users.noreply.github.com

NOTES:

• 5.45.2 contains no changes from 5.45.1. This release is being made to ensure that the version numbers of the google and google-beta provider releases remain aligned, as google-beta's 5.45.2 release contains a beta-only change.

NOTES:

• provider: The Terraform Provider for Google Cloud's regular release date will move from Monday to Tuesday in early March. The 2025/03/10 release will be made on 2025/03/11.
• compute: google_compute_firewall_policy now uses MMv1 engine instead of DCL. (#21235)

FEATURES:

• New Data Source: google_beyondcorp_application_iam_policy (#21199)
• New Data Source: google_parameter_manager_parameter_version_render (#21104)
• New Resource: google_beyondcorp_application (#21199)
• New Resource: google_beyondcorp_application_iam_binding (#21199)
• New Resource: google_beyondcorp_application_iam_member (#21199)
• New Resource: google_beyondcorp_application_iam_policy (#21199)
• New Resource: google_bigquery_analytics_hub_listing_subscription (#21189)
• New Resource: google_colab_notebook_execution (#21100)
• New Resource: google_colab_schedule (#21233)

IMPROVEMENTS:

• accesscontextmanager: added resource to sources in egress_from under resources google_access_context_manager_service_perimeter, google_access_context_manager_service_perimeters, google_access_context_manager_service_perimeter_egress_policy, google_access_context_manager_service_perimeter_dry_run_egress_policy (#21190)
• cloudrunv2: added base_image_uri and build_info to google_cloud_run_v2_service (#21236)
• colab: added auto_upgrade field to google_colab_runtime (#21214)
• colab: added software_config.post_startup_script_config field to google_colab_runtime_template (#21200)
• colab: added desired_state field to google_colab_runtime, making it startable/stoppable. (#21207)
• compute: added ip_collection field to google_compute_forwarding_rule resource (#21188)
• compute: added mode and allocatable_prefix_length fields to google_compute_public_delegated_prefix resource (#21216)
• compute: allow parallelization of google_compute_per_instance_config and google_compute_region_per_instance_config deletions by not locking on the parent resource, but including instance name. (#21095)
• container: added auto_monitoring_config field and subfields to the google_container_cluster resource (#21229)
• filestore: added initial_replication field for peer instance configuration and effective_replication output for replication configuration output to google_filestore_instance (#21194)
• memorystore: added CLUSTER_DISABLED to mode field in google_memorystore_instance (#21092)
• networkservices: added compression_mode and allowed_methods fields to google_network_services_edge_cache_service resource (#21195)
• privateca: added user_defined_access_urls and subfields to google_privateca_certificate_authority resource to add support for custom CDP AIA URLs (#21220)
• workbench: added enable_third_party_identity field to google_workbench_instance resource (#21265)

BUG FIXES:

• appengine: added a mitigation for an upcoming default change to standard_scheduler_settings.max_instances for new google_app_engine_standard_app_version resources. If the field is not specified in configuration, diffs will now be ignored. (#21257)
• bigquery: added diff suppression for legacy values in renewal_plan field in google_bigquery_capacity_commitment resource (#21103)
• compute: fixed google_compute_(region_)resize_request requiring region/zone to be specified in all cases. They can now be pulled from the provider. (#21264)
• container: reverted locking behavior in google_container_node_pool that caused regression of operation apply time spike started in v6.15 (#21102)
• gemini: fixed a bug where the force_destroy field in resource gemini_code_repository_index did not work properly (#21212)
• workbench: fixed a bug with google_workbench_instance metadata removal not working as expected (#21204)