Prepare release for v1.3.0 (#378)

Author: lahsivjar

CHANGELOG.asciidoc

@@ -17,10 +17,10 @@
 ////
 
 [float]
-[[lambda-unreleased]]
-=== Unreleased
+[[lambda-1.3.0]]
+=== 1.3.0 - 2023/02/22
 
-https://github.com/elastic/apm-aws-lambda/compare/v1.2.0...main[View commits]
+https://github.com/elastic/apm-aws-lambda/compare/v1.2.0...v1.3.0[View commits]
 
 [float]
 ===== Features

RELEASE.md

@@ -5,7 +5,7 @@
 
 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. 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. 
+3. Create a test plan for any changes that require manual testing. Ensure that the automatic smoke test on the latest commit is successful.
 4. Trigger a release after succesful testing.
 
 ### Trigger a Release

extension/version.go

@@ -18,5 +18,5 @@
 package extension
 
 const (
-	Version = "1.2.0"
+	Version = "1.3.0"
 )