Skip to content

Feat/change shipping options comopnents to delivery promise components#633

Open
hiagolcm wants to merge 3 commits intomasterfrom
feat/change-shipping-options-comopnents-to-delivery-promise-components
Open

Feat/change shipping options comopnents to delivery promise components#633
hiagolcm wants to merge 3 commits intomasterfrom
feat/change-shipping-options-comopnents-to-delivery-promise-components

Conversation

@hiagolcm
Copy link
Copy Markdown
Contributor

@hiagolcm hiagolcm commented Apr 6, 2026

What problem is this solving?

  • Replace vtex.shipping-option-components by vtex.delivery-promise-components
  • StoreWrapper now uses DeliveryPromiseProvider from vtex.delivery-promise-components/DeliveryPromiseContext (replacing ShippingOptionProvider / ShippingOptionContext).

How to test it?

Workspace

Screenshots or example usage:

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? 🔗

![](put .gif link here - can be found under "advanced" on giphy)

Replace ShippingOptionProvider import with DeliveryPromiseProvider from
vtex.delivery-promise-components/DeliveryPromiseContext. Document in CHANGELOG.

Made-with: Cursor
@vtex-io-docs-bot
Copy link
Copy Markdown

vtex-io-docs-bot bot commented Apr 6, 2026

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

@hiagolcm hiagolcm requested a review from a team as a code owner April 6, 2026 00:12
@hiagolcm hiagolcm requested review from gabpaladino, leo-prange-vtex and vmourac-vtex and removed request for a team April 6, 2026 00:12
@vtex-io-ci-cd
Copy link
Copy Markdown
Contributor

vtex-io-ci-cd bot commented Apr 6, 2026

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@hiagolcm hiagolcm requested a review from iago1501 April 6, 2026 00:12
"vtex.native-types": "0.x",
"vtex.telemarketing": "2.x",
"vtex.shipping-option-components": "1.x"
"vtex.delivery-promise-components": "0.x"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is 0.x the definitive major version for now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants