Repository navigation
[CI] Release only Lambda changes, with generated notes - #16
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PetrHeinz
changed the title
PetrHeinz
marked this pull request as ready for review
October 16, 2026 12:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Releases workflow cut a new version on every push to main, and none of those releases had a description since v0.4.0. Two changes:
index.js,src/**,package.json,package-lock.jsonorbuild/build.sh. README, CI and test changes no longer publish a version with the same code that users would re-upload for nothing. README.md and LICENSE are copied into the ZIP but do not count. Replayed over main's history, Update logtail/node #9, T-16672 Throw on ingesting errors so AWS retries the invocation #11, T-7532 Take the log level from a JSON message #13 and Update @logtail/node to 0.5.12 #15 would have released, while Update README.md: add build badge #7, SH-1002 [CI] Update GitHub Actions versions #10, SH-1113 Fail CI when a PR description contains a GitHub closing keyword #12 and E2E workflow: CloudWatch through the Lambda into a fresh source #14 would not.generateReleaseNotesinncipollo/release-action): the PRs merged since the previous release, new contributors and the full changelog link. It is the same generator the client libraries use throughgh release create --generate-notes, and the format all releases from v0.1.0 to v0.10.0 now show. PRs merged without a release are listed in the next release's notes.Merging this PR touches only the workflow, so it cuts no release.
🤖 Generated with Claude Code