chore(release): types 0.10.13 (checkout_session_id + payment-failure-triage scenarios)#107
Merged
Conversation
….12) @codespar/types@0.10.12 was published in parallel by unrelated work (it does not contain the payment-failure-triage scenarios), so the scenarios added in #103 — which also landed as 0.10.12 — cannot publish at that number. Bump to 0.10.13 so the scenarios + DEMO_SCENARIO_MANIFEST publish at a free version. The manifest version is bumped in lockstep (its self-test enforces equality with the package version), and the example + the managed parity test pin 0.10.13.
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
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.
Single release of
@codespar/typesat the next free version, 0.10.13. Consolidates two additive changes already onmain, plus the manifest bump they require:PayResult.checkout_session_id(merged in feat(types): echo checkout_session_id on PayResult #105)DEMO_SCENARIO_MANIFEST(merged in feat(types): payment-failure triage demo scenarios + scenario manifest #103)0.10.12was published in parallel by unrelated work and predates both, so this ships at 0.10.13. Bumpspackages/types/package.jsonandDEMO_SCENARIO_MANIFEST.versionin lockstep — the manifest self-test enforces equality with the package version, so a package-only bump (like #106) would fail CI.Supersedes #106. After merge, tagging
v0.10.13triggerspublish.yml(OIDC) to publish the package; the example (#104) and the managed parity test (#402) pin 0.10.13.