client-auto-scaling: Amazon EC2 Auto Scaling now provides EBS health check to manage EC2 instance replacement (041f6dd9)
New Features
client-route-53: Amazon Route 53 now supports the Asia Pacific (Malaysia) Region (ap-southeast-5) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region. (b3d22dec)
client-emr-containers: Correct endpoint for FIPS is configured for US Gov Regions. (0cd9baec)
client-inspector2: Add enums for Agentless scan statuses and EC2 enablement error states (52856e7f)
client-quicksight: Explicit query for authors and dashboard viewing sharing for embedded users (18135bcc)
client-bedrock: Amazon Bedrock Evaluation BatchDeleteEvaluationJob API allows customers to delete evaluation jobs under terminated evaluation job statuses - Stopped, Failed, or Completed. Customers can submit a batch of 25 evaluation jobs to be deleted at once. (06501cbb)
For list of updated packages, view updated-packages.md in assets-3.637.0.zip
v3.636.0
3.636.0(2024-08-21)
Chores
turbo: simplify build scripts in package.json (#6366) (614d98e1)
Documentation Changes
link to smithy/middleware-retry in Notable Changes (#6397) (31263194)
New Features
clients: update client endpoints as of 2024-08-21 (f8aaf1df)
client-ses: Enable email receiving customers to provide SES with access to their S3 buckets via an IAM role for "Deliver to S3 Action" (aafc6ebd)
client-entityresolution: Increase the mapping attributes in Schema to 35. (d038be36)
client-glue: Add optional field JobRunQueuingEnabled to CreateJob and UpdateJob APIs. (b3bbf579)
client-securityhub: Security Hub documentation and definition updates (17db5f7e)
client-lambda: Release FilterCriteria encryption for Lambda EventSourceMapping, enabling customers to encrypt their filter criteria using a customer-owned KMS key. (6fff3639)
client-ec2: DescribeInstanceStatus now returns health information on EBS volumes attached to Nitro instances (1baa7ea8)
client-auto-scaling: Amazon EC2 Auto Scaling now provides EBS health check to manage EC2 instance replacement (041f6dd9)
New Features
client-route-53: Amazon Route 53 now supports the Asia Pacific (Malaysia) Region (ap-southeast-5) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region. (b3d22dec)
client-emr-containers: Correct endpoint for FIPS is configured for US Gov Regions. (0cd9baec)
client-inspector2: Add enums for Agentless scan statuses and EC2 enablement error states (52856e7f)
client-quicksight: Explicit query for authors and dashboard viewing sharing for embedded users (18135bcc)
client-bedrock: Amazon Bedrock Evaluation BatchDeleteEvaluationJob API allows customers to delete evaluation jobs under terminated evaluation job statuses - Stopped, Failed, or Completed. Customers can submit a batch of 25 evaluation jobs to be deleted at once. (06501cbb)
For list of updated packages, view updated-packages.md in assets-3.637.0.zip
v3.636.0
3.636.0(2024-08-21)
Chores
turbo: simplify build scripts in package.json (#6366) (614d98e1)
Documentation Changes
link to smithy/middleware-retry in Notable Changes (#6397) (31263194)
New Features
clients: update client endpoints as of 2024-08-21 (f8aaf1df)
client-ses: Enable email receiving customers to provide SES with access to their S3 buckets via an IAM role for "Deliver to S3 Action" (aafc6ebd)
client-entityresolution: Increase the mapping attributes in Schema to 35. (d038be36)
client-glue: Add optional field JobRunQueuingEnabled to CreateJob and UpdateJob APIs. (b3bbf579)
client-securityhub: Security Hub documentation and definition updates (17db5f7e)
client-lambda: Release FilterCriteria encryption for Lambda EventSourceMapping, enabling customers to encrypt their filter criteria using a customer-owned KMS key. (6fff3639)
client-ec2: DescribeInstanceStatus now returns health information on EBS volumes attached to Nitro instances (1baa7ea8)
Note: This package will now be versioned according to the version of semantic conventions being provided.
:rocket: (Enhancement)
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
v1.26.0
1.26.0
:rocket: (Enhancement)
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
Today, we are excited to share the 5.19.0 stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟
Highlights
Introducing TypedSQL
TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.
To get started with TypedSQL:
Make sure that you have the latest version of prisma and @prisma/client installed:
Create a sql subdirectory of your prisma directory.
mkdir -p prisma/sql
You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:
SELECT u.id, u.name, COUNT(p.id) as "postCount"
FROM "User" u
LEFT JOIN "Post" p ON u.id = p."authorId"
GROUP BY u.id, u.name
Import your SQL query into your code with the @prisma/client/sql import:
import { PrismaClient } from '@prisma/client'
import { getUsersWithPosts } from '@prisma/client/sql'
... (truncated)
Commits
0f63437 chore(deps): update engines to 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b...
a411e43 chore(deps): update engines to 5.19.0-30.de1356e7b79f44aaa2d308a544c32a4d2951...
1ff458a chore(deps): update engines to 5.19.0-27.0bc306ebdcdb88c93b6fd25d43855afc7e4f...
Bumps the prod group with 18 updates in the / directory:
3.633.03.637.03.633.03.637.09.3.19.4.00.49.10.49.20.52.10.53.00.52.10.53.01.25.11.26.00.52.10.53.05.18.05.19.08.26.08.27.08.26.08.27.00.5.150.5.161.7.41.7.74.4.34.4.413.6.013.8.01.0.12.0.12.6.32.7.00.14.100.15.0Updates
@aws-sdk/client-s3from 3.633.0 to 3.637.0Release notes
Sourced from
@aws-sdk/client-s3's releases.... (truncated)
Changelog
Sourced from
@aws-sdk/client-s3's changelog.Commits
ee762fePublish v3.637.02c0f590Publish v3.635.0b474584feat(client-s3): Amazon Simple Storage Service / Features : Add support for c...5154d4ffeat(codegen): add Smithy RPCv2 CBOR to list of protocols (#6096)Updates
@aws-sdk/s3-request-presignerfrom 3.633.0 to 3.637.0Release notes
Sourced from
@aws-sdk/s3-request-presigner's releases.... (truncated)
Changelog
Sourced from
@aws-sdk/s3-request-presigner's changelog.Commits
ee762fePublish v3.637.02c0f590Publish v3.635.05154d4ffeat(codegen): add Smithy RPCv2 CBOR to list of protocols (#6096)Updates
@fastify/cookiefrom 9.3.1 to 9.4.0Release notes
Sourced from
@fastify/cookie's releases.Commits
4e816afBumped v9.4.0d2b6413fix: stricter types for unsigned cookies (#292)cd9f415chore(deps-dev): bump sinon from 17.0.2 to 18.0.0 (#286)b161b07Fix problematic type comments (#284)70bf13fAdd algorithm and security notice (#285)e41c436chore(deps-dev): bump tsd from 0.30.7 to 0.31.0 (#283)cb3346ffix: use request.protocol to check for HTTPS (#282)c474dbechore(.gitignore): add .tap/ dir (#278)Updates
@opentelemetry/auto-instrumentations-nodefrom 0.49.1 to 0.49.2Release notes
Sourced from
@opentelemetry/auto-instrumentations-node's releases.Commits
1945456chore: release main (#2375)0f90b3dfix(auto-instrumentations-node): shutdown the SDK when the process exits norm...2105609fix(instrumentation-generic-pool): update span name typo (#2405)d7a5bd4fix(detectors): reduce diag level on detectors failing to detect (#2382)d30c85cfeat(instr-tedious): support tedious@19 (#2401)de7a6cbfix(instrumentation-redis-4): avoid crash from incorrect this._diag ref (#2397)ca70bb9fix(instr-undici): fix issue with config in constructor (#2395)7054bc1export class TestMetricReader (#2393)7e27039create test metric reader (#2388)8b35f78chore(deps): update dependency babel-plugin-istanbul to v7 (#2326)Updates
@opentelemetry/exporter-prometheusfrom 0.52.1 to 0.53.0Release notes
Sourced from
@opentelemetry/exporter-prometheus's releases.Commits
720bc8cchore: prepare next release (#4960)65cedf7chore: prepare next release (#4949)bd25230docs: document console exporter output stability (#4956)948496dchore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17docs: Describe support for ESM (#4876)2ca2459test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52chore: prepare next release (#4939)5578a11chore: sync package-lock.json (#4947)5c1ae0adocs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@opentelemetry/exporter-trace-otlp-httpfrom 0.52.1 to 0.53.0Release notes
Sourced from
@opentelemetry/exporter-trace-otlp-http's releases.Commits
720bc8cchore: prepare next release (#4960)65cedf7chore: prepare next release (#4949)bd25230docs: document console exporter output stability (#4956)948496dchore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17docs: Describe support for ESM (#4876)2ca2459test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52chore: prepare next release (#4939)5578a11chore: sync package-lock.json (#4947)5c1ae0adocs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@opentelemetry/sdk-metricsfrom 1.25.1 to 1.26.0Release notes
Sourced from
@opentelemetry/sdk-metrics's releases.Changelog
Sourced from
@opentelemetry/sdk-metrics's changelog.Commits
720bc8cchore: prepare next release (#4960)65cedf7chore: prepare next release (#4949)bd25230docs: document console exporter output stability (#4956)948496dchore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17docs: Describe support for ESM (#4876)2ca2459test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52chore: prepare next release (#4939)5578a11chore: sync package-lock.json (#4947)5c1ae0adocs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@opentelemetry/sdk-nodefrom 0.52.1 to 0.53.0Release notes
Sourced from
@opentelemetry/sdk-node's releases.Commits
720bc8cchore: prepare next release (#4960)65cedf7chore: prepare next release (#4949)bd25230docs: document console exporter output stability (#4956)948496dchore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17docs: Describe support for ESM (#4876)2ca2459test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52chore: prepare next release (#4939)5578a11chore: sync package-lock.json (#4947)5c1ae0adocs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@prisma/clientfrom 5.18.0 to 5.19.0Release notes
Sourced from
@prisma/client's releases.... (truncated)
Commits
0f63437chore(deps): update engines to 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b...a411e43chore(deps): update engines to 5.19.0-30.de1356e7b79f44aaa2d308a544c32a4d2951...1ff458achore(deps): update engines to 5.19.0-27.0bc306ebdcdb88c93b6fd25d43855afc7e4f...8957496feat(client): Typed SQL (#24907)Looks like these dependencies are updatable in another way, so this is no longer needed.