Skip to content

chore(release): 2.239.0#37033

Merged
mergify[bot] merged 6 commits intov2-releasefrom
bump/2.239.0
Feb 19, 2026
Merged

chore(release): 2.239.0#37033
mergify[bot] merged 6 commits intov2-releasefrom
bump/2.239.0

Conversation

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

@aws-cdk-automation aws-cdk-automation commented Feb 19, 2026

See CHANGELOG

aemada-aws and others added 5 commits February 19, 2026 08:03
… integ tests (#36972)

### Issue # (if applicable)

Closes #N/A

### Reason for this change

Integration tests in `aws-location-alpha` were failing due to:
1. AWS Location Service CFN resources not available in all regions — tests had no region constraints
2. `ExpireTime must not be in the past` — `integ.api-key` had hardcoded expiry `2026-01-01` which is now past

### Description of changes

- Added `regions` constraint to all 6 IntegTest definitions, limiting to regions where Location Service is available: `us-east-1`, `us-west-2`, `eu-west-1`, `eu-central-1`, `ap-southeast-1`, `ap-northeast-1`
- Updated `expireTime` in `integ.api-key.ts` from `2026-01-01` to `2028-01-01`
- Regenerated all snapshots

### Describe any new or updated permissions being added

No new permissions.

### Description of how you validated changes

```
yarn integ test/integ.map.js test/integ.api-key.js test/integ.tracker.js \
  test/integ.place-index.js test/integ.geofence-collection.js \
  --disable-update-workflow --update-on-failed --force \
  --parallel-regions us-east-1 us-west-2 --verbose

Tests: 5 passed, 5 total
```

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable)

N/A

### Reason for this change

Upgrading the `jsii-rosetta` version to bring in this fix (aws/jsii-rosetta#3579) which is more tolerant of multiple concrete dependencies with the same version number - it picks either one dependency instead of failing (which was causing pipeline build failures)

### Description of changes

Upgraded the `jsii-rosetta` version.

### Describe any new or updated permissions being added

N/A

### Description of how you validated changes

N/A

### Checklist
- [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…#37022)

Upgrade `ajv` to `8.18.0`, which is version that is not vulnerable to a ReDoS attack anymore.

Note that CDK never had an actual vulnerability in the first place because the input was not attacker-controlled, but CVE scanners will flag this finding regardless.

This overrides the package in our repository, the dependency that gets installed at build time is bundled into the final `aws-cdk-lib` tarball.

Closes #36989

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec`

**L1 CloudFormation resource definition changes:**
```
├[~] service aws-arcregionswitch
│ └ resources
│    └[~]  resource AWS::ARCRegionSwitch::Plan
│       └      - arnTemplate: arn:${Partition}:arc-region-switch:${Region}:${Account}:plan/${ResourceId}
│              + arnTemplate: arn:${Partition}:arc-region-switch::${Account}:plan/${ResourceId}
├[~] service aws-pinpoint
│ └ resources
│    ├[~]  resource AWS::Pinpoint::EmailTemplate
│    │  └      - arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/PUSH
│    │         + arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/EMAIL
│    ├[~]  resource AWS::Pinpoint::InAppTemplate
│    │  └      - arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/PUSH
│    │         + arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/EMAIL
│    └[~]  resource AWS::Pinpoint::SmsTemplate
│       └      - arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/PUSH
│              + arnTemplate: arn:${Partition}:mobiletargeting:${Region}:${Account}:templates/${TemplateName}/SMS
└[~] service aws-ram
  └ resources
     └[~]  resource AWS::RAM::Permission
        └      - arnTemplate: arn:${Partition}:ram::${Account}:permission/${ResourcePath}
               + arnTemplate: arn:${Partition}:ram:${Region}:${Account}:permission/${ResourcePath}
```
@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Feb 19, 2026
@aws-cdk-automation aws-cdk-automation requested a review from a team February 19, 2026 16:17
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Feb 19, 2026

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Feb 19, 2026

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify Bot merged commit e83bb46 into v2-release Feb 19, 2026
17 of 18 checks passed
@mergify mergify Bot deleted the bump/2.239.0 branch February 19, 2026 17:43
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Feb 19, 2026

Merge Queue Status

Rule: default-merge


  • Entered queue2026-02-19 17:43 UTC
  • Checks passed · in-place
  • Merged2026-02-19 17:43 UTC · at e458da3e24f6a974ba370b92165040fbcc245238

This pull request spent 7 seconds in the queue, with no time running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build
  • any of [🛡 GitHub branch protection]:
    • check-success = validate-pr
    • check-neutral = validate-pr
    • check-skipped = validate-pr

@github-actions
Copy link
Copy Markdown
Contributor

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Feb 19, 2026
@aws-cdk-automation aws-cdk-automation added the pr/needs-maintainer-review This PR needs a review from a Core Team Member label Feb 19, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

auto-approve contribution/core This is a PR that came from AWS. p2 pr/needs-maintainer-review This PR needs a review from a Core Team Member pr/no-squash This PR should be merged instead of squash-merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants