chore: Release 0.0.2

[miquelbeltran]

chore: Release 0.0.2

Description 📝

• Purpose: Prepare release
• Approach: Changelog and version bump

Type of change

• Chore

Updates

• Prepare for release

Test plan 🧪

dry run:

npm publish --dry-run

> @raygun.io/aws-lambda@0.0.2 prepare
> tsc

npm notice
npm notice 📦  @raygun.io/aws-lambda@0.0.2
npm notice Tarball Contents
npm notice 726B .github/dependabot.yml
npm notice 968B .github/ISSUE_TEMPLATE/bug_report.md
npm notice 700B .github/ISSUE_TEMPLATE/feature_request.md
npm notice 1.8kB .github/workflows/node.js.yml
npm notice 1.3kB .github/workflows/pr.yml
npm notice 661B CHANGELOG.md
npm notice 1.1kB LICENSE-MIT
npm notice 3.7kB README.md
npm notice 6.4kB assets/example-1.png
npm notice 27.6kB assets/example-2.png
npm notice 51.9kB assets/example-3.png
npm notice 14.6kB assets/example-4.png
npm notice 394B build/raygun.aws.d.ts
npm notice 6.3kB build/raygun.aws.js
npm notice 2.5kB eslint.config.mjs
npm notice 454B example/index.js
npm notice 7.6kB example/package-lock.json
npm notice 136B example/package.json
npm notice 767B example/prepare.sh
npm notice 3.6kB example/README.md
npm notice 2.6kB lib/raygun.aws.ts
npm notice 1.5kB package.json
npm notice 4.4kB test/raygun_aws_test.js
npm notice 2.9kB test/utils.js
npm notice 276B tsconfig.json
npm notice Tarball Details
npm notice name: @raygun.io/aws-lambda
npm notice version: 0.0.2
npm notice filename: raygun.io-aws-lambda-0.0.2.tgz
npm notice package size: 107.4 kB
npm notice unpacked size: 144.8 kB
npm notice shasum: fd5a8e42c031d62960be81142e613b87c7a19a20
npm notice integrity: sha512-fkF1LgEbbSsJB[...]dMOizHPb2V2oA==
npm notice total files: 25
npm notice
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access (dry-run)
+ @raygun.io/aws-lambda@0.0.2

Author to check 👓

• Project and all contained modules builds successfully
• Self-/dev-tested
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

Reviewer to check ✔️

• Project and all contained modules builds successfully
• Change has been dev-/reviewer-tested, where possible
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

[sumitramanga]

Looks good!!!