Skip to content

fix(release): publish one Chromium-family ZIP for v0.4.4 - #66

Merged
kbuffardi merged 2 commits into
mainfrom
fix/shared-chromium-release-zip
Aug 10, 2026
Merged

fix(release): publish one Chromium-family ZIP for v0.4.4#66
kbuffardi merged 2 commits into
mainfrom
fix/shared-chromium-release-zip

Conversation

@kbuffardi

Copy link
Copy Markdown
Owner

Summary

  • publish one browser-cpp-chromium-family ZIP for Chrome, Edge, Brave, and Chromium
  • retain target-to-artifact mappings in release metadata and update release documentation
  • preserve the separate Firefox build, signing, and signed-XPI flow
  • bump manifest, package, and lockfile versions to v0.4.4

Validation

  • npm run version:check
  • npm run lint
  • npm run test:e2e
  • npm run build
  • npm run release:check-version
  • npm run test:browser:firefox
  • isolated package verification: exactly one Chromium-family ZIP, checksum, and release manifest

Closes #65

Publish one canonical Chromium-family ZIP for Chrome, Edge, Brave, and Chromium while retaining target mappings in release metadata. Preserve Firefox's independent signed-XPI flow and bump the release to v0.4.4.\n\nCloses #65
@kbuffardi
kbuffardi merged commit adfa405 into main Aug 10, 2026
2 checks passed
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.

Release one shared Chromium-family ZIP artifact

1 participant