Adds CI/CD workflows - #1
Merged
Merged
Conversation
lissy93
pushed a commit
that referenced
this pull request
Jul 4, 2026
fix: allow proceeding even when offline check fails/wrong
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI
Whenever a PR is opened, will run tests and other checks.
Uses a files-changed matrix, to only run the checks needed based on what changed.
Docker
Builds and published the Docker image to GHRC (and optionally DockerHub if credentials specified). Does a multi-arch build in parallel (amd64, arm64, armv7), and attests both the build prevenance and SBOM for GHCR.
Triggered by:
Tag
Whenever a PR gets merged, will update the version in package.json (unless PR already did that), then create and publish a new git tag for that.
Release
Creates a new GitHub release, with changelog for a given tag, and builds and attaches the compiled app as well as SHA256 and SLSA build-prevenance attestion to the release.
This is what non-Docker self-hosters will use to run the app without needing to setup NPM and build themselves.
Publish
I've left this blank for now. I started drafting how it should go, but I'll leave it to you to complete that :)
Mirror
Delete if you don't want this, but it can be useful to not be locked-in to GitHub, and to have a backup of your repo. It just mirrors it to an alternate git forge.