Renovate Update Patch & Minor Updates #708
Merged
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:
~> 5.16.0
->~> 5.17.0
==1.28.43
->==1.28.48
1.28.49
1.10.1
->1.10.3
0.19.2
->0.19.3
v1.21.0
->v1.22.0
v1.18.0
->v1.19.0
v0.43.0
->v0.44.0
v0.43.0
->v0.44.0
v1.18.0
->v1.19.0
v1.17.0
->v1.18.0
v1.17.0
->v1.18.0
v1.17.0
->v1.18.0
v1.17.0
->v1.18.0
v1.58.0
->v1.58.1
1.66.1
->1.67.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
hashicorp/terraform-provider-aws (aws)
v5.17.0
Compare Source
NOTES:
/
as the value forkey
is no longer supported (#33358)FEATURES:
aws_shield_application_layer_automatic_response
(#33432)aws_verifiedaccess_instance
(#33459)ENHANCEMENTS:
checksum_mode
argument andchecksum_crc32
,checksum_crc32c
,checksum_sha1
andchecksum_sha256
attributes (#33358)details.region.bucket_account_id
attribute (#33416)checksum_algorithm
argument andchecksum_crc32
,checksum_crc32c
,checksum_sha1
andchecksum_sha256
attributes (#33358)checksum_algorithm
argument andchecksum_crc32
,checksum_crc32c
,checksum_sha1
andchecksum_sha256
attributes (#33358)details.region.bucket_account_id
argument to support cross-account Multi-Region Access Points (#33416)details.region.region
attribute (#33416)JSONSchemaDraft4
schema type support (#35971)sftp_config
argument and makeas2_config
optional (#32741)WAFOptimisticLockException
errors (#33432)BUG FIXES:
replication_task_settings
isnil
(#33456)redis
engine types caused by the newtransit_encryption_enabled
argument (#33451)kms_key_arn
on restore from DB cluster snapshot (#33413)provisioning_artifact_parameters
attribute (#33448)v5.16.2
Compare Source
FEATURES:
aws_cognito_identity_pool
(#33053)aws_verifiedaccess_trust_provider
(#33195)ENHANCEMENTS:
instance_refresh.preferences.scale_in_protected_instances
andinstance_refresh.preferences.standby_instances
fromWait
to the Amazon EC2 Auto Scaling console recommended value ofIgnore
(#33382)alias
attribute (#33388)BUG FIXES:
ValidationError
errors when starting Auto Scaling group instance refresh (#33382)InvalidParameter
errors on Update with Kafka destinations (#33360)name
(#33405)name
(#33405)name
(#33405)name
(#33405)lb_name
(#33405)lb_name
(#33405)lb_name
(#33405)lb_name
(#33405)lb_name
(#33405)lb_name
(#33405)v5.16.1
Compare Source
BUG FIXES:
Search returned 0 results
errors when there are more than 101 file systems in the configured Region (#33336)unexpected state
errors on resource Create (#33369)metadata_location
andtable_type
parameters
when updating Iceberg tables (#33374)boto/boto3 (boto3)
v1.28.48
Compare Source
=======
appstream
: [botocore
] This release introduces multi-session fleets, allowing customers to provision more than one user session on a single fleet instance.cloudformation
: [botocore
] Documentation updates for AWS CloudFormationentityresolution
: [botocore
] Changed "ResolutionTechniques" and "MappedInputFields" in workflow and schema mapping operations to be required fields.lookoutequipment
: [botocore
] This release adds APIs for the new scheduled retraining feature.v1.28.47
Compare Source
=======
cloud9
: [botocore
] Update to include information on Ubuntu 18 deprecation.drs
: [botocore
] Updated existing APIs and added new ones to support using AWS Elastic Disaster Recovery post-launch actions. Added support for new regions.firehose
: [botocore
] DocumentIdOptions has been added for the Amazon OpenSearch destination.guardduty
: [botocore
] AddmanagementType
field to ListCoverage API response.internetmonitor
: [botocore
] This release updates the Amazon CloudWatch Internet Monitor API domain name.ivs-realtime
: [botocore
] Doc only update that changes description for ParticipantToken.simspaceweaver
: [botocore
] Edited the introductory text for the API reference.xray
: [botocore
] Add StartTime field in GetTraceSummaries API response for each TraceSummary.v1.28.46
Compare Source
=======
ec2
: [botocore
] This release adds support for restricting public sharing of AMIs through AMI Block Public Accessevents
: [botocore
] Update events client to latest versionkendra
: [botocore
] Amazon Kendra now supports confidence score buckets for retrieved passage results using the Retrieve API.v1.28.45
Compare Source
=======
ecr
: [botocore
] This release will have ValidationException be thrown from ECR LifecyclePolicy APIs in regions LifecyclePolicy is not supported, this includes existing Amazon Dedicated Cloud (ADC) regions. This release will also change Tag: TagValue and Tag: TagKey to required.medialive
: [botocore
] AWS Elemental Link now supports attaching a Link UHD device to a MediaConnect flow.quicksight
: [botocore
] This release launches new updates to QuickSight KPI visuals - support for sparklines, new templated layout and new targets for conditional formatting rules.v1.28.44
Compare Source
=======
fsx
: [botocore
] Amazon FSx documentation fixessagemaker
: [botocore
] Autopilot APIs will now support holiday featurization for Timeseries models. The models will now hold holiday metadata and should be able to accommodate holiday effect during inference.sso-admin
: [botocore
] Content updates to IAM Identity Center API for China Regions.workspaces
: [botocore
] A new field "ErrorDetails" will be added to the output of "DescribeWorkspaceImages" API call. This field provides in-depth details about the error occurred during image import process. These details include the possible causes of the errors and troubleshooting information.dmtrKovalenko/cypress-real-events (cypress-real-events)
v1.10.3
Compare Source
Changes
v1.10.2
Compare Source
evanw/esbuild (esbuild)
v0.19.3
Compare Source
Fix
list-style-type
with thelocal-css
loader (#3325)The
local-css
loader incorrectly treated all identifiers provided tolist-style-type
as a custom local identifier. That included identifiers such asnone
which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:Note that this bug only affected code using the
local-css
loader. It did not affect code using thecss
loader.Avoid inserting temporary variables before
use strict
(#3322)This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before
use strict
directives:Adjust TypeScript
enum
output to better approximatetsc
(#3329)TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:
However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:
The template literal initializer for
PRESENT
is treated as a string while the template literal initializer forMISSING
is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior oftsc
but in the case where the behavior divergestsc
reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see thedeclare
keyword), which esbuild deliberately doesn't do.Ignore case in CSS in more places (#3316)
This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:
Please never actually write code like this.
Improve the error message for
null
entries inexports
(#3377)Package authors can disable package export paths with the
exports
map inpackage.json
. With this release, esbuild now has a clearer error message that points to thenull
token inpackage.json
itself instead of to the surrounding context. Here is an example of the new error message:Parse and print the
with
keyword inimport
statementsJavaScript was going to have a feature called "import assertions" that adds an
assert
keyword toimport
statements. It looked like this:The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.
Instead, the current proposal is to add a feature called "import attributes" instead that adds a
with
keyword to import statements. It looks like this:This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new
with
keyword. Thewith
keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.open-telemetry/opentelemetry-go-contrib (go.opentelemetry.io/contrib/detectors/aws/ecs)
v1.19.0
: /v0.44.0/v0.13.0Compare Source
Added
gcp.gce.instance.name
andgcp.gce.instance.hostname
resource attributes togo.opentelemetry.io/contrib/detectors/gcp
. (#4263)Changed
go.opentelemetry.io/contrib/detectors/aws/ec2
have been upgraded to v1.21.0. (#4265)go.opentelemetry.io/contrib/detectors/aws/ecs
have been upgraded to v1.21.0. (#4265)go.opentelemetry.io/contrib/detectors/aws/eks
have been upgraded to v1.21.0. (#4265)go.opentelemetry.io/contrib/detectors/aws/lambda
have been upgraded to v1.21.0. (#4265)go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-lambda-go/otellambda
have been upgraded to v1.21.0. (#4265)faas.execution
attribute is nowfaas.invocation_id
.faas.id
attribute is nowaws.lambda.invoked_arn
.go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/otelaws
have been upgraded to v1.21.0. (#4265)http.request.method
attribute will only allow known HTTP methods from the metrics generated bygo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
. (#4277)Removed
net.sock.peer.addr
,net.sock.peer.port
,http.user_agent
,enduser.id
, andhttp.client_ip
were removed from the metrics generated bygo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
. (#4277)go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego
module is removed. (#4295)go.opentelemetry.io/contrib/instrumentation/github.com/go-kit/kit/otelkit
module is removed. (#4295)go.opentelemetry.io/contrib/instrumentation/github.com/Shopify/sarama/otelsarama
module is removed. (#4295)go.opentelemetry.io/contrib/instrumentation/github.com/bradfitz/gomemcache/memcache/otelmemcache
module is removed. (#4295)go.opentelemetry.io/contrib/instrumentation/github.com/gocql/gocql/otelgocql
module is removed. (#4295)New Contributors
Full Changelog: open-telemetry/opentelemetry-go-contrib@v1.18.0...v1.19.0
open-telemetry/opentelemetry-go (go.opentelemetry.io/otel)
v1.18.0
: /v0.41.0/v0.0.6Compare Source
This release drops the compatibility guarantee of Go 1.19.
Added
WithProducer
option ingo.opentelemetry.op/otel/exporters/prometheus
to restore the ability to register producers on the prometheus exporter's manual reader. (#4473)IgnoreValue
option ingo.opentelemetry.io/otel/sdk/metric/metricdata/metricdatatest
to allow ignoring values when comparing metrics. (#4447)Deprecated
NewMetricExporter
ingo.opentelemetry.io/otel/bridge/opencensus
was deprecated inv0.35.0
(#3541).The deprecation notice format for the function has been corrected to trigger Go documentation and build tooling. (#4470)
Removed
go.opentelemetry.io/otel/exporters/jaeger
package. (#4467)go.opentelemetry.io/otel/example/jaeger
package. (#4467)go.opentelemetry.io/otel/sdk/metric/aggregation
package. (#4468)go.opentelemetry.io/otel/exporters/otlp
and its sub-packages. (#4469)New Contributors
Full Changelog: open-telemetry/opentelemetry-go@v1.17.0...v1.18.0
grpc/grpc-go (google.golang.org/grpc)
v1.58.1
: Release 1.58.1Compare Source
Bug Fixes
sass/dart-sass (sass)
v1.67.0
Compare Source
All functions defined in CSS Values and Units 4 are now once again parsed as
calculation objects:
round()
,mod()
,rem()
,sin()
,cos()
,tan()
,asin()
,acos()
,atan()
,atan2()
,pow()
,sqrt()
,hypot()
,log()
,exp()
,abs()
, andsign()
.Unlike in 1.65.0, function calls are not locked into being parsed as
calculations or plain Sass functions at parse-time. This means that
user-defined functions will take precedence over CSS calculations of the same
name. Although the function names
calc()
andclamp()
are still forbidden,users may continue to freely define functions whose names overlap with other
CSS calculations (including
abs()
,min()
,max()
, andround()
whosenames overlap with global Sass functions).
Breaking change: As a consequence of the change in calculation parsing
described above, calculation functions containing interpolation are now parsed
more strictly than before. However, almost all interpolations that would
have produced valid CSS will continue to work. The only exception is
#{$variable}%
which is not valid in Sass and is no longer valid incalculations. Instead of this, either use
$variable
directly and ensure italready has the
%
unit, or write($variable * 1%)
.Potentially breaking bug fix: The importer used to load a given file is no
longer used to load absolute URLs that appear in that file. This was
unintented behavior that contradicted the Sass specification. Absolute URLs
will now correctly be loaded only from the global importer list. This applies
to the modern JS API, the Dart API, and the embedded protocol.
Embedded Sass
files or files that require many importer or function call round-trips with
the embedded host.
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.