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

feat: upgrades to esbuild@0.25.0 #29

Merged
merged 1 commit into from
Feb 11, 2025
Merged

feat: upgrades to esbuild@0.25.0 #29

merged 1 commit into from
Feb 11, 2025

Conversation

shawnzhu
Copy link
Member

No description provided.

@shawnzhu shawnzhu added the dependencies Pull requests that update a dependency file label Feb 11, 2025
Copy link
Member

@aecorredor aecorredor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think ESBuild doesn't follow semantic versioning to the teeth. I'm assuming there weren't any breaking changes from 0.20 -> 0.25?

@shawnzhu
Copy link
Member Author

@aecorredor good question. this is what chatGPT got:

Between versions 0.19.0 and 0.25.0, esbuild introduced several breaking changes:

Version 0.22.0: A change in this version inadvertently broke Amazon's AWS CDK due to unpinned dependencies. The esbuild team reverted the change to mitigate the issue.
GITHUB.COM

Version 0.25.0: This release deliberately included backward-incompatible changes. Users are advised to pin the exact version of esbuild in their package.json or use a version range syntax that only accepts patch upgrades to avoid unexpected issues.
CLASSIC.YARNPKG.COM

For a comprehensive list of changes and updates, please refer to esbuild's CHANGELOG.md.

I didn't see anything bed out of the changelogs between these releases.

if we see any break changes, I will upgrade blamda to 2.0.x

@shawnzhu shawnzhu merged commit c13bdd7 into master Feb 11, 2025
4 checks passed
@shawnzhu shawnzhu deleted the deps branch February 11, 2025 15:48
Copy link

🎉 This PR is included in version 1.10.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot added the released Has been released to the package repository (NPM, etc) label Feb 11, 2025
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 released Has been released to the package repository (NPM, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants