Skip to content
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 dependency @pulumi/awsx to v2 #887

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@pulumi/awsx (source) 0.40.1 -> 2.0.2 age adoption passing confidence

Release Notes

pulumi/pulumi-awsx (@​pulumi/awsx)

v2.0.2

Compare Source

v2.0.0

Compare Source

v1.0.6

Compare Source

v1.0.5

Compare Source

v1.0.4

Compare Source

v1.0.3

Compare Source

What's Changed

Full Changelog: pulumi/pulumi-awsx@v1.0.2...v1.0.3

v1.0.2

Compare Source

v1.0.1

Compare Source

v1.0.0

Compare Source

What's Changed

  • Created new schematized components to be available to every supported Pulumi language
  • ECS defaults to private and must be explicitly made public by setting AssignPublicId=true
  • Upgrade internal dependencies for the Pulumi and AWS packages.
  • Expose all arguments of the underlying resources through the components for greater control.
  • Maintain existing 0.x code within the classic namespace to allow slower trasitioning to the new component versions.
  • Vastly improved VPC component with better defaults and layout options.
  • Improved networking detaults for load ballancers and Fargate ECS services.

Migration from 0.x to 1.0

Before version 1, this package only supported components in TypeScript. All the existing components from the 0.x releases are now available in the classic namespace. The classic namespace will remain until the next major version release but will only receive updates for critical security fixes.

  1. Change references from @pulumi/awsx to @pulumi/awsx/classic to maintain existing behaviour.
  2. Refactor to replace the classic components with the new top-level components.

Note: The new top-level components (outside the classic namespace) may require additional code changes and resource re-creation.

New Contributors

Full Changelog: pulumi/pulumi-awsx@v0.40.1...v1.0.0


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 18, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 18, 2023

✅ Benchmark Results

     ✓ no-errors
     ✓ expected-result

     checks.........................: 100.00% ✓ 256006      ✗ 0     
     data_received..................: 25 MB   841 kB/s
     data_sent......................: 10 MB   341 kB/s
     http_req_blocked...............: avg=1.43µs   min=900ns   med=1.2µs    max=629.02µs p(90)=1.8µs    p(95)=2.1µs   
     http_req_connecting............: avg=4ns      min=0s      med=0s       max=553.32µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=159.04µs min=87.8µs  med=129.4µs  max=19.8ms   p(90)=191.31µs p(95)=219.21µs
       { expected_response:true }...: avg=159.04µs min=87.8µs  med=129.4µs  max=19.8ms   p(90)=191.31µs p(95)=219.21µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 128003
     http_req_receiving.............: avg=22.57µs  min=11.8µs  med=17.8µs   max=8.12ms   p(90)=34.6µs   p(95)=37.5µs  
     http_req_sending...............: avg=7.53µs   min=4.4µs   med=5.5µs    max=10.38ms  p(90)=9.9µs    p(95)=12.6µs  
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=128.93µs min=66.5µs  med=102.7µs  max=19.42ms  p(90)=154.9µs  p(95)=179.6µs 
     http_reqs......................: 128003  4266.505453/s
     iteration_duration.............: avg=228.16µs min=143.1µs med=192.11µs max=20.25ms  p(90)=273.81µs p(95)=310.91µs
     iterations.....................: 128003  4266.505453/s
     vus............................: 0       min=0         max=1   
     vus_max........................: 1       min=1         max=1   

@renovate renovate bot force-pushed the renovate/pulumi-awsx-2.x branch 5 times, most recently from e0beb7f to 9311c34 Compare October 25, 2023 08:43
@github-actions
Copy link
Contributor

github-actions bot commented Oct 25, 2023

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@whatwg-node/fetch 0.9.14-alpha-20231025085344-e9f63c6 npm ↗︎ unpkg ↗︎
@whatwg-node/node-fetch 0.5.0-alpha-20231025085344-e9f63c6 npm ↗︎ unpkg ↗︎

@renovate renovate bot force-pushed the renovate/pulumi-awsx-2.x branch from 9311c34 to e9f63c6 Compare October 25, 2023 08:51
@ardatan ardatan closed this Oct 25, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Oct 25, 2023

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/pulumi-awsx-2.x branch October 25, 2023 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant