Skip to content

chore(types): release 0.10.13 (checkout_session_id on PayResult)#106

Closed
dangazineu wants to merge 1 commit into
mainfrom
chore/release-types-0.10.13
Closed

chore(types): release 0.10.13 (checkout_session_id on PayResult)#106
dangazineu wants to merge 1 commit into
mainfrom
chore/release-types-0.10.13

Conversation

@dangazineu

Copy link
Copy Markdown
Contributor

Bump @codespar/types 0.10.11 → 0.10.13 to publish the additive PayResult.checkout_session_id field merged in #105.

0.10.11 and 0.10.12 are already on the registry and predate the field, so it ships in the next free patch. After merge, tagging v0.10.13 triggers publish.yml (OIDC trusted publishing) to release it.

Version-only change; field + docs already landed in #105.

Bump @codespar/types to 0.10.13 to publish the additive
PayResult.checkout_session_id field merged in #105. 0.10.12 is already on
the registry, so the field ships in the next patch. Tagging v0.10.13 after
merge triggers the publish workflow (OIDC trusted publishing).
@dangazineu
dangazineu force-pushed the chore/release-types-0.10.13 branch from ee7a784 to 7213594 Compare June 28, 2026 18:09
dangazineu added a commit that referenced this pull request Jun 28, 2026
Single release of @codespar/types at the next free version, 0.10.13. Consolidates
two additive changes already on main, plus the manifest bump they require:

- PayResult.checkout_session_id (merged in #105)
- the payment-failure-triage demo scenarios + DEMO_SCENARIO_MANIFEST (merged in
  #103)

0.10.12 was published in parallel by unrelated work and predates both, so this
ships at 0.10.13. Bumps packages/types/package.json AND
DEMO_SCENARIO_MANIFEST.version in lockstep (the manifest self-test enforces
equality with the package version — a package-only bump like #106 would fail it).
Supersedes #106. After merge, tagging v0.10.13 publishes the package; the example
(#104) and the managed parity test (#402) pin 0.10.13.
@dangazineu

Copy link
Copy Markdown
Contributor Author

Superseded by #107, which is the single 0.10.13 release. #106 bumps only package.json; it does not bump DEMO_SCENARIO_MANIFEST.version (added to main in #103), so it would fail the manifest lockstep test on main. #107 bumps both in lockstep and, since PayResult.checkout_session_id (#105) is already on main, publishing 0.10.13 from #107 ships the field and the triage scenarios together. No work lost — closing in favor of #107.

@dangazineu dangazineu closed this Jun 28, 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