Publishing updates to the Atom package registry is done automatically by GitHub Actions when a release is published. The suggested process is:
- Merge the pull request(s) with changes
- Bump the
package.json
version, update the changelog and create a PR (1 reviewer is fine) - Publish a release on GitHub with a tag matching the version number
If the Deploy workflow fails because you forgot to bump the package.json
version, the tag associated with the release will be automatically deleted and the release will become a draft. Simply bump the package.json
version as appropriate and re-publish the release to trigger the workflow again.
Publishing is done by apm
. See https://flight-manual.atom.io/behind-atom/sections/maintaining-your-packages/. The Atom token of a member of the Cylc organization (gotten from signing in at atom.io) needs to be stored as a repository secret. The token of any member of the organization (with push access) will do.
The Deploy workflow also replaces the symlink grammars/cylc.json
with a hard copy of cylc-textmate-grammar/cylc.tmLanguage.json
in a tag that dangles off master, because apm
doesn't pull submodules - see #3.