Skip to content

v0.2.0 release tracking: packed-package smoke#2

Open
michaeljgrimm wants to merge 1 commit into
mainfrom
codex/dat-3880-packed-smoke
Open

v0.2.0 release tracking: packed-package smoke#2
michaeljgrimm wants to merge 1 commit into
mainfrom
codex/dat-3880-packed-smoke

Conversation

@michaeljgrimm

@michaeljgrimm michaeljgrimm commented May 6, 2026

Copy link
Copy Markdown
Contributor

v0.2.0 Release Tracking PR

This PR is the v0.2.0 release tracking PR for the OPF package work approved through DAT-3870.

GitHub shows this PR as the Phase 3 diff only because Phase 1 and Phase 2 were already committed to main before this PR was opened. The full v0.2.0 delivery evidence is:

Phase Issue Commit Status
Phase 1 DAT-3878 5250430 Already on main
Phase 2 DAT-3879 94946bb Already on main
Phase 3 DAT-3880 895d1a0 In this PR

All-Phase PR Feasibility

A true all-phase PR against main is no longer possible without rewriting or reverting main, because main already contains the Phase 1 and Phase 2 commits. Any normal PR targeting main can only show commits and net file changes not already reachable from main, so PR #2 correctly shows only the remaining Phase 3 diff.

I do not recommend rewriting or reverting main just to manufacture an all-phase PR. This tracking PR plus the commit list above is the accurate delivery record.

Merge Recommendation

Recommendation: merge PR #2 after accepting this evidence trail. It is mergeable, and OPF CI succeeded on the Phase 3 head commit 895d1a0 in OPF CI run #31.

No additional PR is required before npm publish approval once PR #2 is merged. npm publish remains explicitly out of scope for this PR and requires separate approval.

Phase 3 Summary

  • Add a packed-install smoke that creates a clean temporary project, installs the generated @openpresentation/opf .tgz, and validates root imports, focused imports, raw JSON imports, valid deck validation, and invalid deck validation.
  • Wire the packed-install smoke into OPF CI after the npm package dry-run check.
  • Set npm package output sourcemap: false and document focused import guidance for consumers that only need one OPF surface.

Validation

  • corepack pnpm install --frozen-lockfile
  • corepack pnpm typecheck
  • corepack pnpm build
  • corepack pnpm test
  • corepack pnpm --filter @openpresentation/opf pack:dry-run
  • node packages/javascript/test/packed-install-smoke.mjs
  • corepack pnpm --filter @openpresentation/opf test:packed

Tarball Evidence

  • Dry run reported openpresentation-opf-0.2.0.tgz, package size 798.9 kB, unpacked size 4.8 MB, 418 files.
  • Packed-install smoke generated and installed openpresentation-opf-0.2.0.tgz at 798885 bytes and checked 418 tarball entries.
  • Hygiene assertions cover required package files, dist/spec/schemas/opf.schema.json, dist/spec/catalogs/audiences/board.json, no dist/spec/openapi.yaml, and no .map entries.

Approval Status

CTO review for Phase 3 is recorded in the PR comments. A formal GitHub approval could not be submitted because the authenticated GitHub user is also the PR author and GitHub blocks self-approval; the GitHub App approval path also returned Resource not accessible by integration.

Verify the generated tarball installs cleanly and keep npm output source-map free for v0.2.0.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@michaeljgrimm

Copy link
Copy Markdown
Contributor Author

CTO review for DAT-3880: approved from the Paperclip quality gate.

Reviewed the packed-install smoke, CI wiring, source-map decision, and tarball evidence. The smoke validates root imports, focused imports, raw JSON imports, valid deck validation, invalid deck validation, required tarball entries, exclusion of source maps, and exclusion of dist/spec/openapi.yaml. OPF CI passed on commit 895d1a0ec7d12d8a8a9e52a6a9335adc5bc83c61.

No blocking findings.

Note: I could not submit a formal GitHub approval because both the GitHub App and gh review path are blocked for this PR (Resource not accessible by integration; authenticated gh user is the PR author, and GitHub disallows approving your own PR).

@michaeljgrimm michaeljgrimm changed the title Add packed package smoke for OPF npm tarball v0.2.0 release tracking: packed-package smoke May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant