Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct VAT and postal code for Campione d'Italia #138

Merged
merged 1 commit into from
Jan 11, 2022

Conversation

spaze
Copy link
Contributor

@spaze spaze commented Jan 11, 2022

After checking the changes in #137 I've noticed that Campione d'Italia became part of the EU customs territory on 1 Jan 2020.

That means two relevant changes:

Until 2020, mail could be sent to Campione using either a Swiss postal code (CH-6911) or an Italian one (I-22061) via Switzerland or Italy, but the Swiss postal code ceased to be valid, with mail instead being charged at the same international rate as that between Switzerland and Italy.
https://en.wikipedia.org/w/index.php?title=Campione_d%27Italia&diff=prev&oldid=957716786

…n 2020

Campione d’Italia formally became part of the EU customs territory on 1 January 2020. VAT will apply, but the tax rate will remain that of Switzerland. Also, the Swiss postal code ceased to be valid.
@driesvints
Copy link
Owner

Thank you @spaze

@driesvints driesvints merged commit cf71081 into driesvints:main Jan 11, 2022
@spaze spaze deleted the patch-1 branch July 26, 2022 00:33
@driesvints
Copy link
Owner

@spaze just noticed this PR. This was sent to main but probably should go to 3.x?

@spaze
Copy link
Contributor Author

spaze commented Jan 1, 2024

@driesvints Possibly, yeah. Can't remember why it's for main though 😇

@driesvints
Copy link
Owner

@spaze ok, feel free to send it to 3.x if you feel it should go in the current release 👍

@spaze
Copy link
Contributor Author

spaze commented Jan 1, 2024

@driesvints Wanted to create a new PR as this one's been merged already but my fork has diverged way too much already and I'm a bit lost in how to file a new PR against your 3.x branch. Do you think you could try merging main into 3.x? I see there are just a few commits besides this one so it shouldn't create many conflicts. If that doesn't work I'll try to think about something 😅 Thanks!

@driesvints
Copy link
Owner

@spaze I'll give it a go soon!

@spaze
Copy link
Contributor Author

spaze commented Jan 3, 2024

Hey @driesvints, I've learned a new trick or two how to sync my fork (had to first switch to the 3.x branch of my fork and then hit the GitHub "Sync fork" button, previously tried that on master which didn't work) and have created #168 by just reapplying the 138.patch to the 3.x branch.

@driesvints
Copy link
Owner

Cool thanks!

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