Skip to content

update changelog to generate version#15

Merged
nicholas-maestrello merged 2 commits intomasterfrom
B2BTEAM-3227
Mar 6, 2026
Merged

update changelog to generate version#15
nicholas-maestrello merged 2 commits intomasterfrom
B2BTEAM-3227

Conversation

@nicholas-maestrello
Copy link
Contributor

What does this PR do?

update changelog to generate version

@nicholas-maestrello nicholas-maestrello self-assigned this Mar 4, 2026
@vtex-io-ci-cd
Copy link

vtex-io-ci-cd bot commented Mar 4, 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 😞

@vtex-io-docs-bot
Copy link

vtex-io-docs-bot bot commented Mar 4, 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 🎉🎉

@nicholas-maestrello nicholas-maestrello merged commit 5ec4713 into master Mar 6, 2026
5 checks passed
@vtex-io-ci-cd
Copy link

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

Your PR has been merged! App is being published. 🚀
Version 1.3.1 → 1.3.2

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.sku-list@1.3.2

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

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