Update zip_codes.xml

[marcostrama]

Changed regex for zipcodes from Brazil. All zipcode must have 8 positions, with or without dash

Description (*)

Changed the regex to force 8 digits for zipcode in Brazil

Related Pull Requests

n/a

Fixed Issues (if relevant)

Didn't found issue but a lot of people asking for help in foruns

Manual testing scenarios (*)

Format of zipcodes in Brazil: 99999-999 or 99999999

1. Put any number less than 8 digits (ex: 01001) - ERROR
2. Put a number with 8 digits, without dash (ex: 01001-001) - OK
3. Put a number with 5 digits, a dash and more 3 digits (ex: 01001-001) - OK

Questions or comments

First contribution to Magento, please let me know if I need to provide more info

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• [N/A] All new or changed code is covered with unit/integration tests (if applicable)
• [N/A] All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Update zip_codes.xml #29984: Update zip_codes.xml

[m2-assistant]

Hi @marcostrama. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sidolov]

Hi @marcostrama , please, sign Adobe CLA, otherwise, we can't process your pull request

[sidolov]

@magento create issue

[marcostrama]

@sidolov just signed, thanks

[sidolov]

@magento run all tests

[sidolov]

@marcostrama please, take a look a failed integration test, it's related to the changes

[marcostrama]

@magento run all tests

[marcostrama]

Hi @sidolov can you give a help here? Functional tests failed with a message:

SUITE PRECONDITION FAILED:
Waited for 60 secs but text 'auth[code=' still not found

Appears to not be related with my changes, maybe some authentication failed for the test. I'm new at this project and I don't now how to proceed. thanks

[sidolov]

Hi @marcostrama , failures did not cause by your changes, looks like the problem with ASI tests. There is no action required from your side!

[magento-engcom-team]

Hi @sidolov, thank you for the review.
ENGCOM-8220 has been created to process this Pull Request
✳️ @sidolov, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[magento-engcom-team]

@marcostrama thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

[engcom-Alfa]

✔️ QA Passed

Put any number less than 8 digits

Before: ❌ Format of zipcodes in Brazil: 99999-999 or 99999

After: ✔️ Format of zipcodes in Brazil: 99999-999 or 99999999

[engcom-Alfa]

@magento run all tests

[m2-assistant]

Hi @marcostrama, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.