| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* make a half-baked tarball
Closes #217
Signed-off-by: Xe Iaso <me@xeiaso.net>
* make two tarballs: one with just the vendor, and one with vendor and npm
Signed-off-by: Xe Iaso <me@xeiaso.net>
---------
Signed-off-by: Xe Iaso <me@xeiaso.net>
|
|
* implement packaging proof of concept with yeet
Signed-off-by: Xe Iaso <me@xeiaso.net>
* docs/developer: add local dev docs for yeet
Signed-off-by: Xe Iaso <me@xeiaso.net>
* apply review feedback
Signed-off-by: Xe Iaso <me@xeiaso.net>
* build package artifacts in CI
Signed-off-by: Xe Iaso <me@xeiaso.net>
* tell CI to fetch all git metadata
Signed-off-by: Xe Iaso <me@xeiaso.net>
* rename package builds job
Signed-off-by: Xe Iaso <me@xeiaso.net>
* upload each package individually
Signed-off-by: Xe Iaso <me@xeiaso.net>
* split package build CI jobs
Signed-off-by: Xe Iaso <me@xeiaso.net>
* fix code injection?
Signed-off-by: Xe Iaso <me@xeiaso.net>
* fix ci?
Signed-off-by: Xe Iaso <me@xeiaso.net>
* fix security alert
Signed-off-by: Xe Iaso <me@xeiaso.net>
* docs/local-dev: point people to yeet v1.13.3
Signed-off-by: Xe Iaso <me@xeiaso.net>
---------
Signed-off-by: Xe Iaso <me@xeiaso.net>
|
|
Signed-off-by: Xe Iaso <me@xeiaso.net>
|
|
Closes #125
Closes #40
Among other things, this moves all of the asset generation to run within
the context of an npm script. Developer documentation stubs have been
added so that people can get started more easily.
The top-level Dockerfile (which is no longer used in production) has
been removed as its presence has been causing confusion. This changeset
will break it anyways.
These changes will make for less "repo churn" as the static assets are
built and rebuilt, at the cost of making the build step more complicated
for downstream packagers. If this becomes a burden, we can explore
making a "release tarball" that contains pre-massaged outputs.
|
|
Signed-off-by: Xe Iaso <me@xeiaso.net>
|
|
Signed-off-by: Xe Iaso <me@xeiaso.net>
|
