@fantastic.dev/better-stripe 0.119.1 → 0.119.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/README.md +1 -1
- package/docs/releasing.md +3 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -26,6 +26,18 @@
|
|
|
26
26
|
- Remove internal tracker references from public documentation and add a
|
|
27
27
|
regression check that prevents their reintroduction.
|
|
28
28
|
|
|
29
|
+
## [0.119.3](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.2...v0.119.3) (2026-11-21)
|
|
30
|
+
|
|
31
|
+
### Continuous Integration
|
|
32
|
+
|
|
33
|
+
- **standards:** add the issue standard workflow ([#502](https://github.com/FantasticDevHQ/better-stripe/issues/502)) ([095a29a](https://github.com/FantasticDevHQ/better-stripe/commit/095a29a1960d02be956c2ea92064613cb4344c4a))
|
|
34
|
+
|
|
35
|
+
## [0.119.2](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.1...v0.119.2) (2026-11-21)
|
|
36
|
+
|
|
37
|
+
### Continuous Integration
|
|
38
|
+
|
|
39
|
+
- **release:** OSS-43 make release PRs meet the PR standard ([#503](https://github.com/FantasticDevHQ/better-stripe/issues/503)) ([9f44b54](https://github.com/FantasticDevHQ/better-stripe/commit/9f44b5448d8a51a07a0ed3a71f905aa37b4de77b))
|
|
40
|
+
|
|
29
41
|
## [0.119.1](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.0...v0.119.1) (2026-11-14)
|
|
30
42
|
|
|
31
43
|
### Bug Fixes
|
package/README.md
CHANGED
|
@@ -34,7 +34,7 @@ billing, and Connect marketplaces. It provides checkout, subscriptions, webhook
|
|
|
34
34
|
syncing, marketplace fees and splits, payouts, refunds, and disputes, with React
|
|
35
35
|
hooks and headless UI components.
|
|
36
36
|
|
|
37
|
-
**Version**: `0.119.
|
|
37
|
+
**Version**: `0.119.3` <!-- x-release-please-version --> (pre-1.0). API may change between minor versions until 1.0.
|
|
38
38
|
|
|
39
39
|
Connect platforms use the default GA API version. Non-Connect merchants using
|
|
40
40
|
customer-only Accounts v2 need preview access and an explicit preview version.
|
package/docs/releasing.md
CHANGED
|
@@ -73,6 +73,9 @@ Releases are automated with [Release Please](https://github.com/googleapis/relea
|
|
|
73
73
|
Write the title for consumers of the package: it becomes the changelog entry. A title that isn't a Conventional Commit is left out.
|
|
74
74
|
|
|
75
75
|
2. **On merge to `main`**, the `Release` workflow opens or updates a release PR that bumps `package.json`, `CHANGELOG.md`, the README version line and `.release-please-manifest.json`. It removes internal tracker IDs and links from the generated changelog (the prefixes in `scripts/internal-references.mjs`), formats it with the repository's pinned Prettier and commits any formatting changes through the release GitHub App, so CI validates the formatted branch. An already formatted changelog creates no extra commit. After formatting, the workflow enables squash auto-merge for the generated release PR using the release GitHub App.
|
|
76
|
+
|
|
77
|
+
Release PRs meet the [PR standard](pull-request-standard.md) like any other PR; the validator has no bot exemption. Release PR titles carry the configured release ticket (`pull-request-title-pattern` in `release-please-config.json`), which this repository's title rule requires. Release Please parses that title again after merge, so keep the pattern and the title in step. Before formatting, `scripts/release-pr-standard.mjs` appends the required sections after the generated body, leaving the generated description, its standalone `---` delimiters and the footer unchanged. The Summary declares the ticket with `Relates to`, and the workflow run serves as evidence and agent identity. The script then amends the release commit so its body ends with `No-ticket: automated release` (skipped when already present), keeping the author and subject, and force-pushes it with a lease using the App token so CI runs on the new head. The formatting commit carries the same footer.
|
|
78
|
+
|
|
76
79
|
3. **Auto-merge waits for green checks**. The active `main` ruleset requires `ci`, `Shadscan UI quality gate (100)` and `codegen`, with no bypass actors. Failed or pending required checks prevent merging. Once GitHub merges the generated release PR, the resulting `Release` workflow run tags the version, creates the GitHub release and publishes to npm through [trusted publishing](https://docs.npmjs.com/trusted-publishers) with provenance. There's no npm token.
|
|
77
80
|
|
|
78
81
|
Release policy lives in `release-please-config.json`. Keep the workflow file named `release.yml`, because the trusted publisher on npmjs.com is bound to that filename. A manually pushed `vX.Y.Z` tag also publishes, but only if it matches `package.json` and `CHANGELOG.md` has a section for it (`scripts/release-notes.mjs`). Verification runs on UbiCloud in four single-worker test shards, with build, typecheck,
|
package/package.json
CHANGED