Skip to content

Prepare v1.2.0 #338

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 1, 2022
Merged

Prepare v1.2.0 #338

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions CHANGELOG.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,15 +20,18 @@
[[lambda-unreleased]]
=== Unreleased

https://github.com/elastic/apm-aws-lambda/compare/v1.1.0...main[View commits]

https://github.com/elastic/apm-aws-lambda/compare/v1.2.0...main[View commits]

[float]
===== Breaking changes
[[lambda-1.2.0]]
=== 1.2.0 - 2022/11/01

[float]
===== Features
- Parse and log APM Server error responses, and backoff on critical errors {lambda-pull}281[281]
- Disable CGO to prevent libc/ABI compatibility issues {lambda-pull}292[292]
- Deprecate `ELASTIC_APM_DATA_RECEIVER_TIMEOUT_SECONDS` in favour of `ELASTIC_APM_DATA_RECEIVER_TIMEOUT` {lambda-pull}294[294]
- Log shutdown reason on exit {lambda-pull}297[297]
- Add support for collecting and shipping function logs to APM Server {lambda-pull}303[303]
- Batch data collected from lambda logs API before sending to APM Server {lambda-pull}314[314]

Expand Down
9 changes: 4 additions & 5 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,9 @@
### Preparing a Release

1. Update the [`CHANGELOG.asciidoc`](CHANGELOG.asciidoc), by adding a new version heading (`==== 1.x.x - yyyy/MM/dd`) and changing the base tag of the Unreleased comparison URL
2. For major and minor releases, update the EOL table.
3. Ensure all changes are merged into github.com/elastic/apm-aws-lambda@main
4. Create a test plan for any changes that require manual testing. At the very minimum, a manual smoke test must be conducted before releasing.
5. Trigger a release after succesful testing.
2. Ensure all changes are merged into github.com/elastic/apm-aws-lambda@main
3. Create a test plan for any changes that require manual testing. At the very minimum, a manual smoke test must be conducted before releasing.
4. Trigger a release after succesful testing.

### Trigger a Release

Expand All @@ -26,4 +25,4 @@ Tag the release via your preferred tagging method. Tagging a release (v1.1.0) v
* [new tag] v1.1.0 -> v1.1.0

This will trigger a build in the CI that will create the Build Artifacts
and a Release in the Github UI.
and a Release in the Github UI.
2 changes: 1 addition & 1 deletion extension/version.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,5 +18,5 @@
package extension

const (
Version = "1.1.0"
Version = "1.2.0"
)