promptfoo 0.62

[pelikhan]

• support for evalid and linking to individual reports

CLI Changes

• 🆙 Updated the default promptfoo version in the CLI commands documentation from ^0.61.0 to ^0.62.0.

Library Changes

• 🆙 Bumped the promptfoo dependency version from ^0.61.0 to ^0.62.0 in package.json.
• 🆙 Upgraded the openai dependency version from ^4.48.1 to ^4.48.3 in both cli and core package.json files.
• 🔄 Modified the PromptScriptTestResult interface in messages.ts to include an evalId string in the value property.
• ✨ Added EMOJI_FAIL and EMOJI_SUCCESS constants in testcontroller.ts.
• 🛠 Refactored the activateTestController function in testcontroller.ts to use the new serverUrl and append output with emojis and error messages.
• 🛠 Changed the startTestViewer function in testcontroller.ts to return serverUrl and updated the terminal command to include --yes flag.

generated by genaiscript pr-describe

[github-actions[bot]]

Concerns:

1. 🚨 The value property in the PromptScriptTestResult interface has been changed to an object with an evalId property. This change assumes that all responses will have an evalId, which may not be the case for all test results. It could lead to runtime errors if the evalId is not provided in the response.

2. 🚨 In the startTestViewer function, the openUrlInTab function call is commented out. This means that the test viewer URL will not automatically open in a new tab, which could be a regression in user experience.

3. 🧐 The startTestViewer function now returns serverUrl, but the function's return type is not specified. It's a good practice to explicitly define the return type for clarity and maintainability.

4. 🧐 The npx command in the startTestViewer function includes a --yes flag that was not present before. This change should be reviewed to ensure it aligns with the intended behavior and security practices, as it could automatically agree to prompts without user confirmation.

Suggested code fixes:

• Ensure that the value property in PromptScriptTestResult can handle cases where evalId might not be present.
• Consider uncommenting or handling the openUrlInTab function to maintain the previous functionality.
• Define the return type for the startTestViewer function.
• Review the addition of the --yes flag in the npx command to ensure it's necessary and secure.

generated by genaiscript pr-review