-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all non-major dependencies #1213
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5e1a540
to
a961587
Compare
a961587
to
e18f41a
Compare
e18f41a
to
91f4434
Compare
91f4434
to
0dafd34
Compare
0dafd34
to
06e0c9f
Compare
06e0c9f
to
76ea70c
Compare
76ea70c
to
d685f9b
Compare
|
d685f9b
to
4da1077
Compare
4da1077
to
beca3ca
Compare
beca3ca
to
4d21cdc
Compare
4d21cdc
to
05dc6fe
Compare
05dc6fe
to
d750970
Compare
dea3faa
to
e99ddad
Compare
e99ddad
to
cb98eee
Compare
cb98eee
to
376525d
Compare
6d52520
to
b93223c
Compare
b93223c
to
87687d8
Compare
87687d8
to
bcdbfb3
Compare
bcdbfb3
to
c31f83d
Compare
|
c31f83d
to
6c1ec6d
Compare
6c1ec6d
to
e1e0424
Compare
e1e0424
to
8465056
Compare
8465056
to
89adcac
Compare
89adcac
to
4b5cc49
Compare
4b5cc49
to
864fa92
Compare
864fa92
to
dc1e53e
Compare
dc1e53e
to
c109ea2
Compare
1a779f9
to
4c56878
Compare
4c56878
to
f78885a
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==3.21.0
->==3.25.0
>= 1.0
->>= 1.11.1
==4.0.0
->==4.0.1
==8.1.3
->==8.2.3
Release Notes
aneoconsulting/ArmoniK.Api (armonik)
v3.25.0
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v3.24.0
Compare Source
🚀 Features
View changes on GitHub
v3.23.0
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v3.22.0
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
hashicorp/terraform (hashicorp/terraform)
v1.11.1
Compare Source
1.11.1 (March 5, 2025)
BUG FIXES:
Temporarily revert updated Windows symlink handling until we can account for known existing configurations using non-symlink junctions. (#36575)
terraform test
: Fix crash when a run block attempts to cleanup after a non-applyable plan. (#36582)Updated dependency golang.org/x/oauth2 from v0.23.0 => v0.27.0 to integrate latest changes (fix for CVE-2025-22868) (#36584)
lang/funcs/transpose: Avoid crash due to map with null values (#36611)
Combining ephemeral and sensitive marks could fail when serializing planned changes (#36619)
v1.11.0
Compare Source
1.11.0 (February 27, 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)terraform test
: Test runs now support using mocked or overridden values during unit test runs (e.g., with command = "plan"). Setoverride_during = plan
in the test configuration to use the overridden values during the plan phase. The default value isoverride_during = apply
. (#36227)terraform test
: Add newstate_key
attribute forrun
blocks, allowing test authors control over which internal state file should be used for the current test run. (#36185)Updates the azure backend authentication to match the terraform-provider-azurermprovider authentication, in several ways:
(#36258)
Include
ca-certificates
package in our official Docker image to help with certificate handling by downstream (#36486)BUG FIXES:
ephemeral values: correct error message when ephemeral values are included in provisioner output (#36427)
Attempting to override a variable during
apply
viaTF_VAR_
environment variable will now yield warning instead of misleading error. (#36435)backends: Fix crash when interrupting during interactive prompt for values (#36448)
Fixes hanging behavior seen when applying a saved plan with -auto-approve using the cloud backend (#36453)
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
v1.10.5
Compare Source
1.10.5 (January 22, 2025)
BUG FIXES:
element(...): no longer crashes when asked for a negative index into a tuple. (#36376)
Updated dependency
github.com/hashicorp/go-slug
v0.16.0
=>v0.16.3
to integrate latest changes (fix for CVE-2025-0377) (#36273)jsondecode(...): improved error message when objects contain duplicate keys (#36376)
v1.10.4
Compare Source
1.10.4 (January 8, 2025)
BUG FIXES:
type conversion: Empty map conversions now return correct type information (#36262)
terraform console
: Fix crash when printing ephemeral values (#36267)v1.10.3
Compare Source
1.10.3 (December 18, 2024)
BUG FIXES:
v1.10.2
Compare Source
1.10.2 (December 11, 2024)
BUG FIXES:
v1.10.1
Compare Source
1.10.1 (December 4, 2024)
BUG FIXES:
templatefile
would panic if given and entirely unknown map of variables (#36118)templatefile
would panic if the variables map contains marked values (#36127)for_each
(#36119)v1.10.0
Compare Source
1.10.0 (November 27, 2024)
NEW FEATURES:
ephemeralasnull
function: a function takes a value of any type and returns a similar value of the same type with any ephemeral values replaced with non-ephemeral null values and all non-ephemeral values preserved.BUG FIXES:
secret_suffix
in thekubernetes
backend now includes validation to prevent errors when thesecret_suffix
ends with a number (#35666).error_message
values to pass the core validate step, so variable validation can be completed later during plan(#35537)
self
with many instances could encounter an error during evaluation (#35895)plantimestamp()
function would return an invalid date during validation (#35902)plan -generate-config-out
) for string attributes that contain primitive types (e.g. numbers or booleans) (#35984)issensitive
could incorrectly assert that an unknown value was not sensitive during plan, but later became sensitive during apply, causing failures where changes did not match the planned result (#36012)ENHANCEMENTS:
element
function now accepts negative indices (#35501)terraform validate
(#35543)plan
,apply
, andrefresh
commands now produce a deprecated warning when using the-state
flag. Instead use thepath
attribute within thelocal
backend to modify the state file. (#35660)UPGRADE NOTES:
assume_role
block (#35721)moved
: Moved blocks now respect reserved keywords when parsing resource addresses. Configurations that reference resources with type names that match top level blocks and keywords frommoved
blocks will need to prepend theresource.
identifier to these references. (#35850)Previous Releases
For information on prior major and minor releases, refer to their changelogs:
v1.9.8
Compare Source
1.9.8 (October 16, 2024)
BUG FIXES:
provider_meta
blocks with invalid names (#35842)v1.9.7
Compare Source
1.9.7 (October 2, 2024)
BUG FIXES:
v1.9.6
Compare Source
1.9.6 (September 18, 2024)
BUG FIXES:
v1.9.5
Compare Source
1.9.5 (August 20, 2024)
ENHANCEMENTS:
BUG FIXES:
removed
blocks with provisioners were not executed when the resource was in a nested module. (#35611)v1.9.4
Compare Source
1.9.4 (August 7, 2024)
BUG FIXES:
v1.9.3
Compare Source
1.9.3 (July 24, 2024)
ENHANCEMENTS:
condition
returnedfalse
) but the error message is derived from an unknown value. (#35400)BUG FIXES:
removed
block. (#35458)v1.9.2
Compare Source
1.9.2 (July 10, 2024)
BUG FIXES:
count
andfor_each
meta attributes. (#35432)v1.9.1
Compare Source
1.9.1 (July 3, 2024)
UPGRADE NOTES:
terraform init
orterraform get
in case of larger git repositories. Please do file an issue if you find the performance difference noticable. (#35376)BUG FIXES:
terraform test
: Removed additional erroneous error message when referencing attributes that don't exist. (#35408)import
blocks: Fix crash that occurs when incorrectly referencing theto
resource from theid
attribute. (#35420)v1.9.0
Compare Source
1.9.0 (June 26, 2024)
If you are upgrading from an earlier minor release, please refer to the Terraform v1.9 Upgrade Guide.
NEW FEATURES:
templatestring
function: a new built-in function which is similar totemplatefile
but designed to render templates obtained dynamically, such as from a data resource result.ENHANCEMENTS:
terraform plan
: Improved presentation of OPA and Sentinel policy evaluations in HCP Terraform remote runs, for logical separation.terraform init
now accepts a-json
option. If specified, enables the machine readable JSON output. (#34886)terraform test
: Test runs can now pass sensitive values to input variables while preserving their dynamic sensitivity. Previously sensitivity would be preserved only for variables statically declared as being sensitive, usingsensitive = true
. (#35021)templatestring
function allows rendering a template provided as a string. (#34968, #35224, #35285)resource
blocks. (#35088)terraform
provider: Allowsmoved
block refactoring from thehashicorp/null
providernull_resource
resource type to theterraform_data
resource type. (#35163)terraform output
withcloud
block: Terraform no longer suggests that data loss could occur when outputs are not available. (#35143)terraform console
: Now has basic support for multi-line input in interactive mode. (#34822)If an entered line contains opening parentheses/etc that are not closed, Terraform will await another line of input to complete the expression. This initial implementation is primarily intended to support pasting in multi-line expressions from elsewhere, rather than for manual multi-line editing, so the interactive editing support is currently limited.
removed
blocks can now declare destroy-time provisioners which will be executed when the associated resource instances are destroyed. (#35230)BUG FIXES:
remote-exec
provisioner: Each remote connection will now be closed immediately after use. (#34137)terraform test
: Fix bug in which non-Hashicorp providers required by testing modules and initialised within the test files were assigned incorrect registry addresses. (#35161)templatefile
function no longer returns a "panic" error if the template file path is marked as sensitive. Instead, the template rendering result is also marked as sensitive. (#35180)import
blocks which referenced resources in non-existent modules were silently ignored when they should have raised an error (#35330)terraform init
: When selecting a version for a provider that has both positive and negative version constraints for the same prerelease -- e.g.1.2.0-beta.1, !1.2.0-beta.1
-- the negative constraint will now overrule the positive, for consistency with how negative constraints are handled otherwise. Previously Terraform would incorrectly treat the positive as overriding the negative if the specified version was a prerelease. (#35181)import
:import
blocks could block a destroy operation if the target resource was already deleted (#35272)cli
: plan output was missing blocks which were entirely unknown (#35271)cli
: fix crash when runningproviders mirror
with an incomplete lock file (#35322)create_before_destroy
when replacing an instance, then applying with-refresh=false
would order the apply operations incorrectly (#35261)resource.
prefix will now be correctly parsed when used as an address target. (#35333)UPGRADE NOTES:
terraform test
: It is no longer valid to specify version constraints within provider blocks within .tftest.hcl files. Instead, version constraints must be supplied within the main configuration where the provider is in use.import
: Invalidimport
blocks pointing to nonexistent modules were mistakenly ignored in prior versions. These will need to be fixed or removed in v1.9.Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.8.5
Compare Source
1.8.5 (June 5, 2024)
BUG FIXES:
terraform test
: Remove duplicate warning diagnostic when providing values for unknown variables in run blocks. (#35172)v1.8.4
Compare Source
1.8.4 (May 22, 2024)
BUG FIXES:
core
: Fix exponential slowdown in some cases when modules are usingdepends_on
. (#35157)import
blocks: Fix bug where resources with nested, computed, and optionalid
attributes would fail to generate configuration. (#35220)golang.org/x/net
release, which addressed CVE-2023-45288 (#35165)v1.8.3
Compare Source
1.8.3 (May 8, 2024)
BUG FIXES:
terraform test
: Providers configured within an overridden module could panic. (#35110)core
: Fix crash when a provider incorrectly plans a nested object when the configuration isnull
(#35090)v1.8.2
Compare Source
1.8.2 (April 24, 2024)
BUG FIXES:
terraform apply
: Prevent panic when a provider erroneously provides unknown values. (#35048)terraform plan
: Replace panic with error message when self-referencing resources and data sources from thecount
andfor_each
meta attributes. (#35047)terraform test
: RestoreTF_ENV_*
variables being made available to testing modules. (#35014)terraform test
: Prevent crash when referencing local variables within overridden modules. (#35030)ENHANCEMENTS:
OTHER CHANGES:
cloud
block and environment variables likeTF_CLOUD_ORGANIZATION
remain unchanged. (#35050)NOTE:
Starting with this release, we are including a copy of our license file in all packaged versions of our releases, such as the release .zip files. If you are consuming these files directly and would prefer to extract the one terraform file instead of extracting everything, you need to add an extra argument specifying the file to extract, like this:
v1.8.1
Compare Source
1.8.1 (April 17, 2024)
BUG FIXES:
moved
block: Fix crash when move targets a module which no longer exists. (#34986)import
block: Fix crash when generating configuration for resources with complex sensitive attributes. (#34996)v1.8.0
Compare Source
1.8.0 (April 10, 2024)
If you are upgrading from Terraform v1.7 or earlier, please refer to
the Terraform v1.8 Upgrade Guide.
NEW FEATURES:
Providers can now offer functions which can be used from within the Terraform configuration language.
The syntax for calling a provider-contributed function is
provider::provider_name::function_name()
. (#34394)Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type.
This extends the
moved
block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported.New
issensitive
function returns true if the given value is marked as sensitive.ENHANCEMENTS:
terraform test
: File-level variables can now refer to global variables. (#34699)When generating configuration based on
import
blocks, Terraform will detect strings that contain valid JSON syntax and generate them as calls to thejsonencode
function, rather than generating a single string. This is primarily motivated by readability, but might also be useful if you need to replace part of the literal value with an expression as you generalize your module beyond the one example used for importing.terraform plan
now uses a different presentation for describing changes to lists where the old and new lists have the same length. It now compares the elements with correlated indices and shows a separate diff for each one, rather than trying to show a diff for the list as a whole. The behavior is unchanged for lists of different lengths.terraform providers lock
accepts a new boolean option-enable-plugin-cache
. If specified, and if a global plugin cache is configured, Terraform will use the cache in the provider lock process. (#34632)built-in "terraform" provider: new
decode_tfvars
,encode_tfvars
, andencode_expr
functions, for unusual situations where it's helpful to manually generate or read from Terraform's "tfvars" format. (#34718)terraform show
's JSON rendering of a plan now includes two explicit flags"applyable"
and"complete"
, which both summarize characteristics of a plan that were previously only inferrable by consumers replicating some of Terraform Core's own logic. (#34642)"applyable"
means that it makes sense for a wrapping automation to offer to apply this plan."complete"
means that applying this plan is expected to achieve convergence between desired and actual state. If this flag is present and set tofalse
then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence.BUG FIXES:
iterator
argument within a dynamic block. (#34751)Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.7.5
Compare Source
1.7.5 (March 13, 2024)
BUG FIXES:
v1.7.4
Compare Source
1.7.4 (February 21, 2024)
BUG FIXES:
terraform test
: Fix automatic loading of variable files within the test directory onwindows
platforms. (#34666)v1.7.3
Compare Source
1.7.3 (February 7, 2024)
BUG FIXES:
terraform test
: Fix crash when dynamic-typed attributes are not assigned values in mocks. (#34610)import
: Throw helpful error message if an import block is configured with an empty ID (34625)v1.7.2
Compare Source
1.7.2 (January 31, 2024)
BUG FIXES:
env:
. (#34511)ENHANCEMENTS:
terraform fmt
: Terraform mock data files (.tfmock.hcl
) will now be included when executing the format command. (#34580)v1.7.1
Compare Source
1.7.1 (January 24, 2024)
BUG FIXES:
terraform test
: Fix crash when referencing variables or functions within the file levelvariables
block. (#34531)terraform test
: Fix crash whenoverride_module
block was missing theoutputs
attribute. (#34563)v1.7.0
Compare Source
1.7.0 (January 17, 2024)
UPGRADE NOTES:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.