-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore: next version release #1536
Open
github-actions
wants to merge
1
commit into
main
Choose a base branch
from
changeset-release/main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
December 19, 2024 11:04
7a8e6d2
to
9513c1b
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
December 19, 2024 19:31
9513c1b
to
5e0c6a4
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
December 20, 2024 11:52
5e0c6a4
to
3a91826
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
December 20, 2024 13:45
3a91826
to
13286df
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
December 23, 2024 13:42
13286df
to
2dab45e
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
December 31, 2024 12:03
20ff56f
to
c277bc8
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
January 2, 2025 09:13
03e8bdb
to
4634cdc
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 2, 2025 09:16
4634cdc
to
856fce1
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 3, 2025 10:33
856fce1
to
bcf43c6
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 3, 2025 10:48
bcf43c6
to
8690472
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 3, 2025 12:31
8690472
to
ba6ba87
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 7, 2025 08:29
ba6ba87
to
75d2817
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 7, 2025 08:55
75d2817
to
98e58ee
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 13, 2025 09:44
98e58ee
to
e736b74
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 13, 2025 10:15
e736b74
to
25550f5
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 13, 2025 10:40
25550f5
to
e9191eb
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
None yet
0 participants
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@shopware-pwa/composables-next@1.6.0
Minor Changes
3778061
Thanks @kasztof! - Allow to pass full seach criteria according to loadNavigationElements method of useNavigation composablePatch Changes
#1564
3d2f2b5
Thanks @mdanilowicz! - Return the last element for the payment and shipping methods inuseOrderDetails
. The reason for this change is that the backend returns collections sorted by the entry date#1550
63d56b3
Thanks @mdanilowicz! - useCustomerOrders - Set current page based on the orders endpoint response@shopware-pwa/cms-base@1.2.1
Patch Changes
#1535
289ff97
Thanks @mkucmus! - Display "from price" label correctly for Product price component.Updated dependencies [
3d2f2b5
,3778061
,63d56b3
]:@shopware-pwa/nuxt3-module@1.1.1
Patch Changes
3d2f2b5
,3778061
,63d56b3
]:vue-demo-store@1.5.0
Minor Changes
63d56b3
Thanks @mdanilowicz! - Removed order details fromAccountOrder
component and moved it to the new order details pagepages/account/order/details/[id].vue
docs@1.8.1
Patch Changes
3d2f2b5
,3778061
,63d56b3
]: