43 lines
2.4 KiB
Markdown
43 lines
2.4 KiB
Markdown
|
# Changelog
|
||
|
|
|
||
|
|
History before 0.1.0 lives in git — cast has said `0.1.0` in `package.json`
|
||
|
|
since its first commit, but grew its release surface (this file,
|
||
|
|
`cast --version`, tagged releases with a prebuilt asset) on the way to
|
||
|
|
actually cutting it, and this file starts there.
|
||
|
|
|
||
|
|
## Unreleased
|
||
|
|
|
||
|
|
### Added
|
||
|
|
|
||
|
|
- **Tagged releases with a prebuilt dist asset, and an installer that
|
||
|
|
installs them** (#96) — the cast half of the flow designed in
|
||
|
|
heavy-duty/box#83, plus the piece unique to cast: a **prebuilt asset**,
|
||
|
|
because cast is the one repo where the source tarball is *not* the
|
||
|
|
package. A release is a PR, then a tag: the `release: X.Y.Z` PR bumps
|
||
|
|
`package.json` (and `package-lock.json`) and stamps this file's Unreleased
|
||
|
|
section with version + date; the merge commit is tagged bare `X.Y.Z`
|
||
|
|
(box's tag scheme — no `v` prefix). `release.yml` turns the tag into the
|
||
|
|
GitHub release — after asserting tag == `package.json` version (a
|
||
|
|
mismatch fails loudly and creates nothing) — with that version's section
|
||
|
|
of this file as the body, extracted by the same
|
||
|
|
`.github/scripts/release-notes.sh` the test harness drives, and with the
|
||
|
|
runnable tree attached as `cast-X.Y.Z.tgz`: `bin/`, compiled `dist/`,
|
||
|
|
production `node_modules/`, `package.json`, built once in CI
|
||
|
|
(`npm ci && npm run build && npm prune --omit=dev`). `install.sh` now
|
||
|
|
defaults to the **latest release**: the tag is resolved by following the
|
||
|
|
`releases/latest` redirect and reading the `Location` header — no API, no
|
||
|
|
token — and the download is that release's asset, so **no `npm ci`, no
|
||
|
|
`tsc`, no devDependencies ever run on the operator's machine**. `CAST_REF`
|
||
|
|
picks the other two channels: a tag pins a release (its asset first,
|
||
|
|
source as the fallback for a ref that has none — `refs/tags` outranks a
|
||
|
|
same-named branch), a branch (`CAST_REF=main`) tracks the development
|
||
|
|
tree and is the one channel that still builds from source, the only place
|
||
|
|
`npm` is required. Until 0.1.0 is cut the default channel has nothing to
|
||
|
|
resolve and dies saying exactly that, naming `CAST_REF=main` as the way
|
||
|
|
to install today — it never falls back to main silently, because "I
|
||
|
|
installed the latest release" must not quietly mean "I installed whatever
|
||
|
|
main was that second". The channel only decides *which* tree arrives and
|
||
|
|
whether it is built here — whatever it fetched lands in the versioned
|
||
|
|
layout (`versions/<package.json version>`, `current` flipped atomically)
|
||
|
|
like any other install.
|