studioraz / magento2-base
Base module for Studio Raz's Magento 2 modules.
Magento 2 module. Base module for Studio Raz's modules.
A base module for ALL Studio Raz modules.
The module lists the installed Studio Raz composer packages (studioraz/*, as recorded by Composer) on the current site
(Stores › Configuration › StudioRaz › Extensions), see screenshot below.
For every package it shows its description, the installed version, the latest released version and its release date,
whether an update is available and a link to its changelog.
Update Check
Latest versions and changelog links are read from the StudioRaz extensions feed:
https://studioraz.github.io/ci-extensions-feed/feed.json (cached for 1 hour, flushed with the config cache).
The check can be disabled under Extensions › Update Check (srbase/update_check/enabled). The feed URL is fixed
(SR\Base\Model\Extension\Feed::FEED_URL). Feed format:
{
"schema": 1,
"packages": {
"studioraz/magento2-base": {
"title": "Base",
"latest_version": "1.10.0",
"released_at": "2026-11-12T00:00:00+00:00",
"changelog_url": "https://github.com/studioraz/magento2-base/blob/1.10.0/CHANGELOG.md"
}
}
}
The package name shown in the list is the feed title. For packages missing from the feed it falls back to
extra.title of the package composer.json, e.g.:
{
"name": "studioraz/magento2-pointofsale",
"extra": {
"title": "Point of Sale"
}
}
Packages missing from the feed (or when the feed is unreachable) are shown with status "Unknown" and no changelog link.
In addition, it adds 2 extra features that should be utilized by dependent modules:
Backend Menu
The module adds a menu item to allow dependent modules add their own links.
When creating new menu item link in etc/adminhtml/menu.xml in order to append it to Studio Raz menu item set parent="SR_Base::srbase"
<config>
<menu>
<add ... parent="SR_Base::srbase" ... />
</menu>
</config>
[image: menu]
System Configuration Tab
The module adds a system configuration tab that other dependent modules can hook to.
When creating a new system configuration section in etc/adminhtml/system.xml in order to append it to Studio Raz tab add <tab>studioraz</tab> to it:
<config>
<system>
<section>
...
<tab>studioraz</tab>
....
</section>
</system>
</config>
[image: extension-list]
Releases
Releases follow the shared Release Please guide.
Use Conventional Commit PR titles (feat: add support, fix: correct behavior).
Squash merges use the PR title and body; single-commit PRs must have a matching commit title.
Pushes to master, the Monday 06:00 UTC schedule and manual runs maintain the release PR and synchronize shared configuration.
Merging a release PR creates a GitHub Release and an unprefixed SemVer tag, and updates the root CHANGELOG.md.
Enrollment preserves existing release history (verified baseline 1.9.0).
The optional RELEASE_TOKEN is forwarded to the shared workflow. Without it, GITHUB_TOKEN is used and bot-created PRs do not trigger PR-title CI. Supply a PAT or GitHub App token when those checks are required.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
1.10.0 (2026-11-12)
Features
Unreleased
1.4.3 - 2022-08-28
Added
- SR logo to sys. conf. menu item
Changed
- Module title in admin menu (
Studio Raz=>StudioRaz)
1.4.1 - 2022-02-08
Fixed
- DateTimeHelper issue, when any operation did not count Timezone, which is passed to DateTime object;
Added
- extra optional param $timezone to each method of DateTimeHelper
1.4.0 - 2022-02-01
Added:
- getTimestamp method DateTimeHelper
- subtractDateInterval method DateTimeHelper
1.3.0
Changed
- Moved const declaration above properties
1.2.0 - 2021-04-16
Implemented
- Helper - to handle DateTime objects
- Exception - common LocalizedException for all SR extensions
1.1.0 - 2021-03-22
Added
- Feature that allows moving a component in the js layout
Changed
- Applied module template
1.0.0 - 2020-12-16
Added
- Project init
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.10.0 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-11-12 20:54:25 |
| 1.9.0 | stable | Pass | Not yet tested Details | 2026-05-07 05:58:10 |
| 1.8.0 | stable | Not tested | Not yet tested Details | 2025-07-06 13:24:25 |
| 1.7.0 | stable | Not tested | Not yet tested Details | 2025-03-16 16:27:06 |
| 1.6.1 | stable | Not tested | Not yet tested Details | 2025-01-15 11:00:04 |
| 1.6.0 | stable | Not tested | Not yet tested Details | 2023-02-22 18:27:44 |
| 1.5.0 | stable | Not tested | Not yet tested Details | 2022-09-04 20:59:05 |
| 1.4.3 | stable | Not tested | Not yet tested Details | 2022-08-28 20:31:05 |
| 1.4.2 | stable | Not tested | Not yet tested Details | 2022-06-10 11:20:33 |
| 1.4.1 | stable | Not tested | Not yet tested Details | 2022-02-08 13:19:20 |
| 1.4.0 | stable | Not tested | Not yet tested Details | 2022-02-01 12:37:24 |
| 1.3.4 | stable | Not tested | Not yet tested Details | 2022-01-31 18:56:48 |
| 1.3.3 | stable | Not tested | Not yet tested Details | 2022-01-18 18:00:20 |
| 1.3.2 | stable | Not tested | Not yet tested Details | 2021-10-31 21:21:22 |
| 1.3.1 | stable | Not tested | Not yet tested Details | 2021-10-31 21:09:44 |
| 1.3.0 | stable | Not tested | Not yet tested Details | 2021-10-29 20:10:25 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2021-04-16 11:42:33 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2021-03-21 23:10:23 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2020-12-16 21:19:45 |
Requires 2
| Package | Constraint |
|---|---|
| composer-runtime-api | ^2.0 |
| magento/framework | * |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Warning | 18 | 18 warnings (ruleset: Magento2), 1 auto-fixable with phpcbf |
| PHPMD | Warning | 12 | 12 rule violations (MissingImport:9, UnusedFormalParameter:2, UnusedPrivateMethod:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.