Publishing a New Version

Only Adobe employees are eligible to publish new extension versions.

1. Fork https://git.corp.adobe.com/AdobeDocs/experience-platform.en if you haven't already, add release notes to help/edge/release-notes.md (usually determined by looking through merged pull requests and commits), then create a pull request against the main fork.
2. Open the Alloy extension repository (the one you're looking at now) locally.
3. Make sure you're on the main branch and have pulled the latest changes.
4. Run npm ci to ensure you have the latest dependencies.
5. Version and tag Alloy by running npm version major/minor/patch. Whether you use major, minor, or patch depends on what has changed since the last release and how that matches semantic versioning.
6. Running npm version major/minor/patch should have changed package.json and package-lock.json, committed the changes, and created a new git tag. Push these changes to Github by running git push origin main --follow-tags --no-verify. Go to Github and ensure you see the newly added commit and tag.
7. See https://github.com/adobe/alloy/wiki/Publishing-a-New-Release to publish a new Github release.
8. Obtain Akamai NetStorage Upload capabilities by sending a request to Jeffrey Walter or Joel Stachowicz and include your public RSA key. This is normally found in ~/.ssh/id_rsa.pub. If you don't have a key, you'll need to generate one by running ssh-keygen -t rsa -b 2048 -C "[email protected]".
9. Ensure release notes have been merged and published before continuing to the next step.
10. With an SFTP client like Filezilla or the sftp terminal command, we will connect by using dxresources.ssh.upload.akamai.com as the host, sshacs as the user, and then your private key file.
11. Once connected, navigate to the /prod/alloy directory, create a new directory with a name corresponding to the version being published (e.g., 2.3.0), then uploading the built alloy.js and alloy.min.js files to the new directory.
12. Navigate to the /prod/alloy/latest directory and upload the built alloy.js and alloy.min.js files to that directory as well.

Congratulations! You've published a new version. Now, be sure to release a new version of the Launch extension.