Skip to content

chore: prepare 0.0.19 release cut#22

Merged
freshtechbro merged 1 commit into
mainfrom
codex/generalfixes
Apr 13, 2026
Merged

chore: prepare 0.0.19 release cut#22
freshtechbro merged 1 commit into
mainfrom
codex/generalfixes

Conversation

@freshtechbro

Copy link
Copy Markdown
Owner

Summary

  • add post-publish registry-consumer smoke validation and wire it into the public release workflow
  • bump package and extension version owners to 0.0.19 and refresh release-facing docs and ledgers
  • fix the screencast stop race that could schedule another frame after a first-capture stop request

Testing

  • npm run version:check
  • node scripts/audit-zombie-files.mjs
  • node scripts/docs-drift-check.mjs
  • node scripts/chrome-store-compliance-check.mjs
  • ./skills/opendevbrowser-best-practices/scripts/validate-skill-assets.sh
  • npx opendevbrowser --help
  • npx opendevbrowser help
  • npm run lint
  • npm run typecheck
  • npm run test:release-gate
  • npm run test
  • npm run build
  • npm run extension:build
  • npm run extension:pack
  • npm pack
  • node scripts/registry-consumer-smoke.mjs --version 0.0.18 --output /tmp/registry-consumer-smoke-0.0.18.json

Notes

  • direct push to protected main was rejected by repo rules, so this release-prep bundle is going through the required PR path
  • the only mandatory gate still pending is the real post-publish registry-consumer smoke for 0.0.19 after npm publish

- add post-publish registry-consumer smoke coverage and workflow wiring
- bump package and extension metadata to 0.0.19 and refresh release docs
- record release-prep evidence and the screencast stop-race fix

Co-authored-by: Codex <noreply@openai.com>
@freshtechbro freshtechbro merged commit 0002d7d into main Apr 13, 2026
8 checks passed
@freshtechbro freshtechbro deleted the codex/generalfixes branch April 13, 2026 19:35
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