Adds a workflow that, on every push to master, will publish new versions
of interface subpackages to the NPM registry if any are available.
Staged to trigger on a test branch for now.
Adds a 'merge-release' workflow that runs on any push to a release
branch. At present the only job merges the triggering branch to
'ops-tlon'.
Also renames the 'merge' workflow to 'merge-master' to distinguish it
appropriately.
Hosted container services such as Azure Container Images are broken
by the absence of metadata in images pushed by Skopeo. Using Docker we
can push and ensure all metadata is in place.
Tested on: GitHub Actions for black-river-software/urbit fork.
When pushing the docker image, update the "latest" tag as well as
pushing a tag for the current Urbit version. This way users pulling
tloncorp/urbit:latest will always get an image with the latest point
release of Urbit.
d3c5aa74c1 introduced a Docker image intended for deploying Urbit ships
This commit modifies the build.yml GitHub Actions workflow to build the
docker image as part of the push/PR workflow, and adds a
`release-docker.yml` workflow, which runs on any tag push `urbit-v*` and
pushes the image to Docker Hub, also synchronizing the README.
Co-authored-by: Josh Lehman <josh@urbit.org>
Sets two environment variables, LANDSCAPE_STREAM and
LANDSCAPE_SHORTHASH, to be employed by landscape builds. Also reverts
the janeway version used to v0.13.1 as the --dev flag is unnecessary.
Some other commits have been squashed in:
meta: remove user declarations for glob action
This is a tricky problem. SSH needs UID 0 to exist, and intuitively it
does (root), but we can't enforce that when GitHub is running our
container. Specifying "USER 0:0" in the actions Dockerfile doesn't cut
it.
Instead it seems best to try and construct a shadow-utils setup on the
underlying Docker image.
meta: target glob workflow at release/next-js
Adds a workflow that executes the 'glob' action on every push and pull
request to the 'release/next-js' branch.
(For now this is just staged to the 'jt/lacd' branch for testing.)
This action, when supplied with the appropriate arguments, will create a
Landscape glob from GITHUB_SHA [1] and deploy it OTA to the appropriate
ship.
It needs to be supplied the following:
* ship name
* base64-encoded GCP Service Account credentials
* a base64-encoded SSH secret key to be used for GCP actions
* the corresponding base64-encoded SSH public key
[1]: https://docs.github.com/en/free-pro-team@latest/actions/reference/environment-variables
