Commit Graph

15 Commits

Author SHA1 Message Date
Damien Retzinger a7e327d44f feat(supported-version): dynamically append "version" to matrix 2026-05-07 09:30:09 -04:00
Damien Retzinger 34ddee6aef fix: using latest accidentally output two versions for Magento Open Source 2026-02-19 10:31:12 -05:00
Ryan Hoerr 5608271fe3 fix: allow matrix testing without EOL versions (#299)
* fix: remove versions dependent on EOL composer 1

* Restore composer 1 versions

* Add `usable` version type, filtered by code constraints

* Added code comment

* Rebuilt index.js with latest changes merged

* Updated documentation
2025-12-15 11:22:34 -05:00
Damien Retzinger 9c1dbc7d07 feat(supported-version): add optional services output for each matrix entry (#206) 2025-12-15 10:13:50 -05:00
Ryan Hoerr ab5dc9fc95 Fix opensearch versions based on container support (#289)
* Fix opensearch versions based on wardenenv container support

* opensearchproject/opensearch:2.19.1

* Disable opensearch security

* spawn separate opensearch service when needed

* fix opensearch flags; fix PackageMatrixVersion type and test

* Try mysql:8.4 over mariadb:11.4

* updated dist/index.js

* Allow trigger creation during integration tests
2025-12-14 17:47:56 -05:00
Damien Retzinger 2f1b2eaa5d feat(supported-version): add recent kind (#188) 2025-04-09 09:51:01 -04:00
Vinai Kopp 2086708ffc feat: add releases 2.4.4-p6, 2.4.5-p5 and 2.4.6-p3 (#169) 2023-10-11 06:25:00 +13:00
Vinai Kopp b645c2327d fix: pass correct repo url for nightly (#158)
fix: pass correct repo url for nightly

The amendMatrixForNext function uses the repository argument to
determine the version constraint for the returned matrix for kind
nightly.
Previously, the upstream-mirror repo url was passed as an argument, but
the nightly builds use a different repo url.
This resulted in failed builds, because the version string 'next' could
not be parsed by composer.

Example:
https://github.com/mage-os/generate-mirror-repo-js/actions/runs/6370219504/job/17291152703

With this change, the nightly kind will always return the @alpha
version constraint, that is, stability constraint.
There currently is no way to distinguish between different nightly
repos, but since both work the same way, this is fine (for now).
2023-10-02 06:27:52 +13:00
Damien Retzinger 7f1821f6ac fix(supported-versions): nightly build matrix tag (#152) 2023-09-24 16:07:37 -04:00
Vinai Kopp f7f0504691 feat: add project versions (#110)
* refactor: allow version matrixes by projects

* feat: add initial version-matrix for mage-os

* feat: add project as optional input to action

* docs: document new input

* refactor: tighten types a bit

* chore: apply change requests from code review
2023-09-06 22:08:57 +02:00
Damien Retzinger 5599a0d2e7 feat(supported-versions): add release date (#100)
Previously, we didn't take into account a release date, which meant
that @vinai could not add MageOS or Magento releases before the actual
day of release.

With this, we can now add the releases to supported verisons before
a release comes out, allowing us to make a kind that allows testing
MageOS and Magento Mirror releases more quickly.
2023-08-16 13:57:48 +02:00
Damien Retzinger dbc889f7ce feat(supported-version): dynamically compute (#120)
Previously, I maintained supported versions by revising a file of versions. This was monotonous, like time.

Now, these are just based upon the documented EoL dates of the versions published by Magento.
2023-01-09 13:09:24 -05:00
Damien Retzinger 7431dcb7af feat: allow using "next" version on supported version (#58)
This also allows using the action in https://github.com/mage-os/generate-mirror-repo-js where the test module is an external package installed with composer. In this case, no local path repo configuration is needed.

Co-authored-by: Vinai Kopp <Vinai@users.noreply.github.com>
2022-10-11 16:19:49 -04:00
Damien Retzinger 26c354d8d4 feat(supported-version): add all kind (#36) 2022-08-12 08:40:31 -04:00
Damien Retzinger 664360ede2 feat(supported-version): add user-defined kind (#28)
`kind` is a new input property for the `supported-version` action which
allows one to define what specific versions of Magento they support.

Currently, `kind` supports `latest`, `currently-supported`, and `custom`. See the
README for `supported-version` if you want more specifics
2022-08-05 17:36:38 -04:00