Using GitHub Releases for mas.js distribution

[yesil]

As part of the M@Sv2 initiative, our Creative Cloud Desktop (CCD) partners will consume commerce, merch cards, and related features via a single mas.js file. After several rounds of discussion, we've determined that an evergreen distribution is not feasible. Instead, the Warriors team will provide regular releases of mas.js.

We've agreed to use GitHub's releases section for distribution. Initially, we'll build and upload the package manually, with details such as package naming and version scheme to be determined. Following initial feedback, we plan to automate this process.

Given that MAS is now on Milo, we propose using the GitHub releases section of the Milo repository for this purpose. Each release will result in the creation of a permanent MAS tag in the repository.

I'd like to open a discussion with the team regarding the pros and cons of using the Milo repository for this distribution method. Your thoughts and feedback on this approach, as well as on package naming and versioning, would be valuable as we move forward with implementation.

[mokimo]

+1 on automating the releases & I'd suggest to do it earlier than later, otherwise it'll just get forgotten.

I don't see any huge blockers or issues using Github releases. One thing to consider is that as per usual things don't go to main instantly and need some time and preparation. Just something to consider as part of the release and distribution strategy, but this is already existant.

Another use-case to consider is other features living within milo also doing Github releases in the future.

[yesil]

I think Github releases is fine to host many different releases from the same mono repository.
Can you enable this feature on Milo for contributor?
Automation will be done but we still need to discuss about the frequency and versioning convention.
However CCD team needs is waiting for the first release to validate the integration, hence manual release.

[mokimo]

Anyone with write access to the repository can create releases. No need for any special setup on top of it!
See: https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository

Repository collaborators and people with write access to a repository can create, edit, and delete a release.

[yesil]

Thanks @mokimo

I published the very first mas.js(named mas-js) pre-release at https://github.com/adobecom/milo/releases/tag/mas-js-v0.0.1

To install it via npm:
npm add https://github.com/adobecom/milo/releases/download/mas-js-v0.0.1/adobecom-mas-js-0.0.1.tgz