-
Notifications
You must be signed in to change notification settings - Fork 168
Closed
Labels
automationThis item relates to automationThis item relates to automationcompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
Description
Bug description
Before releasing a new version I was running e2e tests. The integration tests for all Node.js versions are failing due to what appears to be a version mismatch between the version in the layer and the one expected:
{\"level\":\"ERROR\",\"message\":\"Package version mismatch: ${packageJSON.version} != ${process.env.POWERTOOLS_PACKAGE_VERSION}\",\"service\":\"e2e-tests-layer-consumer\",\"timestamp\":\"2022-10-11T12:34:47.567Z\",\"xray_trace_id\":\"1-634562e7-4fdd82be20abfd125ce2ea64\"}
From here.
Looking at the tested code, the error seems to be thrown from here.
At the same time, looking at the code that creates the test, the expected version is declared here.
Expected Behavior
E2e tests should pass successfully.
Current Behavior
Tests are failing.
Possible Solution
Review version expected vs actual.
Steps to Reproduce
Run e2e tests.
Environment
- Powertools version used: latest
- Packaging format (Layers, npm): Layers
- AWS Lambda function runtime: all
- Debugging logs: See above.
Related issues, RFCs
N/A
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationcompletedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)