Bug: `Error: Environment variable AWS_REGION is required` in Unit Tests in v2.25.0

[AplusKminus]

Expected Behavior

Simply upgrading 2.24.1 to 2.25.0 should not break existing behavior (unless specified in the release notes). Especially not unit tests that do not run in a Lambda context.

Current Behavior

All unit tests fail with the error message:

Error: Environment variable AWS_REGION is required

Code snippet

The file someFunction.ts:

import { Logger } from "@aws-lambda-powertools/logger";

const logger = new Logger({
    serviceName: "service-name",
});

export const someFunction = (input: string): string => {
    logger.info(input);
    return input;
};

The file someFunction.test.ts:

import { describe, expect, it } from "vitest";
import { someFunction } from "./someFunction.js";

describe("test someFunction", () => {
    it("should return its parameter", () => {
        expect(someFunction("test input")).toBe("test input");
    });
});

Steps to Reproduce

1. Add the two files provided above and execute the test file.
2. It should not fail.

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

2.25.0

AWS Lambda function runtime

22.x

Packaging format used

npm

Execution logs

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link

[svozza]

We are aware of this issue and are tracking it in #4318. We will be doing a patch release today with a fix. I will close this issue in favour of the original issue.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[AplusKminus]

@svozza thank you! I didn't find the referenced issue as it was already closed. I guess this is just an issue of how GitHub handles "closes #n" messages.

[svozza]

I will post a message in here when the release is out, I'm just in the process of doing it now.

[dreamorosi]

Release notes are not out, and release workflow is still running, but v2.25.1 with the fix is already published on npm.