Tagging releases

Would it be possible for you to use the Git repo at https://github.com/vippsas/vipps-woocommerce ? That does have all prior releases (and future ones).

I’m not sure about the composer-based project issue you mention, could you elaborate?

For downloading older releases, yes, github would be possible. But it wouldnt solve the composer issue.

To elaborate:
Lets Say you have an old composer-based project laying around. WooCommerce is version 3.9.0 and vipps is something similarly old, lets Say 1.0.0. The composer.json has WooCommerce version locked to 3.9.0 and vipps plugin locked to 1.0.0

However, the reference to 1.0.0 source in composer.lock is not referencing a tagged release, its referencing trunk, since tags are missing.

If we (or other companies having similar workflow) make a single change in the repo of that project, that would trigger a composer install during deployment, which will download vipps as is from trunk. Without you knowing it, vipps is now at a potential 2 year newer version, while WooCommerce is still 2 year old. Something is bound to break at some point.

We don’t really want to encourage running older versions like that – for instance, this february Vipps retired their previous-version api for the login service, making older versions of that plugin nonfunctional in any case. If you for some reason *have* to freeze the plugin to an outdated version, it seems to me that it should be possible to do so using the Git repo (just don’t use composer to download the trunk). It may still stop working because of API changes of course.

We do try, within reason, to support older versions of WooCommerce for the trunk version which ought to make this less of an issue too.

I’m not you however, so maybe there is some usecase here I’m not seeing. We can start adding tags going forward; but keep in mind we can’t really support older version nor guarantee that breaking changes in the API won’t happen.

Agreed, this was just an example. Thank you for planning to tag going forward.