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

payment.xml validation #574

Closed
c-walter opened this issue Dec 2, 2024 · 6 comments
Closed

payment.xml validation #574

c-walter opened this issue Dec 2, 2024 · 6 comments

Comments

@c-walter
Copy link

c-walter commented Dec 2, 2024

Hey, please check

</method>v
for latest versions. There is a "v" in the xml which is there by mistake.

@Morgy93
Copy link
Contributor

Morgy93 commented Dec 3, 2024

Fixed via #572

Please release ASAP 🙏

@JasiukiewiczM
Copy link

Fixed 3 weeks ago and still waiting for release? Why is that?

@janteuber
Copy link
Contributor

We won't do a separate release for such a small change. This adjustment will be included in the next release.

@Morgy93
Copy link
Contributor

Morgy93 commented Dec 6, 2024

We won't do a separate release for such a small change. This adjustment will be included in the next release.

Could you consider releasing a patch version? That’s exactly what they’re meant for.
A 3.13.2 release would be ideal.
Since 3.13.1 is currently broken, it would greatly benefit all users to have a fixed version available as soon as possible.

@janteuber
Copy link
Contributor

Hi everyone,

I've fixed the issue from GitHub and released a new plugin version. Check it out here: v3.13.2 Release.

Thanks for your patience!

Best,
Jan

@Morgy93
Copy link
Contributor

Morgy93 commented Dec 9, 2024

Hi everyone,

I've fixed the issue from GitHub and released a new plugin version. Check it out here: v3.13.2 Release.

Thanks for your patience!

Best, Jan

Thank you for your efforts!

I now understand why you hesitated to create a patch release—it seems the project doesn’t strictly adhere to semantic versioning (semver). Please don’t take this as criticism; it’s just feedback that I believe is important for users of this module to be aware of.

In version 3.13.2, new features were introduced compared to 3.13.1, which technically goes against the guidelines of semver. This isn’t a problem in itself, but it’s something users should know beforehand when including this module.

Just as a quick reminder, under semantic versioning:

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes
  2. MINOR version when you add functionality in a backward compatible manner
  3. PATCH version when you make backward compatible bug fixes

https://semver.org/

Thanks again for your work!

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

No branches or pull requests

4 participants