Skip to content

Conversation

@kaio-donadelli
Copy link
Contributor

What is the purpose of this pull request?

Previously, version 4.x uses only the human readable version of a state name, while the main branch properly maps the state names (e.g., "Bayern") to 2-digit values (e.g.: "BY").

What problem is this solving?

This was preventing German partner Towa from integrating with us.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires change to documentation, which has been updated accordingly.

@vtex-io-ci-cd
Copy link
Contributor

vtex-io-ci-cd bot commented Sep 3, 2025

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 😞

@jeffersontuc jeffersontuc merged commit d5db5af into 4.x Oct 15, 2025
7 checks passed
@jeffersontuc jeffersontuc deleted the l10n/update-DEU-state-selection branch October 15, 2025 19:10
@vtex-io-ci-cd
Copy link
Contributor

vtex-io-ci-cd bot commented Oct 15, 2025

Your PR has been merged! App is being published. 🚀
Version 4.26.13 → 4.26.14

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 [email protected]

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants