Skip to content

v1.15.1

Choose a tag to compare

@CodeBoy2006 CodeBoy2006 released this 03 Apr 11:09
· 55 commits to main since this release

Better Pingvin Share v1.15.1

Better Pingvin Share 1.15.1 focuses on release confidence, automation workflows, and operational hardening. This patch release adds bearer-token ZIP downloads for the automation API, introduces comprehensive backend/frontend/API/browser regression coverage, and gates container publication behind a unified GitHub Actions CI workflow.

Highlights

  • Added bearer-token-protected ZIP bundle downloads for /api/v1/shares/:shareId/files/zip.
  • Established a full regression stack across backend unit/integration tests, frontend Vitest coverage, Newman API smoke/full-regression suites, and Playwright browser smoke coverage.
  • Introduced a unified CI workflow with parallel backend, frontend, API smoke, and browser E2E jobs, artifact uploads, PR summaries, and a stable branch-protection target.
  • Moved GHCR publication behind the CI gate so main and release tags publish only after required checks succeed.

What's New

Automation API

  • /api/v1 now supports ZIP bundle downloads for share files with bearer-token authorization.
  • Browser smoke coverage now verifies API token creation in the UI and end-to-end /api/v1 usage.

Testing and Quality

  • Added root-level and package-level commands for fast tests, coverage, full regression runs, and browser smoke execution.
  • Added backend fixtures and coverage for authentication, users, config, reverse shares, shares, files, API tokens, and automation endpoints.
  • Added frontend coverage for utilities, services, hooks, middleware, core components, and page smoke paths.
  • Added structured Newman outputs (JSON, JUnit, HTML, logs, and request diagnostics) and Playwright outputs (HTML, JSON, JUnit, traces, screenshots, and videos on failure).

CI and Release Flow

  • Added .github/workflows/ci.yml as the new central CI workflow.
  • Standardized branch protection around CI / Required checks.
  • Converted Docker publication into a reusable/manual workflow invoked only after CI passes.
  • Kept manual publish controls for maintainers while separating development images from formal vX.Y.Z/latest release tags.

Fixes and Hardening

  • Fixed Docker seed config resolution after the backend config refactor.
  • Restored valid PNG uploads for the admin logo endpoint.
  • Stabilized CommonJS/default-import interop for backend runtime dependencies such as ClamAV and Sharp integrations.
  • Hardened anonymous-owner flows for expired-share handling and deletion regressions.
  • Aligned the browser API-token smoke flow with the backend's accepted relative expiration format for share creation.
  • Normalized GHCR image naming to lowercase and improved multi-architecture Docker build execution on native GitHub-hosted runners.

Upgrade Notes

  • This release includes the API token schema migration used by the automation token flow; ensure backend migrations are applied before enabling those workflows in production.
  • No manual configuration migration is required for the new test or CI tooling.
  • Maintainers should update branch protection to require CI / Required checks.
  • Release tags now publish images only after CI succeeds, so published containers may appear slightly later than in the previous release flow.