aivee 0.1.0-dev.7025438 → 0.1.0-dev.d34a6ba

package/README.md

@@ -64,10 +64,10 @@ aivee doctor
 
 The CLI command is `aivee`. The release workflow publishes the unscoped npm
 package `aivee` and the owner-scoped GitHub Packages package
-`@warengonzaga/aivee`. Neither package has been published yet. The first release
-requires a repository `NPM_TOKEN` with npm publish access and GitHub Actions
-package-write permission.
-See the [release guide](docs/releasing.md) for the one-time setup.
+`@warengonzaga/aivee`. npm publishing uses trusted publishing through GitHub
+Actions OIDC, so no `NPM_TOKEN` secret is needed. Package artifacts are also
+published for pull requests, `dev` pushes, and manual workflow runs. See the
+[release guide](docs/releasing.md) for the one-time setup.
 
 ## 📖 Usage
 
@@ -90,9 +90,11 @@ npm run test:render-smoke
 npm audit --omit=dev
 ```
 
-GitHub Actions are manual-trigger only. Use the platform selector for Linux,
-Windows, macOS, or the full matrix. A native macOS run is still required before
-claiming Mac support.
+Build Flow runs on pull requests targeting `dev` or `main`, pushes to `dev` or
+`main`, and manual dispatch. Its package artifacts publish on pull requests,
+`dev` pushes, and manual runs. The separate platform-validation workflow is
+manual-trigger only; use its selector for Linux, Windows, macOS, or the full
+matrix. A native macOS run is still required before claiming Mac support.
 
 ## 🤝 Contributing
 

package/docs/releasing.md

@@ -1,18 +1,18 @@
 # Releasing AIVEE
 
-The `Build Flow` workflow validates pull requests targeting `dev` or `main`.
-Merging the release pull request to `main` publishes `aivee` to npm and
-`@warengonzaga/aivee` to GitHub Packages, then creates a GitHub Release after
-both registries report success. Development, pull-request, and manual runs do
-not publish packages.
+The `Build Flow` workflow validates pull requests targeting `dev` or `main` and
+publishes package artifacts on pull requests, pushes to `dev`, and manual runs.
+These preview artifacts go to npm and GitHub Packages. A push to `main` after
+merging a release PR publishes the release versions and creates a GitHub Release
+after both registries report success. Container publishing is disabled.
 
 ## One-time setup
 
-1. Add an npm automation token with publish access as the repository secret
-   `NPM_TOKEN`. The workflow uses it to create the initial npm package and to
-   publish later versions.
-2. Enable GitHub Actions package write access for the repository. The workflow
-   uses `GITHUB_TOKEN` to publish the GitHub Packages copy.
+1. Configure npm trusted publishing for this GitHub repository and the
+   `build-flow.yml` workflow. The workflow uses OIDC; no `NPM_TOKEN` secret is
+   required.
+2. Allow GitHub Actions to write packages. The workflow uses `GITHUB_TOKEN` to
+   publish the GitHub Packages copy.
 
 After setup, release promotion from `dev` to `main` runs the version, package,
 and GitHub Release flow. Check both registries after the first automated release;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aivee",
-  "version": "0.1.0-dev.7025438",
+  "version": "0.1.0-dev.d34a6ba",
   "license": "MIT",
   "author": "Waren Gonzaga",
   "repository": {

package/src/timeline/caption-layouts.mjs

@@ -46,6 +46,7 @@ export const CAPTION_LAYOUT_PRESETS = Object.freeze(Object.fromEntries(
     ...layout,
     ...(layout.textOutline ? { textOutline: Object.freeze({ ...layout.textOutline }) } : {}),
     ...(layout.textShadow ? { textShadow: Object.freeze({ ...layout.textShadow }) } : {}),
+    ...(layout.bubble ? { bubble: Object.freeze({ ...layout.bubble }) } : {}),
   })]),
 ));