chore(sdk): add build, publish metadata, and release process for @acc… - #247
Open
Seunfunmi-319509 wants to merge 13 commits into
Open
chore(sdk): add build, publish metadata, and release process for @acc…#247Seunfunmi-319509 wants to merge 13 commits into
Seunfunmi-319509 wants to merge 13 commits into
Conversation
…ensa/sdk Closes accensa#102 - Add tsup build pipeline emitting ESM (.mjs) + CJS (.js) + .d.ts to dist/ - Update package.json: main, module, types, exports map, files, sideEffects - Add comprehensive package README covering verifyReceipt, attachAccensaHook, createSettleHook, signing contract, and supported runtimes - Set up Changesets for versioning and changelog generation - Document semver policy in CONTRIBUTING.md with wire contract as major-worthy - Add .github/workflows/publish.yml: CI publishes on tag with provenance - Add verify-pack job to ci.yml: installs packed tarball into scratch project and verifies both entry points in ESM and CJS - Add CHANGELOG.md documenting the initial published release - Add lint script (no-op) so root lint command doesn't fail - vectors.rs reproducibility check unchanged and verified
|
@Seunfunmi-319509 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
@Seunfunmi-319509 is attempting to deploy a commit to the ACCENSA Team on Vercel. A member of the Team first needs to authorize it. |
|
MergeKeeper review Scope: in scope for linked issue The SDK build, publishing metadata, release process, and tarball verification workflow have been successfully implemented according to instructions. Reviewed commit: |
![mergekeeper[bot]](https://avatars.githubusercontent.com/u/173216192?s=60&v=4){kind=small}
|
MergeKeeper merge status Status: blocked Reason: Next steps:
|
…le, build SDK before dependent CI jobs
The micro-frontend scaffold added packages/shared (@accensa/shared) but pnpm-lock.yaml was never regenerated, so pnpm install --frozen-lockfile failed for every CI job with ERR_PNPM_OUTDATED_LOCKFILE. Verified the regenerated lockfile passes --frozen-lockfile under both pnpm 11 (ci.yml) and pnpm 9 (verify-pack, publish).
A pristine pnpm@11 install errors with ERR_PNPM_IGNORED_BUILDS for core-js-pure@3.50.0 (a transitive dep of the freshly-regenerated lockfile) because it is missing from the allowBuilds policy. Its postinstall is a benign messaging script; core-js is already allowlisted.
- restore multi-merchant db.ts (anchor/webhook schema grafted), sync and payments API routes, dashboard with mergePayments + modal a11y - fix web typecheck (12) and lint (3): PostgresClient alias, health route guard, anchor-submit ScVal guard, storybook/react imports, hook refs, anchor-panel callback ordering - SDK: restore rich reportSettlement (retry, error classes), wire error re-exports, stroop-correct price formatter, network-error wrapping, and re-export receiptLeaf - db.integration.test falls in line with new tables; format pre-existing drift; add @storybook/react dep
- drop duplicate lint/typecheck scripts in root package.json left by the main sync - drop duplicate @playwright/test devDependency in apps/web - SDK client: remove grafted if (!response.ok) duplicate, redundant error imports, and a locally redefined AccensaTimeoutError; map 429/auth/network errors in the fetch catch as intended - sync route: remove stale inline per-event indexing block grafted into the batched onEvents, and restore sync-events/cron-auth/sync-logger imports
The pnpm v9 to v11 bump only covered six jobs in ci.yml, but every workflow that runs pnpm install --frozen-lockfile uses the same pnpm-workspace.yaml, which on pnpm@9 cannot be parsed (allowBuilds and minimumReleaseAgeExclude are pnpm 11 config). This kept the visual regression job - and reconcile/publish - failing at the install step. - bump pnpm@9 to pnpm@11 in the remaining ci.yml jobs (test-reconcile, e2e web), publish.yml, reconcile.yml, and visual.yml - drop the duplicate node-version key in the e2e web job - restore test:visual, test:visual:update, storybook, and build-storybook scripts to apps/web (the merge dropped them; visual.yml runs pnpm test:visual)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ensa/sdk
Closes #102