@fantastic.dev/better-stripe 0.119.3 → 0.119.5

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 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.5](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.4...v0.119.5) (2026-11-21)
30
+
31
+ ### Documentation
32
+
33
+ - **community:** adopt organization community health defaults ([#504](https://github.com/FantasticDevHQ/better-stripe/issues/504)) ([adfb8e1](https://github.com/FantasticDevHQ/better-stripe/commit/adfb8e1536f18029d649a25bf25d3daeb3ce889c))
34
+
35
+ ## [0.119.4](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.3...v0.119.4) (2026-11-21)
36
+
37
+ ### Continuous Integration
38
+
39
+ - **standards:** add the PR standard re-run workflow ([#506](https://github.com/FantasticDevHQ/better-stripe/issues/506)) ([2bbdbb2](https://github.com/FantasticDevHQ/better-stripe/commit/2bbdbb253cd725d15c56c057a0008e477ee4429d))
40
+
29
41
  ## [0.119.3](https://github.com/FantasticDevHQ/better-stripe/compare/v0.119.2...v0.119.3) (2026-11-21)
30
42
 
31
43
  ### Continuous Integration
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Fantastic.Dev
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
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.3` <!-- x-release-please-version --> (pre-1.0). API may change between minor versions until 1.0.
37
+ **Version**: `0.119.5` <!-- 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.
@@ -218,6 +218,22 @@ proof, packed consumers and account/clock limits. Existing apps should follow
218
218
 
219
219
  ## Contributing
220
220
 
221
+ Contributions are welcome. Read the
222
+ [contributing guide](https://github.com/FantasticDevHQ/.github/blob/main/CONTRIBUTING.md)
223
+ and [Code of Conduct](https://github.com/FantasticDevHQ/.github/blob/main/CODE_OF_CONDUCT.md),
224
+ and report vulnerabilities privately as described in the
225
+ [security policy](https://github.com/FantasticDevHQ/.github/blob/main/SECURITY.md).
226
+
227
+ Source development needs Node.js 24 (as CI uses; the package supports Node.js
228
+ 20+, and the example's Vite and ESLint toolchain needs 20.19+, 22.13+ or 24+)
229
+ and pnpm 10.32.1, pinned in `package.json`.
230
+
231
+ ```sh
232
+ pnpm install --frozen-lockfile
233
+ pnpm run check:all # build, lint, format, typecheck, codegen drift, size/debt/circular/secrets gates, Shadscan, tests, coverage, AGENTS.md and CI parity
234
+ pnpm run test:pr-standard # PR metadata validator and bot tests
235
+ ```
236
+
221
237
  Example worktrees with Stripe use a **single-machine sandbox pool of one to five
222
238
  keys**. Other machines need separate sandbox accounts, keys and pools; leases do
223
239
  not coordinate across machines. See the
@@ -225,8 +241,8 @@ not coordinate across machines. See the
225
241
 
226
242
  See the [development guide](docs/development.md) for local setup and code generation,
227
243
  [testing utilities](docs/testing.md) for fixtures, and the [release guide](docs/releasing.md)
228
- for publishing. Run `pnpm run check:all` before submitting changes.
244
+ for publishing. Pull requests follow the [PR standard](docs/pull-request-standard.md).
229
245
 
230
246
  ## License
231
247
 
232
- MIT
248
+ [MIT](LICENSE), Copyright (c) 2026 Fantastic.Dev.
@@ -1,22 +1,70 @@
1
1
  # Pull request standard
2
2
 
3
- Every pull request, including bot and dependency PRs, must use this title structure:
3
+ Work is tracked on commits. A feature branch can carry many commits, each tied
4
+ to its own Linear ticket, so the ticket belongs on the commit and the PR title
5
+ does not have to carry one.
6
+
7
+ ## Titles
8
+
9
+ Every pull request, including bot and dependency PRs, uses a Conventional Commit
10
+ title:
4
11
 
5
12
  ```text
6
- type(scope): TICKET-123 short description
13
+ type(scope): short description
7
14
  ```
8
15
 
9
- Use a lowercase Conventional Commit type: `feat`, `fix`, `docs`, `style`,
10
- `refactor`, `perf`, `test`, `build`, `ci`, `chore`, or `revert`. The scope is optional.
11
- For a breaking change, put `!` before the colon. Put the uppercase Linear ticket ID
12
- immediately after the colon and space, followed by a description. Examples:
16
+ Use a lowercase type: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`,
17
+ `test`, `build`, `ci`, `chore`, or `revert`. The scope is optional. For a
18
+ breaking change, put `!` before the colon. A single-ticket PR may put the
19
+ uppercase ticket ID first in the description, and must then declare it in
20
+ Summary. Examples:
13
21
 
14
22
  ```text
23
+ fix(auth): correct session expiry
15
24
  fix(auth): JIF-65 correct session expiry
16
- chore: JIF-65 update dependencies
17
- feat(api)!: JIF-65 require authenticated requests
25
+ feat(api)!: require authenticated requests
26
+ ```
27
+
28
+ ## Commits
29
+
30
+ Every non-merge commit says which ticket it works on. Put a Linear magic word
31
+ and the ticket ID on its own line in the commit body:
32
+
33
+ ```text
34
+ feat(billing): add invoice export
35
+
36
+ Fixes JIF-65
37
+ ```
38
+
39
+ Use a closing word such as `Fixes` only when the commit completes the ticket,
40
+ and a non-closing word such as `Refs` for partial work. Outside contributors
41
+ without Linear access reference a GitHub issue the same way, as `#42`,
42
+ `owner/repo#42` or a full `https://github.com/.../issues/42` URL:
43
+
44
+ ```text
45
+ fix(cli): handle missing config file
46
+
47
+ Fixes #42
48
+ ```
49
+
50
+ A commit that works on no ticket or issue carries a footer with the reason:
51
+
52
+ ```text
53
+ docs: fix typo in README
54
+
55
+ No-ticket: comment-only fix
18
56
  ```
19
57
 
58
+ Linear links a commit only through a magic word; a bare ID is not enough. It
59
+ moves the ticket to In Progress when the commit is pushed and to Done when the
60
+ commit reaches the default branch. When a PR is squash-merged, the squash
61
+ message is built from the PR title and body, so the Summary declarations below
62
+ end up on the merged commit too. Merge commits are exempt.
63
+
64
+ Outside contributors follow the shared
65
+ [contributing guide](https://github.com/FantasticDevHQ/.github/blob/main/CONTRIBUTING.md);
66
+ keep its Commits and Pull requests sections consistent with this standard.
67
+
20
68
  Use the PR template and fill in these level-two headings exactly once, in order:
21
69
 
22
70
  | Section | Required content |
@@ -32,34 +80,55 @@ placeholders such as `TBD`, `N/A`, and `Pending` do not satisfy the standard.
32
80
 
33
81
  ## Linear linkage
34
82
 
35
- In Summary, include exactly one standalone linkage declaration for the ticket in
36
- the title. Choose the declaration that matches the actual scope:
37
-
38
- | Declaration | Use |
39
- | -------------------- | ------------------------------------------------------------------------------------------------------------------------ |
40
- | `Fixes JIF-123` | This PR completes the issue. Linear may apply its configured merged status. |
41
- | `Refs JIF-123` | This PR is partial work. Other configured workflow automation can still run, but merge does not apply the merged status. |
42
- | `Relates to JIF-123` | An informational relation with no status automation. |
43
-
44
- The ID may be replaced by the raw full Linear issue URL, for example
45
- `Refs <raw issue URL>`. The validator also
46
- accepts Linear's other documented closing, non-closing, and relation keywords,
47
- such as `Closes`, `Implements`, `References`, and `Related to`. Put the declaration
48
- on its own visible line, outside comments or code examples. Keep extra informational
49
- ticket links separate and use a closing word only for work actually completed.
50
- Reviewers assess whether the selected intent matches the PR's scope.
51
-
52
- An ordinary Markdown ticket link is useful context but does not declare this
53
- intent. Magic words in PR comments do not create Linear associations. These rules
54
- follow Linear's GitHub integration documentation.
55
-
56
- Linear also supports IDs in branch names and PR titles. The explicit body statement
57
- records intent; its absence is not proof that a missing native association was
58
- caused by formatting. Native PR linking requires the correct Linear workspace's
59
- GitHub integration with access to the organization/repository and working event
60
- synchronization. Check those independently when a correctly identified PR does not
61
- appear in Linear. GitHub autolink references, Markdown links, GitHub issue-sync
62
- mappings, and Codex PR attachments are separate from Linear's native PR association.
83
+ In Summary, declare every ticket the PR works on, on standalone lines outside
84
+ comments and code. The validator requires a declaration for every ticket that
85
+ any commit references, and for the title ticket when there is one. Several IDs
86
+ may follow one word:
87
+
88
+ ```text
89
+ Fixes JIF-65, JIF-66
90
+ Refs JIF-70
91
+ ```
92
+
93
+ | Declaration | Use |
94
+ | -------------------- | ---------------------------------------------------------------------------------------- |
95
+ | `Fixes JIF-123` | The ticket is completed. Linear applies its configured merged status. |
96
+ | `Refs JIF-123` | Partial work. Other workflow automation can run, but merge does not apply merged status. |
97
+ | `Relates to JIF-123` | An informational relation with no status automation. |
98
+
99
+ A raw full Linear issue URL may replace an ID. A GitHub issue reference
100
+ (`Fixes #42`, `Refs owner/repo#42` or a full issue URL) satisfies the Summary
101
+ declaration for outside contributors; it never substitutes for a Linear ticket
102
+ that a commit or the title references. Every target on a declaration line must
103
+ be a valid ticket or issue. The validator also accepts
104
+ Linear's other documented closing, non-closing, and relation words, such as
105
+ `Closes`, `Implements`, `References`, `Part of`, and `Related to`. A PR that works
106
+ on no ticket or issue states `No ticket: <reason>` in Summary instead. A feature PR also
107
+ links its Linear project.
108
+
109
+ Linear does not re-detect tickets that were linked by earlier merges into a
110
+ feature branch when that branch merges to the default branch. The feature PR's
111
+ Summary must list them again; the validator enforces this through the commits.
112
+
113
+ An ordinary Markdown ticket link is context, not a declaration. Magic words in
114
+ PR comments do not create Linear associations. These rules follow
115
+ Linear's GitHub integration documentation.
116
+
117
+ ### One-time Linear setup per team
118
+
119
+ Native linking requires the correct Linear workspace's GitHub integration with
120
+ access to the organization and repository. In Linear, under Settings > Team >
121
+ Workflows & automations:
122
+
123
+ 1. Enable **Link commits to issues with magic words**, and add the GitHub push
124
+ webhook that Linear shows. Commit linking works with one GitHub organization.
125
+ 2. Optionally add branch-specific rules for the PR target branch. For example,
126
+ a merge into `^feat/.*` sets an "Integrated" status and a merge into `main`
127
+ sets Done. Rules apply to target branches only.
128
+
129
+ Check these when a correctly declared PR or commit does not appear in Linear.
130
+ GitHub autolinks, Markdown links, and GitHub issue sync are separate from
131
+ Linear's native association.
63
132
 
64
133
  Evidence must include a reviewer-accessible HTTPS link or fenced test, log, or API
65
134
  output. Explain which checks passed and what the result demonstrates. A bare
@@ -71,7 +140,9 @@ Reviewers assess those details.
71
140
 
72
141
  In Evidence, explicitly declare `UI changes: Yes` or `UI changes: No`.
73
142
  UI changes require screenshots and/or video of the affected flow, uploaded
74
- through GitHub attachments. At least one is required; both are welcome when useful.
143
+ through GitHub attachments or published as a GitHub Actions artifact (for
144
+ example a recording from an end-to-end job, which agents without a browser can
145
+ produce). At least one is required; both are welcome when useful.
75
146
  Embed screenshots inline and label the proof fields you include:
76
147
 
77
148
  ```markdown
@@ -79,12 +150,23 @@ UI changes: Yes
79
150
 
80
151
  - Screenshot: ![Affected flow](https://github.com/user-attachments/assets/UPLOAD_ID)
81
152
  - Video: https://github.com/user-attachments/assets/RECORDING_ID
153
+ - Video: https://github.com/OWNER/REPO/actions/runs/RUN_ID/artifacts/ARTIFACT_ID
154
+ ```
155
+
156
+ Upload attachments with the GitHub CLI rather than a browser: write the local
157
+ reference on the labeled line, then pass the file with `--attach` to
158
+ `gh pr edit` (also `gh pr create` and `gh pr comment`). `gh` uploads the file
159
+ and rewrites the reference to the attachment URL:
160
+
161
+ ```sh
162
+ # body.md contains: - Screenshot: ![Affected flow](./flow.png)
163
+ gh pr edit <n> --body-file body.md --attach './flow.png#Affected flow'
82
164
  ```
83
165
 
84
166
  The validator inspects changed frontend files, styles, markup, and image assets,
85
167
  excluding tests and fixtures. Detected UI files require visual proof even
86
168
  if the declaration says No. Declare Yes for UI changes in other file types too,
87
- such as server-rendered templates in backend code. Use GitHub upload URLs.
169
+ such as server-rendered templates in backend code. Use GitHub upload or Actions artifact URLs.
88
170
  Reviewers verify the media actually demonstrate
89
171
  the affected flow; the validator checks references, not image or video contents.
90
172
  Backend,
@@ -123,11 +205,18 @@ so metadata edits can clear a failure without another commit. Operators can use
123
205
  the workflow's manual PR-number input to revalidate existing PRs or retry an API
124
206
  failure. Run `pnpm run test:pr-standard` to test the validator and bot behavior.
125
207
 
208
+ Metadata bodies accept LF, CRLF and lone CR line endings. If the metadata API or
209
+ feedback update fails after the head is known, the enforcer attempts a failure
210
+ status and rethrows the original error even if status publication also fails.
211
+
126
212
  ## CI compute
127
213
 
128
214
  The metadata job uses `ubicloud-standard-2-ubuntu-2404`, the repository's default
129
215
  Linux UbiCloud runner. Existing test and deployment jobs keep their configured
130
- UbiCloud sizes. GitHub Actions schedules these workflows; repository Actions and
216
+ UbiCloud sizes. npm provenance publishing requires a supported GitHub-hosted
217
+ build/publish job under an approved runner exception; new exceptions require
218
+ explicit owner approval. Keep ordinary verification on UbiCloud and follow the
219
+ [release guide](releasing.md). GitHub Actions schedules these workflows; repository Actions and
131
220
  the UbiCloud integration's repository access must both remain enabled. A queued
132
221
  job without a runner calls for checking integration access, not changing providers.
133
222
 
package/docs/releasing.md CHANGED
@@ -74,7 +74,7 @@ Releases are automated with [Release Please](https://github.com/googleapis/relea
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
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.
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`); a title ticket is optional under the PR standard, but this one links release PRs to the release ticket. 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
78
 
79
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.
80
80
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fantastic.dev/better-stripe",
3
- "version": "0.119.3",
3
+ "version": "0.119.5",
4
4
  "description": "Convex component for Stripe Accounts v2, subscriptions, metered billing and Connect marketplaces, with React workflows.",
5
5
  "keywords": [
6
6
  "stripe",