-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: aws/aws-cdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.110.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: aws/aws-cdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.110.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 8 files changed
- 4 contributors
Commits on Nov 21, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 8fa6bdd - Browse repository at this point
Copy the full SHA 8fa6bddView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9202974 - Browse repository at this point
Copy the full SHA 9202974View commit details -
chore: build failing with unsafe-perm is not a valid npm option (#28069)
We switched the images used to run our main build to jsii/superchain:bullseye-slim-node18 which comes with Node.js 18 instead of Node.js 16. This Node.js upgrade also includes an upgraded version of npm, and in recent npm versions, the unsef-perm option is not required anymore. This change simply removes the now redundant command. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Configuration menu - View commit details
-
Copy full SHA for 1cc484b - Browse repository at this point
Copy the full SHA 1cc484bView commit details -
chore: pr-build failing with unsafe-perm is not a valid npm option (#…
…28068) We switched the images used to build PRs to `jsii/superchain:bullseye-slim-node18` which comes with Node.js 18 instead of Node.js 16. This Node.js upgrade also includes an upgraded version of npm, and in recent npm versions, the unsef-perm option is not required anymore. This change simply removes the now redundant command. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Configuration menu - View commit details
-
Copy full SHA for 8f5e319 - Browse repository at this point
Copy the full SHA 8f5e319View commit details -
Configuration menu - View commit details
-
Copy full SHA for d57d1d5 - Browse repository at this point
Copy the full SHA d57d1d5View commit details -
chore(release): v2.110.1 (#28093)
See CHANGELOG ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Configuration menu - View commit details
-
Copy full SHA for 0d37f0d - Browse repository at this point
Copy the full SHA 0d37f0dView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.110.0...v2.110.1