chore: release 1.1.0 #1355
Merged
chore: release 1.1.0 #1355
Conversation
This file contains hidden or 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
In `getGallery` rather check the length of an array to get an accurate bool value than simple the array which will always return true.
this commit was made because if you went to a category and changed to the 2nd page, the currently active category's name would not appear after hard refreshing the page this was happening because activeCategory used route.value.fullPath, which includes the query params. So after the regex pipeline from urlPathToFind, the value passed to findActiveCategory() was "men?page=2" (expected query-param free "men") it was possible to fix this by adding another regex to the pipeline but it's cleaner to just use route.value.path as that's the intention of the implementation M2-1035
before this commit pagination arrows on the category page would be hidden if you hard refreshed the page the culprit was the on-interaction prop on the LazyHydrate component M2-1034
- M2-1036 - added display:block for sf-image-loaded fixes the issue in the Safari browser
ci: add polling farmer for deploy status ci: fix extra parentheses
- lock dependencies on the last working version to avoid upgrade issues
- add images extensions for a proper rendering
- add magento store config load test - add create empty guest cart load test - add magento create customer
our approach to reporting deployment status changed so we no longer need the personal access token workaround. In the past, it was needed because the deploy-template.yml workflow was called by the parent deploy-vue-storefront-cloud workflow, which is prevented by: https://github.com/chrnorm/deployment-action/tree/3afecce166a0a2f92d3a9e7351a9908a72121c24#notes using a personal access token is also not secure since if stolen it could be used to push to the deployment status of every repo I have access to (including vsf org).
bartoszherba
force-pushed
the
release/1.1.0
branch
from
590831e to
75f9608
Compare
bartoszherba
force-pushed
the
release/1.1.0
branch
from
9af72ff to
5777e59
Compare
- exclude */customer*, */checkout* paths from being cached in the CDN
…obile chromium based browsers
|
SonarCloud Quality Gate failed.
|
bartoszherba
approved these changes
Oct 19, 2022
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.
Vue Storefront for Magento 1.1.0 highlights
Vue Storefront for Magento 1.1.0 provides a few new features like SEO-friendly URLs, SEO meta tags, Google Cloud CDN support, and more.
Features
Bugfix
Chore
Docs
Repository