Closed glo82145 closed 1 year ago
Fails | |
---|---|
:no_entry_sign: | A version label is required. A maintainer must add one. |
Messages | |
---|---|
:book: | Associated JIRA tickets: [PWA-3047](https://jira.corp.magento.com/browse/PWA-3047). |
:book: | DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed). |
:book: | Access a deployed version of this PR [here](https://pr-4118.pwa-venia.com/). Make sure to wait for the "pwa-pull-request-deploy" job to complete. |
Generated by :no_entry_sign: dangerJS against e412420004790c69e2f3af0d92c7a2ab110d47ba
run lighthouse-desktop
Successfully started codebuild job for lighthouse-desktop
run lighthouse-mobile
Successfully started codebuild job for lighthouse-mobile
Description
Describe the bug
Using the create PWA scaffolding tool appears to use an old version. This appears it is related to issue #4009 that was closed without resolution.
To reproduce
Steps to reproduce the behavior:
Run the yarn create @magento/pwa or npx @magento/create-pwa command Note that during the questionnaire portion the prompt only includes mention of Magento 2.3.3 and 2.4-develop
I would expect to not see a reference to }}2.4-develop{{ in the questionnaire, }}2.3{{ in the }}.env{{ file, and the generated 2.4 }}MAGENTO_BACKEND_URL{{ should work.
Related Issue
Closes PWA-3047
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist