14.2.0 alpha Test PR #4410
Closed
14.2.0 alpha Test PR #4410
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Removing gomage plugin * Removing gomage plugin * Update package.json
* PWA remove gomage package * PWA remove gomage package
* New Commit to Create NEW PR with Latest Develop * Fixing Prettier Issues * Adding workflow file to publish package * Updating Namespace to @adobe * Fixing Prettier Issues * Adding module to venia-concept/package.json * PWA Gomage * Adding Alpha versions * Removing Adobe Braintree Plugin from Package.json --------- Co-authored-by: Aanchal Pawar <[email protected]> Co-authored-by: glo82145 <[email protected]>
* Update package.json * Update package.json
glo42707
added
the
needs-triage
glo42707
added
the
version: Patch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
test PR for alpha testing created by arpit
Related Issue
Closes #PWA-3415.
Acceptance
only test PR
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