fix(deps): update dependency boto3 to v1.40.0#2225
Merged
ebyhr merged 1 commit intoapache:mainfrom Jul 31, 2025
Merged
Conversation
ebyhr
approved these changes
Jul 31, 2025
github-project-automation
bot
moved this from PRs In Progress
to Ready to merge
in Basic Kanban Board
github-project-automation
bot
moved this from Ready to merge
to Done
in Basic Kanban Board
snazy
added a commit
to snazy/polaris
that referenced
this pull request
Nov 20, 2025
* Simplify BaseMetaStoreManager.extractStorageConfiguration (apache#2194) as a static helper method its strongly preferable to not depend on the full `PolarisCallContext` if not necessary. * Remove PolarisCallContext from TreeMapMetaStore (apache#2195) * remove PolarisCallContext from TreeMapMetaStore methods * reset diagnosticServices in TreeMapMetaStore * simplify ensure methods * Remove getCurrentContext from InMemoryStorageIntegration (apache#2201) * Remove getCurrentContext from JWTBroker (apache#2202) * fix(deps): update dependency boto3 to v1.39.17 (apache#2211) * fix(deps): update dependency org.apache.commons:commons-compress to v1.28.0 (apache#2212) * Enable python client debug flag (apache#2154) * Enable python client debug flag * Move debug msg to stderr and move debug enable after option parsing * Remove postgres_latest as image tag (apache#2045) * Remove postgres_latest as image tag * Change image tag to latest for getting started examples * Change image tag to latest from helm * fix(deps): update dependency io.smallrye.common:smallrye-common-annotation to v2.13.8 (apache#2222) * Remove CallContextResolver (apache#2215) it seems like these were unused leftovers from previous changes * Replace CommitFailedException with CommitConflictException (apache#2198) * Replace CommitFailedException with CommitConflictException In some cases, we were using CommitFailedException to represent commit conflicts, which returns the correct 409 response but is tied to Iceberg. However, some of these conflicts originate from Polaris, making CommitConflictException a more appropriate and accurate choice. This change updates those instances to improve clarity and exception handling semantics. Resolves apache#2168 * JDBC: Include error code + SQL state in exception messages (apache#2220) * fix(deps): update dependency boto3 to v1.40.0 (apache#2225) * chore(deps): update actions/stale digest to 8f717f0 (apache#2224) * Fix Awaitility build configuration (apache#2232) * Fix compilation warnings in AzureCredentialStorageIntegrationTest (apache#2231) * Remove CallContext.CURRENT_CONTEXT (apache#2203) the last callers of `CallContext.getCurrentContext` had been removed in the following commits: - 756e535 - e7eb59f - 4d94745 thus we can now remove the `CURRENT_CONTEXT` threadlocal and all associated methods. * NoSQL: adoptions & cosmetics * Last merged commit 0449d9b --------- Co-authored-by: Christopher Lambert <[email protected]> Co-authored-by: Mend Renovate <[email protected]> Co-authored-by: Yong Zheng <[email protected]> Co-authored-by: Tamas Mate <[email protected]> Co-authored-by: Alexandre Dutra <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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:
==1.39.17->==1.40.0Release Notes
boto/boto3 (boto3)
v1.40.0Compare Source
======
customer-profiles: [botocore] The release updates standard profile with 2 new fields that supports account-level engagement. Updated APIs include CreateProfile, UpdateProfile, MergeProfiles, SearchProfiles, BatchGetProfile, GetSegmentMembership, CreateSegmentDefinition, CreateSegmentEstimate.ec2: [botocore] Added support for the force option for the EC2 instance terminate command. This feature enables customers to recover resources associated with an instance stuck in the shutting-down state as a result of rare issues caused by a frozen operating system or an underlying hardware problem.elbv2: [botocore] This release enables secondary IP addresses for Network Load Balancers.entityresolution: [botocore] Add support for creating advanced rule-based matching workflows in AWS Entity Resolution.glue: [botocore] Added support for Route node, S3 Iceberg sources/targets, catalog Iceberg sources, DynamoDB ELT connector, AutoDataQuality evaluation, enhanced PII detection with redaction, Kinesis fan-out support, and new R-series worker types.inspector2: [botocore] Extend usage to include agentless hours and add CODE_REPOSITORY to aggregation resource typeiot: [botocore] This release allows AWS IoT Core users to use their own AWS KMS keys for data protectionopensearch: [botocore] Granular access control support for NEO-SAML with IAMFederation for AOS data sourcequicksight: [botocore] Added Impala connector supports3control: [botocore] Add Tags field to CreateAccessPointsesv2: [botocore] This release introduces support for Multi-tenant managementworkspaces-web: [botocore] Added ability to log session activity on a portal to an S3 bucket.sts: [botocore] Updated the default sts service endpoint fromlegacytoregional. This behavior can be overridden using thests_regional_endpointssetting in the shared AWS config file or theAWS_STS_REGIONAL_ENDPOINTSenvironment variable.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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.