-
Notifications
You must be signed in to change notification settings - Fork 4
Publishing
Daniel Coelho edited this page Apr 27, 2022
·
6 revisions
Note: This section is only for Utrust team members or external collaborators with permissions.
We should aim to always publish the release in Magento Marketplace and GitHub repository.
Therefore, to release a new version of the current code on the master
branch, you'll need to follow these steps:
- Checkout from master to a branch with the version name (e.g.:
release-v0.1.3
) - Update the version on
etc/module.xml
line 3 - Update the version on
composer.json
line 4 - Update
CHANGELOG.md
with all the significant changes since the last version update - Open Pull-request, ask for approval and merge to
master
(Don't delete the branch!) - Download and Zip the codebase with the name
utrust-for-magento-2_v<version-number>.zip
- Go to "Releases" and create a new Release:
- The tag version and release title should be the release version (e.g.
release-v0.1.2
) - The target branch is the one created in step 1.
- Copy the version changes from the
CHANGELOG.md
- Upload the new
utrust-for-magento-2_v<version-number>.zip
to the attachments - Click
Publish release
- The tag version and release title should be the release version (e.g.
- Optionally, send a message to the Utrust Support team to communicate this new release to Merchants which use Magento.
- Go to Magento Developer and sign-in.
- Select the
Utrust Payments
extension for Magento 2. - Click on
Submit a New Version
. - Input the new release version and proceed.
- Grab the zip from the GitHub release, unzip it, open folders
Utrust
andPayment
, zip again (we need the root of the zip to have the composer.json file). - Submit this new zip for technical review and submit it.
- After review, it might take a few days, it should be automatically shown on the Marketplace.