chore(deps): bump actions/setup-node from 4 to 6#1
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): bump actions/setup-node from 4 to 6#1dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dependabot
Bot
added
dependencies
sshdopey
added a commit
that referenced
this pull request
Apr 20, 2026
Two major changes that ship together because they replace the same surface:
1. Plans now have user-supplied names stored on chain
- Plan creation form has a required Name field at the top ('Pro Monthly',
'Enterprise Annual', etc.)
- After the contract create_plan succeeds and returns a plan_id, a single
Stellar tx writes both the project tag (vw{slot}p{planId}) and the plan
name (vw{slot}n{planId}) — one wallet signature for both ops
- readProjects parses vw{slot}n* entries into a planNames map on each
OnChainProject so any reader (dashboard, checkout) can resolve names
- getProjectPlansWithData accepts the planNames map and merges it into
each returned plan as plan.name
- New NamedPlan type (ChainPlan + name) used by all downstream UI
2. Public IDs are short, opaque, premium-feeling strings
- lib/plan-id-codec.ts: base-56 encoding (alphabet excludes I/O/l/0/1
ambiguity) padded to 4 chars minimum. Plan 42 -> 'AAAs', plan 1000 ->
'AAR2', plan 1M -> 'AHJq'
- decodePlanId is back-compat: still accepts plain numeric strings so
legacy /p/42 links keep working
- planCheckoutUrl(id) returns the canonical /p/{encoded} share URL
- All UI surfaces switched: plan cards show 'Pro Monthly', subscriber
rows show plan name (fallback 'Plan AAAs'), subscriber detail modal
shows sub_AAAs as the subscription ID, integrate tab shows the
encoded checkout URL as the headline integration step
- Checkout page /p/[planId] decodes the URL, fetches plan + reads the
merchant's account data to display the proper plan name and project
name above the price ('Vowena Tips → Pro Monthly → $9.99 / month')
Result: no numeric indexes (#0, #1, #2) anywhere a user or developer sees.
sshdopey
added a commit
that referenced
this pull request
Apr 20, 2026
The user shouldn't see 'Plan #2' or 'GDFI...VLYN' anywhere — they should see 'Vowena Tips → Pro Monthly'. This commit makes that real: useSubscriptions hook now resolves human names: - For each subscription, after fetching plan + sub, also reads the merchant's Stellar account data via readProjects() - Walks the projects to find which one owns the plan, pulls projectName and planName from there - Caches per merchant (one Horizon read per unique merchant, not per sub) - Exposes Subscription.projectName and Subscription.planName /subscriptions page (subscriber-facing): - Card shows project name as eyebrow + plan name as headline - Avatar tile uses project initial - Status surface uses period label ('per month' not 'per 2592000s') - Falls back to 'Untitled project' / 'Plan' if metadata missing SubscriptionModal: - Header shows project initial, project eyebrow, plan name - Details tab shows Project, Plan, Subscription ID (sub_xxxx encoded), Plan ID (encoded), subscriber wallet (with Explorer link), merchant wallet (with Explorer link) - All numeric IDs hidden behind encoded form Project Subscribers tab — drill into a single plan: - Added 'Plan' dropdown next to status filter (only shows when project has 2+ plans) - 'All plans' default; selecting a plan filters subscribers to that one - Combines with status filter, so e.g. 'Active subscribers to Pro Monthly' Plus: clarified to the user that plan IDs are GLOBALLY UNIQUE across all merchants — there's exactly one plan #1 in the contract. The scrambled URL /p/GnRap resolves to that one plan; no merchant collision is possible.
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.
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)621ac41README.md: bump to latest released checkout version v6 (#1446)2951748Bump@actions/cacheto v5.0.1 (#1449)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)