Skip to content

fix: node lambda version#216

Merged
gadomski merged 1 commit into
mainfrom
force-release
Dec 1, 2025
Merged

fix: node lambda version#216
gadomski merged 1 commit into
mainfrom
force-release

Conversation

@gadomski
Copy link
Copy Markdown
Contributor

@gadomski gadomski commented Dec 1, 2025

This is an empty commit to trigger a release. I always forget that chore: won't trigger one, and I'd like a release to use in a downstream project.

This is an empty commit to trigger a release.
@gadomski gadomski requested a review from hrodmn December 1, 2025 16:15
@gadomski gadomski self-assigned this Dec 1, 2025
@gadomski gadomski merged commit f777304 into main Dec 1, 2025
5 checks passed
@gadomski gadomski deleted the force-release branch December 1, 2025 16:23
github-actions Bot pushed a commit that referenced this pull request Dec 1, 2025
## [10.4.1](v10.4.0...v10.4.1) (2025-12-01)

### Bug Fixes

* node lambda version ([#216](#216)) ([f777304](f777304))
@ds-release-bot
Copy link
Copy Markdown
Contributor

ds-release-bot Bot commented Dec 1, 2025

🎉 This PR is included in version 10.4.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants