Skip to content

g1t/services/billing/migrations/0037_security_activation.sql

21 lines1,630 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Teams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar1-- The Security and quality activation: $10 a month per workspace turns on
2-- the security suite's paid features for its private repositories (custom
3-- patterns, validity checks, delegated bypass, code scanning, dependency
4-- review and the security overview). Public repositories have them free,
5-- and secret scanning, push protection, vulnerability alerts and security
6-- updates are free everywhere. Agent fixes are charged as agent usage.
7--
8-- Its monthly price lives in the price book like every other price, so the
9-- pricing page, the Billing page and the subscription all read it from
10-- here, and a change to it is versioned and published like any other. It is
11-- a flat price, not a cost passed through, so it carries no markup.
12INSERT OR IGNORE INTO prices (meter, title, unit, cost_micros, markup_percent, source, updated_at)
13VALUES ('security_activation', 'Security and quality activation', 'workspace-month', 10000000, 0, 'list', '2026-10-07T00:00:00Z');
14
15INSERT OR IGNORE INTO price_changes (id, meter, old_cost_micros, new_cost_micros, markup_percent, reason, created_at)
16VALUES ('prc_security_activation', 'security_activation', 10000000, 10000000, 0,
17 'New: the Security and quality activation, $10 a month per workspace', '2026-10-07T00:00:00Z');
18
19INSERT OR IGNORE INTO price_versions (id, meter, version, cost_micros, markup_percent, effective_at, reason, created_by, created_at, applied_at)
20VALUES ('pv_security_activation_1', 'security_activation', 1, 10000000, 0, '2026-10-07T00:00:00Z',
21 'The Security and quality activation', 'migration', '2026-10-07T00:00:00Z', '2026-10-07T00:00:00Z');